I have a reasonable setup

i7-8700 Coffee Lake 3.7- 4.7GHz

Geforce RTX 2080 Ti

64 GB DDR4 3000 mhz

Win 10 on a SSD

Flight sims on hard disks 

Really enjoying the new Orbx sceneries but

A smooth  flight with P3D v4.5 hf2 but jerky in P3D v5 hf1
P3D v5 is like this even in default mode -in fact shifting sliders/frame rates  makes little difference 

Must be my setup but what?
xxd09

PS XPlane 11 flies beautifully too

 

 

 

Edited June 16, 20205 yr by w6kd
Title edited for congruence with post

I have said it many times.. watch your P3D settings under V5, they are not the same as V4. So you cannot just take all the same sliders settings under V4.5 and make them the same with V5.

V5 is a new engine and the settings have changed.. instead start from a low setting and move them up slowly until you get a balance between performance and visuals. Having said that HF2 for V5 is on the making to address issues many people are experiencing with V5.

S.

48 minutes ago, xxd09 said:

A smooth  flight with P3D v4.5 hf2 but jerky in P3D v5 hf1
P3D v5 is like this even in default mode -in fact shifting sliders/frame rates  makes little difference 

Must be my setup but what?
 

Your post title should be "I probably have a problem with my setup" then, rather than the one you chose! 🙄

Performance of v5 with your graphics card - 2080Ti, the same one I use - should be substantially better than v4.5. First P3D version I can get reliably smooth performance with VR and complex addons. Turn off EA (particularly godrays), in fact take your sliders back to default and work up from there. Again, performance is significantly better than v4.5 thanks in part to DX12 and this should be particularly noticable with a cutting-edge graphics card (whilst you should have no problems with EA on a 2080Ti, you can still get into trouble with the wrong slider settings).

To answer the clickbait title, by the way: the point of v5 is that it is the next step of the iterative process that is Prepr3d. In particular, it's building on the 64-bit architecture of v4 to move closer to a next-gen sim by further modernizing the engine. This is bound to cause some teething problems, but the sim with its new visuals looks a whole lot better than V4/v3/v2/v1. 

 

The only showstopper that I can remember from the release version was the invisible walls, and "showstopper" is an overstatement.

For me, it's (almost) completely replaced v4.5 for the past 2 months, 1 day of flying, and I've been sim flying since its release more than I ever have before in my life. In fact, I was mainly flying X-plane before v5 was released, so it's been good enough to make me put that sim back in the hangar and return to the P3D fold.

In short, I think the argument that it was released prematurely is overstated, as a whole bunch of us are very happy that Lockheed Martin released it when they did!

I think that v5 is intended as a means to move their simulation engine forward and maintain backward compatibility and we do not have to re-learn everything.

Doing this meant that there would be problems emerging, we knew that. Many problems would be hard to spot with the diversity of addons and plug-ins in general use.

We must face the facts; the platform is far too open to expect that a small select group test all the functions and parameters fully enough for a bug free first release. Yet the platform remains just as open; to continue with the opportunity for the richness of development we all wanted without re-establishing techniques from the ground up.

So we got the new sim, it arrived sooner rather than later. This could be seen as a knee-jerk reaction to the proximity of forthcoming new flight simulators, that's merely debatable. There is a timeline for LM Prepar3D that has been interjected by other news arriving during those times.

The way to get things going with this platform was to allow the community to test it out and move on from this experience. Version five continues the trend of improvements we all hoped for. HF1 arrived very quickly to address major issues arising, so that our flights could continue more or less OK. HF2 hopefully will largely address the remaining problems encountered as we report our findings.

We can recognise this work and support the ways chosen. Those that are OK with v4 but find v5 too much hassle should continue with v4 for now.

To join in with the evolution of v5, any problems encountered with v5 should be properly determined whereby we determine where exactly the fault lies - by elimination. I would very much like to see, on AVSIM forums, more expertise showing in the art of problem solving. Start with stock simulator and move forward from a working setup before installing plug-ins and addons, no matter how 'compatible' they are supposed to be.

Actually took me a few weeks to get in to the point. All my nvidia inspector settings for V4 were useless and giving me GTX 1660 Super a lot of hung messages and CTDs. 

I use a 60hz monitor and that's the tricky part. Last night after a lot of testing I finally get rid of stutters and now I'm having an amazing experience with v5 and NGXu as you can see on link below.

 

 

Edited June 15, 20205 yr by Tadeu Primo
link

1 minute ago, Tadeu Primo said:

All my nvidia inspector settings for V4 were useless and giving me GTX 1660 Super a lot of hung messages and CTDs. 

Thats the main problem: Nvidia driver can't see the difference between V4 and V5, so some people run into problem with their v4 tweaks running on v5.

I remain at a bit of a loss when default settings of P3D v5 don’t work
Thanks for all the replies

I will go below default settings and try that

xxd09

 

1 minute ago, SteveW said:

I think that v5 is intended as a means to move their simulation engine forward and maintain backward compatibility and we do not have to re-learn everything.

Doing this meant that there would be problems emerging, we knew that. Many problems would be hard to spot with the diversity of addons and plug-ins in general use.

We must face the facts; the platform is far too open to expect that a small select group test all the functions and parameters fully enough for a bug free first release. Yet the platform remains just as open; to continue with the opportunity for the richness of development we all wanted without re-establishing techniques from the ground up.

So we got the new sim, it arrived sooner rather than later. This could be seen as a knee-jerk reaction to the proximity of forthcoming new flight simulators, that's merely debatable. There is a timeline for LM Prepar3D that has been interjected by other news arriving during those times.

The way to get things going with this platform was to allow the community to test it out and move on from this experience. Version five continues the trend of improvements we all hoped for. HF1 arrived very quickly to address major issues arising, so that our flights could continue more or less OK. HF2 hopefully will largely address the remaining problems encountered as we report our findings.

We can recognise this work and support the ways chosen. Those that are OK with v4 but find v5 too much hassle should continue with v4 for now.

To join in with the evolution of v5, any problems encountered with v5 should be properly determined whereby we determine where exactly the fault lies - by elimination. I would very much like to see, on AVSIM forums, more expertise showing in the art of problem solving. Start with stock simulator and move forward from a working setup before installing plug-ins and addons, no matter how 'compatible' they are supposed to be.

The platform - in particular, the graphics engine - needed to move forward. I'm pretty impressed by what LM has been able to do while still maintaining backward compatibility.

A new or substantially modified engine is inevitably going to cause problems on some combinations of hardware and addons. v4.5 was the end of a 3-year developmental run, the era of v5 is just beginning.

Whilst I'm looking forward to HF2, I am happy with the sim in its current state, and was impressed by how quickly LM rolled out HF1.

As you say, a problem-solving approach to CTDs is the way to go - start by going back to the basics (fresh/clean install of client at least, with default sliders), and progressively move sliders or add addons until a problem is encountered. 

13 minutes ago, Tadeu Primo said:

Actually took me a few weeks to get in to the point. All my nvidia inspector settings for V4 were useless and giving me GTX 1660 Super a lot of hung messages and CTDs. 

I use a 60hz monitor and that's the tricky part. Last night after a lot of testing I finally get rid of stutters and now I'm having an amazing experience with v5 and NGXu as you can see on link below.

 

 

It looks really great, nice work.

But for those playing at home, please don't blame LM if your sim crashes when you're using a non-compatible aircraft. I'm pretty sure that a fair percentage of the crashes people get angry about are due to dubious tweaks and/or addons.

Glad you're having fun, Tadeu. 🙂

Btw, there's absolutely nothing wrong with flying a non-compatible aircraft, I do enjoy a bit of test piloting myself. Just remember to blame yourself when the BSOD appears!

Joe mentioned a point I always stress: Default the Nvidia Profiles Global and Prepar3D.exe before moving on. Don't forget to Restore/Apply those profiles guys!

Another word of advice: There are crashes that you might only see with add-ons that those add-on devs cannot fix. E.g., PMDG doesn't know why users are sometimes getting DXGI errors when switching to and from the VC. They're waiting for HF2. 

Nvidia profiles will conflict with V5. The new DX12 performance algorithms introduced by LM engineers might conflict with nvidia settings introduced by you trying to push for other settings.

It is recommended to wipe those envidia profiles and let P3D to choose the best for the rendering.

Regards,

Simbol 

14 minutes ago, simbol said:

Nvidia profiles will conflict with V5. The new DX12 performance algorithms introduced by LM engineers might conflict with nvidia settings introduced by you trying to push for other settings.

It is recommended to wipe those envidia profiles and let P3D to choose the best for the rendering.

Regards,

Simbol 

So setting preferred max performance NCP not needed to be set anymore?

and also image sharpening not advisable  to use?

leave all as default?

thanks 

mike

4 minutes ago, mikeymike said:

So setting preferred max performance NCP not needed to be set anymore?

and also image sharpening not advisable  to use?

leave all as default?

thanks 

mike

Clear your NCP profiles, test V5 withouth any.. then add slowly one NCP settings at a time.

The point is not to asume your old profile NCP will just works. You need to try first the P3D embedded anti-aliasing, frame limiting, V-sync settings, etc.. They were codded inside the engine for a reason and having an external software fighting with these settings cannot achieve any positive results.

S.

Edited June 15, 20205 yr by simbol