Prosco Posted February 27, 2021 Report Posted February 27, 2021 (edited) Good morning all, I just bought the SAB 340 1.6. Download: OK. Installation: OK. Launch: I arrive in the cockpit, the program asks for my email and password, I validate and CRASH. Here the install message and the log files. I contacted support: wait. NB: I have the TBM900 and no problem. Edited March 3, 2021 by Prosco
Goran_M Posted February 27, 2021 Report Posted February 27, 2021 Remove JarDesign ground handling plugin and try again. Please post back results. 1
Prosco Posted February 27, 2021 Author Report Posted February 27, 2021 First, a big thank you Goran_M for this quick response. I just removed JarDesign ground handling plugin and same problem, I put the log file (Log_crash_04.txt) accessible here. I specify : 1/ Installation => OK / X-plane launch and SAAB 340 launch => OK / Window with Email and password request => OK. 2/ I validate the window and Xplane 11.52 Vulkan mode => CRASH. 3/ I restart Windows 10, deactivate fire wall then Xplane then SAAB 340 => Crash. 4/ I restart Windows 10 then Xplane then TBM 900 => OK. 5/ I restart Windows 10 then Xplane then SAAB 340 => Crash.
Ben Russell Posted February 27, 2021 Report Posted February 27, 2021 7 minutes ago, Prosco said: First, a big thank you Goran_M for this quick response. I just removed JarDesign ground handling plugin and same problem, I put the log file (Log_crash_04.txt) accessible here. I specify : 1/ Installation => OK / X-plane launch and SAAB 340 launch => OK / Window with Email and password request => OK. 2/ I validate the window and Xplane 11.52 Vulkan mode => CRASH. 3/ I restart Windows 10, deactivate fire wall then Xplane then SAAB 340 => Crash. 4/ I restart Windows 10 then Xplane then TBM 900 => OK. 5/ I restart Windows 10 then Xplane then SAAB 340 => Crash. Looks like X-Plane is getting stuck in some kind of Vulkan-related loop. Option 1: Update your GPU drivers, test again. Option 2: Use X-Plane in OpenGL mode. Option 3: Try removing "X:\X-Plane 11/Resources/plugins/SAM/" temporarily. Hope that helps.. 1
Prosco Posted February 27, 2021 Author Report Posted February 27, 2021 (edited) Option 1, 2 and 3 => CRASH. I weigh that the crash occurred during the validation process (mail + password + validation) puique until this validation, I was in the cockpit of the SAAB 340 then the validation window appeared and after validation "server connection" and ... CRASH. I specify : 4/ I restart Windows 10 then Xplane then TBM 900 => OK. Edited February 27, 2021 by Prosco
sirtopper Posted February 27, 2021 Report Posted February 27, 2021 Hi, not sure if will help but I have to load into xplane with a default xplane aircraft then switch to the SAAB 340. This works for me 1
Prosco Posted February 27, 2021 Author Report Posted February 27, 2021 Sorcellery !!! 1 / I removed JarDesign ground handling plugin 2 / I switched to OpenGL mode 3 / I reinstalled the LES SAAB 340 4 / I started Xplane then Cessna 172SP 5 / from the Cessna 172SP, I launched the SAAB 340A. It works ! I'm in the cockpit! Then, I put back JarDesign ground handling plugin, I switched to Vulkan mode and finally I launched the SAAB 340A with fear in my stomach and ... it still works. Soon I'll be flying! A big thanks to all of you
Prosco Posted February 28, 2021 Author Report Posted February 28, 2021 (edited) I think I found the BUG !!! If I run LES SAAB 340 without or with plugins: EGLL Gate 211 => OK LFBR 32R => OK LFML 13L => OK LFPO any location => CRASH. I should point out that in the Custom scenery, I only have the Global Airports updated today. Edited February 28, 2021 by Prosco
Goran_M Posted February 28, 2021 Report Posted February 28, 2021 Corrupted scenery is getting very annoying.
Prosco Posted February 28, 2021 Author Report Posted February 28, 2021 With the Cessna and the 737 Laminar, no problem.
JGregory Posted February 28, 2021 Report Posted February 28, 2021 We are discussing this with Laminar, please be patient.
Prosco Posted February 28, 2021 Author Report Posted February 28, 2021 No problem, I am more than patient and I am not complaining but I just bought the SAAB 340A and no luck for the first launch of the plane, I am leaving from LFPO. So it crashes and I don't understand, until by chance I change airports. Thanks again to those who helped me.
Captain_Alex Posted March 2, 2021 Report Posted March 2, 2021 I have also noticed the crash at LFPO. I am wondering if there are any more locations that cause a crash.
GrandPa1965 Posted March 12, 2021 Report Posted March 12, 2021 (edited) Actually my XPlane 11 freezes when I fly the Saab 1.6.2 from for example EGLC or LERS to the east until I cross Lon 1,6XXXXX°. I could repeat this several times even with a virgin installation of XPlane without any other plug-ins or mods than the Saab. And the LFPO issue applies to my XPLane as well so maybe the additional information does help. Edited March 12, 2021 by GrandPa1965
JGregory Posted March 13, 2021 Report Posted March 13, 2021 On 3/2/2021 at 3:37 PM, legofreak85 said: I have also noticed the crash at LFPO. I am wondering if there are any more locations that cause a crash. 6 hours ago, GrandPa1965 said: Actually my XPlane 11 freezes when I fly the Saab 1.6.2 from for example EGLC or LERS to the east until I cross Lon 1,6XXXXX°. I could repeat this several times even with a virgin installation of XPlane without any other plug-ins or mods than the Saab. And the LFPO issue applies to my XPLane as well so maybe the additional information does help. Prime Meridian seems to be the problem.
N1K Posted March 13, 2021 Report Posted March 13, 2021 LFMK seems to be a problem too. I flew it in there no problem, but can't get it to load a saab there.
Ben Russell Posted March 13, 2021 Report Posted March 13, 2021 2 hours ago, N1K said: LFMK seems to be a problem too. I flew it in there no problem, but can't get it to load a saab there. Are these custom scenery airports or just stock x-plane stuff?
N1K Posted March 13, 2021 Report Posted March 13, 2021 Stock, don't believe I have any custom scenery in that area of the world.
JGregory Posted March 13, 2021 Report Posted March 13, 2021 The issue has been diagnosed. Please see the release notes fro v1.6.2.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now