Can't start with a default flight using the NGX in P3Dv3.1

[WebMaximus 372]

OK, so here comes next issue/question since I replaced P3Dv2.5 with P3Dv3.1.

 

If I try to start P3D using a default flight using the NGX P3D won't start. I see the logo showing up and then I see the progress bar for a split second saying it's loading stuff but then I'm back at the desktop and nothing happens. Checking active processes using Task Manager I see Prepar3d.exe running.

 

The only way to make P3D start normally again is to manually edit Prepar3D.cfg blanking out the default flight and setting SHOW_SCENARIO_WINDOW=1 so I get a chance to load my flight from the scenario screen. Funny thing is loading the very same flight this way via the scenario screen works just fine...it's only when I set that same flight to be the default flight and with SHOW_SCENARIO_WINDOW=0 it doesn't work. Also, this is only true for a saved flight with the NGX. If I do the same thing with one of the stock aircraft everything works just fine.

 

Anyone else seen this?

[downscc 1,327]

Right, until LM fixes this the only way I start a PMDG session in P3D is from the set scenario screen. I have dozens of scenarios saved, typically a PMDG aircraft sitting at the gate in a turn around configuration, so I am either creating a new or loading an existing scenario.

[WebMaximus 372]

OK, good to know it's not just me.

 

Thanks Dan!

[Richard Sennett 2,499]

OK, good to know it's not just me.

 

Thanks Dan!

 

Keep in mid no vc lighting on the ground also if you dont start at night in scenario screen - LM issue

[WebMaximus 372]

Ok, another reason to fly during daytime. I always preferred that.

 

I'm honestly surprised how issues like these still exist in a RTM version...feels more like issues found in version 1.0 rather than 3.1

[downscc 1,327]

Keep in mid no vc lighting on the ground also if you dont start at night in scenario screen - LM issue

So far, my ground light splashes are working during daylight in v3.1 but I've only made a few daytime starts. Even the dome light works in the 777 yay!

[Richard Sennett 2,499]

Ok, another reason to fly during daytime. I always preferred that.

 

I'm honestly surprised how issues like these still exist in a RTM version...feels more like issues found in version 1.0 rather than 3.1

 

So far, my ground light splashes are working during daylight in v3.1 but I've only made a few daytime starts. Even the dome light works in the 777 yay!

 

 

This should clear things up for you

 

http://www.avsim.com/topic/480329-vc-runway-lights-not-working/

[WebMaximus 372]

Thanks for the info but I still find it strange how issues like these make it all the way to a RTM version.

 

Surely people in the beta team found the same issues and still the version is released without first fixing the problems.

[Richard Sennett 2,499]

Thanks for the info but I still find it strange how issues like these make it all the way to a RTM version.

 

Surely people in the beta team found the same issues and still the version is released without first fixing the problems.

 

I am pretty sure they know about it but not on the priority list at the moment - give it time it will be sorted out - cant be happier how far P3D has come along

[JRBarrett 3,034]

Thanks for the info but I still find it strange how issues like these make it all the way to a RTM version.

 

Surely people in the beta team found the same issues and still the version is released without first fixing the problems.

I'm not sure it's really a P3D problem as much as it the nature of an ultra-complex aircraft like the NGX or 777.

 

PMDG's own guidance has long been that you should NOT set either the NGX or the 777 as a default flight in either FSX or P3D - that doing so is prone to cause problems.

 

Consider: if you own either the NGX or 777, you will be aware that once loaded, the aircraft goes through a rather long countdown while all aircraft systems fully initialize. I think that what is happening when you have either PMDG aircraft set as the the "default" flight, is that you are trying to initialize the aircraft systems before all of the components of the underlying sim ITSELF are fully initialized - which could lead to a variety of instabilities that could cause poor performance or a CTD.

 

It would kind be like trying to put on your socks after you have already put on your shoes. P3D is a very complex piece of software, and so is the NGX/777. Trying to bring them both online at the same time is probably not a good idea. Waiting for the scenario screen before loading the PMDG aircraft would seem to be the best practice, as once that screen appears, you know that the simulator itself if fully initialized to the point where it is ready for the aircraft to be loaded.

[scandinavian13 5,192]

If I try to start P3D using a default flight using the NGX P3D won't start.

 

This is something we've discouraged since the 747-400 in FSX. It is also discussed in both FSX and P3D versions of the Intro Manuals for the 737 and 777.

[WebMaximus 372]

I am pretty sure they know about it but not on the priority list at the moment - give it time it will be sorted out - cant be happier how far P3D has come along

I fully agree it's great we have someone who is continuously developing the simulator and I'm sure investing in the project twice shows that.

 

What I found a bit strange with these issues is the fact that they are new. We're not talking about some minor issues that have always been there and that might get fixed eventually like the unrealistic friction.

 

That you now can't use a default flight with the NGX is not a big thing, I'm sure I can learn to manually load the flight from the scenario screen. However having the landing lights misbehaving OTOH I don't consider as a minor thing and that one is new and again I'm surprised why you don't address such an issue before you choose to release and especially when you know the issue hasn't always been there but has recently been introduced by you.

This is something we've discouraged since the 747-400 in FSX. It is also discussed in both FSX and P3D versions of the Intro Manuals for the 737 and 777.

Thanks for enlightening me Kyle but I have a couple of thousands of hours in the NGX where I've always loaded a default flight with zero issues until now so clearly something changed in version 3.x.

I'm not sure it's really a P3D problem as much as it the nature of an ultra-complex aircraft like the NGX or 777.

PMDG's own guidance has long been that you should NOT set either the NGX or the 777 as a default flight in either FSX or P3D - that doing so is prone to cause problems.

Consider: if you own either the NGX or 777, you will be aware that once loaded, the aircraft goes through a rather long countdown while all aircraft systems fully initialize. I think that what is happening when you have either PMDG aircraft set as the the "default" flight, is that you are trying to initialize the aircraft systems before all of the components of the underlying sim ITSELF are fully initialized - which could lead to a variety of instabilities that could cause poor performance or a CTD.

It would kind be like trying to put on your socks after you have already put on your shoes. P3D is a very complex piece of software, and so is the NGX/777. Trying to bring them both online at the same time is probably not a good idea. Waiting for the scenario screen before loading the PMDG aircraft would seem to be the best practice, as once that screen appears, you know that the simulator itself if fully initialized to the point where it is ready for the aircraft to be loaded.

I'm sure you're right about how complex the NGX is and how that is the reason why you can't load it in a default flight but like I just wrote in another reply this is new in version 3 of P3D. Using the very same version of the NGX in P3Dv2.5 doesn't show this behavior.

[pete_auau 1,152]

Than you were lucky than, as written in the introduction manual is what to use as the default plane

[scandinavian13 5,192]

Thanks for enlightening me Kyle but I have a couple of thousands of hours in the NGX where I've always loaded a default flight with zero issues until now so clearly something changed in version 3.x.

 

As Peter said, you've just been getting lucky. If you've seen quriky issues here and there (and/or OOMs), then I can almost guarantee they were related to your default aircraft.

 

I avoid it regardless of the simulator, with the exception of X-Plane.

[WebMaximus 372]

OK, well...will follow the recommended procedure from now on. Reason I've been using a default save file has been to not having to remember at what gate I parked on last flight :wink: