Hello - wondering if anyone else has experienced this.

I'm able to run P3D with FS2Crew installed and the QualityWings 787, however when I try to load another plane, or scenario that uses another plane, P3D crashes to the desktop.

I've also noticed that after I crash the plane, P3D freezes and will eventually crash to the desktop and the scenario is not reloaded.

I have other add-ons that I've uninstalled one at a time and the problem only goes away when I uninstall FS2Crew.

Thanks.

You mean when you load a plane other than the 787 from the "free flight" screen P3D crashes?

It's not FS2Crew.  FS2Crew only loads when the 787 loads.  FS2Crew is literally built directly into the aircraft via gauges added to the aircraft's panel.cfg file.

Best,

 

Yes, exactly.  Here is where I'm at right now.

With FS2Crew installed, I go to the free flight screen.  My default scenario is loaded which has the QW 787 loaded.  I select a new vehicle and hit OK and the preview of the new plane disappears and shortly P3D crashes and just disappears.

If I simply uninstall FS2Crew and do nothing else, when I start P3D the same exact way, choosing the same exact other vehicle, P3D starts and runs fine.

I understand the FS2Crew is built into the QW 787, but I don't have to uninstall QW 787, just FS2Crew.

Thanks

Update: I just discovered that the problem also goes away if I just go into the QW 787 and disable FS2Crew, without uninstalling it.

Edited June 22, 20205 yr by dam54

I'm not sure about this one.  It'd odd.

But the default plane in FSX/P3D on the Free Flight Screen should never ever be a 3rd party plane, otherwise you can have loading problems.

It should always be a default plane... like the trike in FSX.

So make your default plane on the free flight screen be a default plane.

Cheers,

 

Edited June 22, 20205 yr by byork

Thanks!

 It works now if I make sure the free flight screen comes up with one of the default scenarios and then load the scenario I want after.

Sounds like something P3D needs to work on as it pretty much negates being able to set up a default scenario to jump right into without having to go through the free flight screen.

Glad you got it sorted 🙂

It was also a FSX thing too.

Basically, never have a complex 3rd party plane as the 'default' plane on startup.  It can cause load problems and weird behavior.

 

 

Well, I spoke a little too soon.

While I'm able to now start out with a default scenario and then choose the QW 787 and have it load fine, I still have the issue where it CTD when the plane crashes.

Again, I'm able to crash in other planes and it reloads the scenario correctly.  If I fly the QW 787 and crash that plane, it does not reload the scenario, but instead stops responding and eventually crashes back to the desktop.  I did the same test I did with the other issue, disabled FS2Crew, start the same default scenario, select the QW 787, take off and crash the plane.  With FS2Crew disabled, it reloads the scenario fine.

There's definitely something weird going on.  It also doesn't make sense to me that I didn't have to uninstall QW 787, just FS2Crew.  Everything works fine QW 787, even loading up a saved scenario as the default using that complex plane worked fine, as long as FS2Crew is not enabled at the time.

Can anyone confirm that they are able to fly the QW 787, crash the plane, and have it reload the scenario after the crash without P3D becoming unresponsive and crashing to the desktop?

I'm really hoping to get this all working together.  I should mention I also have FS2Crew Ultimate Ground Crew, but I've been able to leave that enabled.

Thanks!

I just tried it in P3D v5... took off and deliberately crashed... no problems... the sim reloaded with the F22.

I might suggest disabling Crash Detection... I usually leave it off because it's easy to hit stuff on the ground.

 

Thanks for testing that for me!

I did some more testing on my end to figure out why yours works and mine doesn't.  Here is what I found.

I have been using a "cold and dark" startup and thought maybe that could be the difference between us, so I removed the config entry and allowed it to start up fully powered, and low and behold, it worked, no problem reloading after a plane crash.

Here is the content of my QW787.cfg file when it doesn't work:

IrsAlignSecs=60
MinAptRwyLen=6300
EfBFPlanOverlay=1
ArmPauseAtTod=1
Arm1xAtTod=1
PlayAnnouncements=0
PlayTakeoffCalloutSounds=0
RemoteCdu=1
LoadFuelonAircraftLoad=1
CduAutoCalcVspeeds=1
CduAutoCalcZfw=1
LoadPanelStateonAcLoad=1
PanelState=coldanddark.pnl
calcpayload=1
ArmPauseAtDistFromDest=1

If I simply remove the "PanelState=coldanddark.pnl" entry, it works normally.  And again, with FS2Crew disabled, it also works fine.  So, could there be something between FS2Crew and the coldanddark.pnl state that could be causing the issue?

Thanks!

Again, we don't recommend pre-loaded anything.  

For things to load clean, have default plane on the free flight screen on startup... then when the plane loads, then load the panel state.

FSX/P3D can be a finicky beast... and doing it this way ensures everything loads in the right order.

Cheers,