Jump to content

Goran_M

Leading Edge
  • Posts

    5,636
  • Joined

  • Days Won

    229

Everything posted by Goran_M

  1. We're not "justifying" anything. We're giving you a legitimate reason. X-Plane 11.50 B10 broke the ILS. This is simply fact. Try the TBM in 11.41 or any beta builds prior to 11.50 B10, and the ILS will work perfectly. The SR22 was made for 11.50, and the X-Plane change in beta 10 was there while they were working on it. If you try flying the SR22 it in 11.41, you won't get very far. We have no reason to lie, and we never have lied about how something broke. It WILL be fixed, but it will be part of a larger update. A work-around is if you have navigraph data. Don't use the 11.50 format. Using the X-Plane 11 format will make the ILS work perfectly.
  2. I understand, Igor. But I can only go by what the backtrace is telling me. And it's telling me the TBM is not the cause. The reason your other add ons are working is because no 2 add ons are coded the same, and something in X-Plane is causing it to crash. It could be the TBM, or it could be a combination of the TBM and your plugins. It could even be a plugin not liking something in the TBM, and as a result, X-Plane is crashing because of the conflict. In cases like this, where the backtrace lists X-Plane.exe crashing, the best thing to do is to send the log to Laminar. This may very well be a bug in X-Plane that the TBM found, and needs to be addressed. If it was the TBM that caused this, the backtrace would have at least 1 mention of the TBM.
  3. Above is the backtrace from your log file, which is what tells us what caused the crash. I see no reference to the TBM causing the crash. This is X-Plane crashing from something within the sim. Not the TBM. This is something for Laminar to look into. I'll need the log.txt. Not the TBM900_Log.txt
  4. There's a lot going on in that crash. You have quite a few plugins, and at least 1 of which may be conflicting with the TBM. Can you remove your 3rd party terrain rdar and see if the crash happens again. The TBM has its own terrain radar.
  5. Make sure you don't have anything else overriding the TBM's load manager. Including the default X-Plane load screen.
  6. This is most definitely an issue you need to take up with the corresponding developers of those plugins. They'll need to add some kind of exception to the TBM.
  7. In cases like this, the TBM900_log.txt is the file we need.
  8. https://discord.gg/yUrUf5
  9. Shouldn't do either of those things. Can you replicate the problems, and if so, please post a log.txt file afterwards.
  10. Might have to contact X-Aviation support for this one.
  11. Make sure Windows Defender is also not running.
  12. Are you using an older installer? Make sure you download the current installer from your account.
  13. The AOA indicator runs on OpenGL. 11.50 uses Vulkan, and the AO indicator is not yet compatible with Vulkan. As for the lighting, make sure you have HDR enabled in your Graphics settings in X-Plane.
  14. I'm not sure what to tell you, then. The log that you posted should indicate that Gizmo is loaded and running. It does not. See for yourself. Open up the log.txt file you uploaded in your previous post and do a search for Gizmo. There is no trace of it. Do you perhaps have some kind of anti virus that is preventing Gizmo from running?
  15. No, it's definitely personnel. Personal is when something is "personal" to you. Personnel, is authorized "persons".
  16. I just looked through your log. There is no mention of Gizmo anywhere in there. Can you double check it's in your Resources/plugins folder?
  17. The fact you're getting serious stuttering tells me you either have incompatible plugins installed on X-Plane Vulkan, or your hardware may need upgrading. Without a log file, we can't determine what the problem is. The TBM works fine on vanilla X-Plane.
  18. https://discord.gg/WUe5qT
  19. Happy to help.
  20. You have a lot going on here. Can you try an airport with no plugins. A good test airport we like to use is SCIP. Try that airport and see if it crashes again. My guess is, looking from the log file and the crash, that the ground handling plugin is causing issues, so also remove that plugin from the plugins folder and see if that also fixes the problem. Post back results.
  21. Windows updates, if big enough, will change the OS, causing Gizmo to "see" the OS as a new one.
  22. Your log shows no indication of a crash and no indication of the TBM being loaded.
  23. Then I have no idea how you managed to run the TBM on years old Nvidia drivers. Saso even commented to people to PLEASE update your GPU drivers when running the TBM, otherwise you will get CTD's or the TBM will simply fail to load.
×
×
  • Create New...