Jump to content
Sign in to follow this  
Timberleaf

CTD using Windows 11 + FS2Crew FBW Project

Recommended Posts

I have isolated the CTD's to this combination: 1) the upgrade to Windows 11 and 2) FS2Crew FBW Project. This combo is causing the sim to crash inconsistently - doesn't crash at the same point in time each instance of the sim. I can't yet isolate whether it is a driver, the command center, the app, the sounds, etc. All I know at this time is by disabling the FS2Crew FBW Project app and command center, the sim doesn't crash using FBW A320 solo

If I find out more, I will report it (assuming you don't already know about this). Before the upgrade to Windows 11 this didn't happen, not even once, for me. I hope this helps and I look forward to more.


 TimberLeaf Savitri

Share this post


Link to post
Share on other sites

I am using all the above. No CTD on my system. Been using Windows 11 for months now.  I only post this, to let you know that your CTD may be something unique to your system. 

 

 


Rick Verhallen

i9-10900K OC to 5.2 Ghz | 32 GIG- G.Skill 4000 RAM | Asus ROG Maximus XII Hero Motherboard | Asus RTX 3080Ti |  47" Samsung 4K Monitor I HTC Vive Pro HMD I HP Reverb G2 HMD

Share this post


Link to post
Share on other sites

I've been using Win 11 since it was first released.  No problems here.

FS2Crew basically runs externally from the simulator now.  Generally speaking, it can't cause MSFS to crash because it's run outside of the MSFS process -at least the core of it.

When you get your crash, do you get a dialogue box that says "View details"?

 

Share this post


Link to post
Share on other sites

I don't get any dialog box when the ctd occurs. When I check the event viewer it only points to MSFS and D3D11.dll. This is the only lead. Considering that this only occurs with the FS2Crew in the back running, I am trying to figure out why.

I am not pointing and fingers, no blame, just want it "right" so I can continue using the FS2Crew with the FBW plane. All I can do is report what I know, even if the two are not related. I pray you will be smarter than I and be able to think about what I haven't thought of yet.

 

EDIT: I booted up today with the same airport, same settings, with one difference. Instead of loading into a stand, I loaded into a gate. The flight was flawless. I can't explain it, it just worked.

Edited by Timberleaf

 TimberLeaf Savitri

Share this post


Link to post
Share on other sites

You could also go into Windows' Event Viewer, try to reproduce the CTD and see if Event Viewer has anything logged...also I think MSFS maybe has some log or even SimConnect, probably something goes wrong with SimConnect at a certain situation that crashes the entire sim.

Cheers,

Manuel

Edited by Manuel82

spacer.png

Share this post


Link to post
Share on other sites

Perhaps it is relative to my system. It makes no sense to me, though I am grateful it worked this morning flawlessly. Hopefully it will continue.

I also noticed in the pop-up FS2Crew that the WASM is v1.0. Is there an update to that? (Perhaps that might be a clue to my CTD experiences)

Edited by Timberleaf

 TimberLeaf Savitri

Share this post


Link to post
Share on other sites

WASM is still at 1.0.

But why loading at a stand would make a difference for you is odd.

That happens all airports or some 3rd party airport?

Edited by byork

Share this post


Link to post
Share on other sites

It was KMCO, default MSFS. The default gates are all screwed up, and never do you spawn at a gate properly. It is always "wonky" and at odd angles to the gate itself. The scenery is nice, though. So, I thought to just spawn at a stand (where the typical carriers go, UPS, for example). Not accurate in the real world, but something different. At least I was lined up at the parking spot correctly. But, it just wouldn't work right. Regardless, obviously my system is unique. Perhaps something didn't load correctly in the background, and all I needed to do was just restart - again. For the record, I did restart, several times.

I wish I could give you clearer information, or perhaps all of this would make more sense. It is what happened, and if something else pops up that didn't before, or yields a greater insight, I will report back.

I have used your addons for years, and I know you make quality products. I am confident in you which is why I brought this to the "table". I did the best I could to isolate the situation. Perhaps it is all a red herring. If that is the case, I am sorry to have wasted your time. But, grateful for your consideration.


 TimberLeaf Savitri

Share this post


Link to post
Share on other sites

It seems to be working as it should, and as it has, correctly. Nothing new to add. I loaded into KATL and it works. I loaded into KMCO (gate). Works correctly.

Unless something new emerges, I guess this is a non-issue, now. Thanks for your consideration. If this occurs again I'll give you more then.

Thanks, always, for your great addons.

Edited by Timberleaf

 TimberLeaf Savitri

Share this post


Link to post
Share on other sites

I'm having these CTDs as well. I'm still on win10. All drivers and windows are up to date. 

To identify the issue I clean-reinstalled the sim and fbw and made a flight -working OK.

Other add-ons working well as well. Installing FS2CREW FBW, PBE AND RAAS via the FS2CREW manager- CTDs with nothing to explain the error in event viewer ( just a generic fs crash report).

These CTDs happen either when a flight with fbw is loaded or during preflight and sometime I make it to taxi or takeoff and then a CTD. All CTDs has the same characteristic - the sound pauses for a second, comes back and then the whole Sim crashes with no error message.

Please advise.

Edited by Jonathan Poller

Jonathan Poller

Banner_FS2Crew_Bus6.png qw787_banner.png

 

Share this post


Link to post
Share on other sites

It's hard to guess... unlike the FSX/P3D versions of FS2Crew, the MSFS versions of FS2Crew run "outside" the MSFS process.

Never say never with computers, but in theory we can't make MSFS crash because our programs now run externally and separately from MSFS.

I would try this:

1. Make a backup of your community folder.

2. Delete everything non FS2Crew related as means to try to isolate.

Try again.

Also, if you search the MSFS forums in general, you'll see for some users MSFS is a bit of a wild beast.

I've personally never had any issues with MSFS, but others have based on what I've seen in Facebook.  With 1000s of possible driver/hardware/users mods out there, it can be a bit of a house of cards.

Cheers,

Share this post


Link to post
Share on other sites

H, I have the same issue, I recently upgraded to Win11, installed the Product Download Manager then installed FS2Crew/FBWA320/ PBE&RASS. Now MSFS will CTD about a minute into the loading screen! I uninstalled all 3, deleted residue folders, MSFS works fine; reinstalled FS2Crew...CTD, rinse, repeat. I had no issues with Win10,not sure what's going on with Win11?! I hope that you can provide a fix.

Here are the log files

log_file_autostart

20220206 01:01:06.047000: MS Store version file not found - C:\Users\*******\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\EXE.xml
20220206 01:01:06.051000: MS Disc version file not found - C:\Users\*******\AppData\Local\Packages\Microsoft.FlightSimDisc_8wekyb3d8bbwe\LocalCache\EXE.xml
20220206 01:01:06.055000: MS Alpha version file not found - C:\Users\*******\AppData\Local\Packages\Microsoft.KHAlpha_8wekyb3d8bbwe\LocalCache\EXE.xml
20220206 01:01:06.059000: Steam version file exists - C:\Users\*******\AppData\Roaming\Microsoft Flight Simulator\EXE.xml
20220206 01:01:06.063000: Folder does not exist, will not create EXE.xml - C:\Users\*******\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\
20220206 01:01:06.066000: Folder does not exist, will not create EXE.xml - C:\Users\*******\AppData\Local\Packages\Microsoft.FlightSimDisc_8wekyb3d8bbwe\LocalCache\
20220206 01:01:06.070000: Folder does not exist, will not create EXE.xml - C:\Users\*******\AppData\Local\Packages\Microsoft.KHAlpha_8wekyb3d8bbwe\LocalCache\
20220206 01:01:06.073000: XML Validation Check Failed - C:\Users\*******\AppData\Roaming\Microsoft Flight Simulator\EXE.xml (A name contained an invalid character.)

log_file_community_folder

20220206 01:01:06.203000: MS Alpha Version user config not found - C:\Users\*******\AppData\Roaming\Local\Packages\Microsoft.KHAlpha_8wekyb3d8bbwe\LocalCache\UserCfg.opt
20220206 01:01:06.207000: MS Disc Version user config not found - C:\Users\*******\AppData\Roaming\Local\Packages\Microsoft.FlightSimDisc_8wekyb3d8bbwe\LocalCache\UserCfg.opt
20220206 01:01:06.211000: Steam Version user config exists - C:\Users\*******\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt
20220206 01:01:06.215000: Steam Version packages folder - D:\MSFS
20220206 01:01:06.219000: MS Store version user config not found - C:\Users\*******\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt
20220206 01:01:06.222000: FS2Crew package source folder found - C:\Program Files (x86)\FS2Crew Command Center\community_folder\fs2crew-cmd-center
20220206 01:01:06.226000: Copy the FS2Crew folder - C:\Program Files (x86)\FS2Crew Command Center\community_folder\fs2crew-cmd-center
20220206 01:01:06.230000: To the Community folder - D:\MSFS\Community
20220206 01:01:06.463000: Copying of package completed successfully!

log_file_data_proc

20220206 01:01:06.364000: MS Alpha Version user config not found - C:\Users\*******\AppData\Roaming\Local\Packages\Microsoft.KHAlpha_8wekyb3d8bbwe\LocalCache\UserCfg.opt
20220206 01:01:06.365000: MS Disc Version user config not found - C:\Users\*******\AppData\Roaming\Local\Packages\Microsoft.FlightSimDisc_8wekyb3d8bbwe\LocalCache\UserCfg.opt
20220206 01:01:06.366000: Steam Version user config exists - C:\Users\*******\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt
20220206 01:01:06.367000: Steam Version packages folder - D:\MSFS
20220206 01:01:06.368000: MS Store version user config not found - C:\Users\*******\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt
20220206 01:01:06.369000: FS2Crew package source folder found - C:\Program Files (x86)\FS2Crew Command Center\wasm\fs2crew-data-proc
20220206 01:01:06.371000: This package version - 1.0.0
20220206 01:01:06.372000: Installed package version - 1.0.0
20220206 01:01:06.373000: Installed package version already up to date!

 

I've checked and triple checked  exe.xml, even created new ones, I know it's fine because FSUIPC loads fine. Help please

Edited by Red Tails

Dell S2417DG QHD G-SYNC 165Mhz | Gainward Phoenix GS GTX 1080 Ti 11GB | Intel i7 8086K @ 5.2Ghz | Asus Maximus XI Formula  | Corsair  500D RGB  |  Corsair AX860i | Corsair Dominator Vengeance RGB DDR4 32GB 3200Mhz | Corsair H115i Platinum RGB  | Samsung Evo SSD 2 x 1000GB  | WD Black 2 TB | SoundBlaster Z | Track IR 5 | Harmon Kardon HK695  |

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...