Jump to content

skiselkov

Members
  • Content Count

    372
  • Joined

  • Last visited

  • Days Won

    28

skiselkov last won the day on February 9

skiselkov had the most liked content!

Community Reputation

228 Excellent

6 Followers

About skiselkov

  • Rank
    Advanced Member

Recent Profile Visitors

3,552 profile views
  1. Looking at that traffic global screen, all the contacts are more than 10,000 ft away from your altitude. TAS/TCAS only shows contacts that are within +-2,700 ft in normal more or +-10,000 ft when in UNREST (unrestricted) mode. Can you check if they appear when they're within 2,700 ft of your altitude?
  2. Same for you, please let me know if you'd like to use the beta build of the TBM for the time being.
  3. We have a workaround in the beta build of the TBM. The issue is a driver compatibility issue on AMD + Vulkan + Windows 10. Let me know if you'd like to hop onto the beta channel for now until we get the fix out in the general build.
  4. I have no idea what this is. We do not control map layers, nor do we control TCAS. I see you've got some other plugin doing weird stuff to your install: XPR 16:57:43 plugin enablePilot Client Connector Started. Altitude/win v1.9.19b started What is this? This isn't our code and it's the doing stuff to the multiplayer (i.e. TCAS) subsystem.
  5. I'm afraid I don't understand. What inverter? The TBM doesn't have an inverter. What did you push?
  6. Ok, I can see even X-Plane's fmod is complaining about getting some garbage from the sound driver: 0:03:35.947 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(511): FMOD error 29 - Value passed in was a NaN, Inf or denormalized float. 0:03:35.947 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(511): FMOD error 29 - Value passed in was a NaN, Inf or denormalized float. If I had to guess, something is *really* broken in your audio driver. While FMod might be able to catch the error early and some
  7. Try loading into the TBM and then immediately quitting. We need to get the full log. The file you sent is truncated. Also, ZIP compression will reduce the size by about a factor of 20x, making it far easier to ship. We need to see the start as the aircraft is loading in.
  8. Found the issue with the Localizers. X-Plane 11.50b10 changed one element of the localizer nav data encoding (bearing), which broke the custom localizer simulation code in the TBM. Compatibility workaround will be included in the next TBM update.
  9. Thanks for the quick responses guys, will investigate.
  10. When you report problems include ALL the reproduction steps. What airport? What runway? What approach were you flying? Where were you located? With what you have told me so far, I really have nothing to go on
  11. Your turbines are worn out. That's why the engine can't produce its full power rating anymore. Check engine maintenance.
  12. Disable VSync and let's see where the framerate falls. I bet it's because your sustainable framerate is somewhat below 30 fps in the TBM, which results in the driver being unable to make up its mind and jumping between 20 fps and 30 fps.
  13. Message sent. We should have you up and running in Vulkan in no time.
  14. @Thedonsimmer We need to have a closer look at what's happening under the hood in your sim. Something is clearly causing control issues, either by moving the throttle on its own or preventing the binding from working. Here's how the throttle control in the TBM works: it reads the following dataref: sim/flightmodel/engine/ENGN_thro. So we will need to take a look at its exact behavior, as that's what the aircraft model is looking at as well. Please go ahead and grab this plugin: https://github.com/leecbaker/datareftool/releases/download/2020.03.24/datareftool_2020_03_24.zip and install it
  15. I'm aware of some issues in the enroute pathway logic. I'm debugging this and hoping to get this one finally squashed in release 1.1.13. Thanks for the patience guys.
×
×
  • Create New...