Sign in to follow this  
WebMaximus

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

Recommended Posts

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?

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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!

Share this post


Link to post
Share on other sites

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/

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

  • Upvote 1

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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:

Share this post


Link to post
Share on other sites

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:

You can still save it, just don't make it the default. From the startup screen, just press on "Load" and select your saved file rather than starting a new flight from scratch. Works for me every time.

Share this post


Link to post
Share on other sites

You can still save it, just don't make it the default. From the startup screen, just press on "Load" and select your saved file rather than starting a new flight from scratch. Works for me every time.

 

OK, thanks.

 

I thought it was using a saved situation that was a no-no but great if it's OK to use a saved situation as long as you don't make it the default situation.

Share this post


Link to post
Share on other sites

To be clear about Default flight files with P3D:

 

1. For many aircraft, saved flight files can only be loaded reliably, with all systems operating, once the sim has started up. So to always successfully load a saved flight we must allow the sim to be started up first.

 

2. If the sim has started (without a saved flight specified as a command parameter e.g. from a shortcut or batch), whether going into the sim or the scenario screen, by definition the Default flight has been loaded.

 

3. If the default flight is not a saved flight with a stock aircraft, there may be subsequent problems loading a saved flight if the sim completes the startup.

Share this post


Link to post
Share on other sites

Where to blank out the default flight ??? ..... I have erased the line SITUATION that is inside  [uSERINTERFACE] in Prepar3D.cfg and now when I open P3D the default flight is still charged

 

Thanks

J J Gómez Prieto

IVAO 142928

Share this post


Link to post
Share on other sites

Where to blank out the default flight ??? ..... I have erased the line SITUATION that is inside  [uSERINTERFACE] in Prepar3D.cfg and now when I open P3D the default flight is still charged

 

Thanks

J J Gómez Prieto

IVAO 142928

 

Save a new default flight over the old one.

Share this post


Link to post
Share on other sites

OK ......  thanks ..................Steve and Kyle ... what I have done is :

 

- Check  like Default the " Prepar3D Default " ...  (C:\Users\My user\AppData\Local\Lockheed Martin\Prepar3D v3)

 

- Modif Prepar3D.cfg with SHOW_SCENARIO_WINDOW=0 ( I'll tell you why later )

 

Then when I run Prepar3D v3.1 .....  the program go inside it and show the aircraft and scenery by default  ...... in this moment I go to Scenery/Load and select one saved with PMDG B739 aircraft ... then OK and the aircraft and scenery change without problem, but after  20 seconds waiting I can not make any change because it seems like if the mouse were been deactivated; I can use F1 to F12, all joystick functions, but the mouse is not active anymore.

 

As I told before I have Modif Prepar3D.cfg with SHOW_SCENARIO_WINDOW=0 instead SHOW_SCENARIO_WINDOW=1 because if I do so when in the main window I push OK immediately the simulator crashes

 

Regards

Share this post


Link to post
Share on other sites

As I told before I have Modif Prepar3D.cfg with SHOW_SCENARIO_WINDOW=0 instead SHOW_SCENARIO_WINDOW=1 because if I do so when in the main window I push OK immediately the simulator crashes

 

You may need to find the source of this issue then, because this is absolutely critical to avoid the issue of not being able to use the switches in the VC.

 

EDIT:

Full names in the forum, please - first and last.

Share this post


Link to post
Share on other sites

OK Kyle .... this is the main problema ..... to find that issue ..... I have that problema from v3.1 versión of P3D .... never before ... and, at the moment I have done ALL .... don't know what to do more ... surely I'll come back to v3.0

 

Regards and sorry for the omission of my name

 

Juan José Gómez Prieto

IVAO 142928

Share this post


Link to post
Share on other sites

Juan, I am aware of some that have problems with the 3.1 upgrade. Their solution was to remove P3D and install the full P3Dv3.1 program. I had no problem just doing the client update but not everyone is so lucky. The symptoms are verry similar to what you report.

Share this post


Link to post
Share on other sites

Thanks Dan, I had decided to go back to 3.0 but with your info I think that 3.1 deserves another opotunity  ...... and I am very obstinate.

 

Juan José Gómez Prieto

IVAO 142928

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