Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

CTD When Using Flightbeam KSFO-MSFS2024-Hopefully Resolved

Featured Replies

I tried at least 5 times to get a flight going when using the native version of Flightbeam's KSFO. I kept getting a CTD during the Pre-Flight phase (FENIX A321) about 5-10 minutes in. I had version 7.0.3 version of the noolaero-module-vgds installed, so I went to the Flightbeam website and found a newer version, 8.0.0 and updated the module (Flightbeam uses this Visual Docking system in their sceneries). I am currently flying from KSFO to KSAN and have experienced NO CTD. Maybe the version I was using was outdated or corrupted? I hope this truly fixed my issue. Also, this might help anyone else with a similar issue. Please don't turn this into a MSFS2020 vs. MSFS2024 debate. 😉

i913900KF (5.8GHz) | Case: Fractal PopAir RGB I Gigabyte Z790 UD AX| MSI Gaming RTX 4070Ti Super 16GB | Kingston Fury Beast 64GB DDR5 5200Mhz | SOLIDIGM P41 Plus 2TB NVMe M.2 SSD | Samsung SSD 870 EVO 2TB | Thermalright Frozen Notte 240 MM Liquid Cooling | LG EVO 42" Monitor 3840 x 2160 120Hz | Honeycomb Alpha & Bravo | Logitech G Pro pedals | Tobii EyeTracker | 850W Thermaltake 80+ GOLD |

Just curious if you're in the su4 beta. I dont have vds installed I use that scenery a few times during the beta and got a ctd. Probably why i did 😜

7800+4090+64ram

Just Flight RJ, 146 and F28, Piper Arrows ---A2A Aerostar and Comanche---Black Square Starship, Duke(s), TBM, Bonanza/BaronV2, KingAir---FSReborn FSR500---COWS Da42---FX P180, HJet & VJet---FlySimWare Chancellor and LearJet---FlightSimStudio EMB175 &P2006T---Fenix 320---PMDG DC6, 737(700+900), 777---C22J---Milviz Cessna 310 & Porter---SimWorksStudios Kodiak, PC12, Zenith & RV14---BigRadials Goose---IndiaFoxEcho MB3339+F35.

 

  • Author
4 minutes ago, Sonosusto said:

Just curious if you're in the su4 beta. I dont have vds installed I use that scenery a few times during the beta and got a ctd. Probably why i did 😜

No, still SU3, but may be worth a try. I may be wrong, but I believe Flightbeam sceneries require the noolaero VGDS module installed to function properly.

 

Edited by TomCYYZ

i913900KF (5.8GHz) | Case: Fractal PopAir RGB I Gigabyte Z790 UD AX| MSI Gaming RTX 4070Ti Super 16GB | Kingston Fury Beast 64GB DDR5 5200Mhz | SOLIDIGM P41 Plus 2TB NVMe M.2 SSD | Samsung SSD 870 EVO 2TB | Thermalright Frozen Notte 240 MM Liquid Cooling | LG EVO 42" Monitor 3840 x 2160 120Hz | Honeycomb Alpha & Bravo | Logitech G Pro pedals | Tobii EyeTracker | 850W Thermaltake 80+ GOLD |

  • Author

Of note as well, I had no CTD regarding my flight mentioned above, if that's any consolation.

 

i913900KF (5.8GHz) | Case: Fractal PopAir RGB I Gigabyte Z790 UD AX| MSI Gaming RTX 4070Ti Super 16GB | Kingston Fury Beast 64GB DDR5 5200Mhz | SOLIDIGM P41 Plus 2TB NVMe M.2 SSD | Samsung SSD 870 EVO 2TB | Thermalright Frozen Notte 240 MM Liquid Cooling | LG EVO 42" Monitor 3840 x 2160 120Hz | Honeycomb Alpha & Bravo | Logitech G Pro pedals | Tobii EyeTracker | 850W Thermaltake 80+ GOLD |

2 hours ago, TomCYYZ said:

No, still SU3, but may be worth a try. I may be wrong, but I believe Flightbeam sceneries require the noolaero VGDS module installed to function properly.

 

Good to know. I guess I didnt RTFM again... 🤣  Like the first time I fired up the Bae146. 

7800+4090+64ram

Just Flight RJ, 146 and F28, Piper Arrows ---A2A Aerostar and Comanche---Black Square Starship, Duke(s), TBM, Bonanza/BaronV2, KingAir---FSReborn FSR500---COWS Da42---FX P180, HJet & VJet---FlySimWare Chancellor and LearJet---FlightSimStudio EMB175 &P2006T---Fenix 320---PMDG DC6, 737(700+900), 777---C22J---Milviz Cessna 310 & Porter---SimWorksStudios Kodiak, PC12, Zenith & RV14---BigRadials Goose---IndiaFoxEcho MB3339+F35.

 

10 hours ago, TomCYYZ said:

I had version 7.0.3 version of the noolaero-module-vgds installed, so I went to the Flightbeam website and found a newer version, 8.0.0 and updated the module (Flightbeam uses this Visual Docking system in their sceneries).

So the culprit is more the noolaero-module-vgds than the FlightBeam KSFO? I use the scenery as my benchmark area but I don't have installed the VGDS module as I'm flying from Signature FBO 😉

Vincent B.
Check my free MSFS sceneries : https://flightsim.to/profile/vbazillio/trending and my hardware configuration.

  • Author
13 hours ago, vbazillio said:

So the culprit is more the noolaero-module-vgds than the FlightBeam KSFO? I use the scenery as my benchmark area but I don't have installed the VGDS module as I'm flying from Signature FBO 😉

I assume that, since I could never get a full flight started with Flightbeam KSFO loaded. Last night I also loaded PACSim KSLC with which I always had a CTD in MSFS2024 The flight was a successful one. However, KSLC is a MSFS2020 product only, NOT MSFS2024 Native (PACSim have not officially updated their Airports to MSFS2024). I did notice though, I had an FPS drop of about 40% with stuttering using the KSLC scenery, possibly not fully optimized for MSFS2024. PACSim recommend using noolaero-module-vgds as well. 

i913900KF (5.8GHz) | Case: Fractal PopAir RGB I Gigabyte Z790 UD AX| MSI Gaming RTX 4070Ti Super 16GB | Kingston Fury Beast 64GB DDR5 5200Mhz | SOLIDIGM P41 Plus 2TB NVMe M.2 SSD | Samsung SSD 870 EVO 2TB | Thermalright Frozen Notte 240 MM Liquid Cooling | LG EVO 42" Monitor 3840 x 2160 120Hz | Honeycomb Alpha & Bravo | Logitech G Pro pedals | Tobii EyeTracker | 850W Thermaltake 80+ GOLD |

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.