Jump to content

skiselkov

Members
  • Content Count

    377
  • Joined

  • Last visited

  • Days Won

    28

skiselkov last won the day on February 9 2020

skiselkov had the most liked content!

Community Reputation

231 Excellent

6 Followers

About skiselkov

  • Rank
    Advanced Member

Recent Profile Visitors

3,930 profile views
  1. Yeah, Centos7 may be just a bit too old on the libs being shipped. Looking at the release info, it came out in 2014, which means the lib major revisions are from that year. Afterwards Centos only ships bugfixes & backported security patches, not new functionality. I usually test as far back as Ubuntu 16.04, but really 18.04 (i.e. around 2018) is the cutoff for how old of a distro we support.
  2. What distro are you running? The issue is in missing symbols in some basic libs: OpenGPWS.xpl: undefined symbol: _ZTINSt6thread6_StateE X-TCAS.xpl: undefined symbol: _ZTINSt6thread6_StateE systems.xpl: undefined symbol: __cxa_thread_atexit_impl _ZTINSt6thread6_StateE is normally found in libstdc++.so (the standard C++ library) and __cxa_thread_atexit_impl is found in libc.so (the standard C library). I build & test on Ubuntu 18.04 LTS.
  3. Looking at the log, I believe you're hitting the same scenery as the user on our Discord. The issue is VirtualDesign3D's SCEL because of this nugget of a great airport name encoded in the apt.dat: "Arturo Merino Benítez International__de X-plane octubre-2016" You can temporarily work around this issue by going into the scenery, there should be a subfolder named "Earth nav data", inside which you'll find "apt.dat". Open it up in Notepad and near the top should be a line that looks like this: 1 1555 1 0 SCEL Arturo Merino Benítez International__de X-plane octubre-2016 Just trim down
  4. Hey CJ, thanks for the input. I checked this with folks who consulted for us during the development - the landing lights switch takes precedence over the PULSE system, so if you set the switch to LDG, you will get steady lights, regardless of what the PULSE system is selected to. To get pulsing, you need to select the landing lights switch to either TAXI or OFF and then select the PULSE switch to on.
  5. Cannot reproduce. I tried both normal point-to-point navigation and OBS mode. As you can see, I have BRG1 selected to GPS and it's showing the correct target.
  6. 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?
  7. Same for you, please let me know if you'd like to use the beta build of the TBM for the time being.
  8. 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.
  9. 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.
  10. I'm afraid I don't understand. What inverter? The TBM doesn't have an inverter. What did you push?
  11. 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
  12. 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.
  13. 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.
  14. Thanks for the quick responses guys, will investigate.
  15. 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
×
×
  • Create New...