1 hour 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.

 

 

Hi,
Offtopic:
How do you make the screens in the cockpit so clear? i can not read mine in the NGXu. its washed out.
thanks for an short tipp.

I have not seen a sim that on release some users find that they have a problem, and yes the same will happen to you know what.

I was checking out the guru3d forum yesterday and noticed that we (nVidia users) don't really have a completely DX12 compatible driver yet. Seems that the 50 ver drivers will be a big step forward concerning DX12.  

That sounds like one way forward

xxd09

 

4 hours ago, xxd09 said:

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

 

Have a look here and try my settings as a starting point..

 

4 hours 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.

 

 

Any tips?  Great video.  Incredibly smooth!

4 hours ago, OzWhitey said:

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

<...>

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!

The constant crashing and hanging on AMD cards with even a fresh install and default planes is kinda showstopping for me. Released without proper testing, as in not even tested once on AMD cards. Sounds pretty premature to me.

8 minutes ago, Prpn said:

The constant crashing and hanging on AMD cards with even a fresh install and default planes is kinda showstopping for me. Released without proper testing, as in not even tested once on AMD cards. Sounds pretty premature to me.

GPUs are abstracted hardware, so it doesn't matter what the GPU card is, so long as it complies with the system. DX requires that all GPUs are capable of the common set of instructions or they are not compatible. Something is wrong with your AMD GPU or the drivers or something else such that it does not perform as expected. That's between AMD and Microsoft, LM could do nothing about it, they won't be releasing an AMD specific codebase and an Nvidia specific codebase, just one DX specific codebase is all they can do.

Edited June 15, 20205 yr by SteveW

18 minutes ago, Prpn said:

The constant crashing and hanging on AMD cards with even a fresh install and default planes is kinda showstopping for me. Released without proper testing, as in not even tested once on AMD cards. Sounds pretty premature to me.

Yes, AMD cards have often been a problem with Microsoft/ESP sims. I know it's not much help now, but I would never advise a flight simmer to buy anything but NVidia. AMD may look good, but "it's a trap".

I know nothing about AMD video cards (apart from the fact that they lead to sadness and frustration on flightsim forums), so I don't know how they compare to the LM official recommendation:

"8 GB + (e.g. NVIDIA GeForce GTX 2080 Ti)"

If I was LM, I probably would have specified that the sim had not been tested with AMD (if that's the case).

I do wonder what percentage of the simmers with CTD problems are running AMD.

Edit: I see Steve posted at the same time, but perhaps not with the same conclusion!

 

 

Edited June 15, 20205 yr by OzWhitey

I've learned from my 30+years of simming that tinkering and adding new features is a  form of addiction for many of us. So, even when in a beta and  the developer cautions us, the desire to install it is greater than the risk of frequent crashes and lots of headaches.

P3D, like fsx, may at some point reach its end of life vis-a-vis the initial technology. Too many bugs and too much patching up.

This is where MIcrosoft might have been smart. Abandon( pretty much) fsx, and start from scratch. A hard lesson learned by Dovetail with Flight sim world.Eventually Lockheed may go excusively to its military clients, once it realizes that the needs of military flight sim clients differ from our needs.

tc

9 minutes ago, SteveW said:

 Something is wrong with your AMD GPU or the drivers or something else such that it does not perform as expected. That's between AMD and Microsoft, LM could do nothing about it

Stating something like this with such certainty is fun but meaningless. Meanwhile both Nvidia and AMD users see the same kind of DXGI hang ups and I get the distinct impression that this is a LM code issue, with Nvidia drivers simply being more forgiving. Example, the PMDG 747 view switching issue. Outright crash on many AMD cards, and I've seen a lot of users reporting it can take a long time on Nvidia cards as well. My guess is, error in code being handled more gracefully by one card than the other. And if you only ever develop for one specific manufacturer and not even testing it a single time on any other card, you get this kind of half-*cheeked* public beta job.

1 minute ago, Prpn said:

Stating something like this with such certainty is fun but meaningless. Meanwhile both Nvidia and AMD users see the same kind of DXGI hang ups and I get the distinct impression that this is a LM code issue, with Nvidia drivers simply being more forgiving. Example, the PMDG 747 view switching issue. Outright crash on many AMD cards, and I've seen a lot of users reporting it can take a long time on Nvidia cards as well. My guess is, error in code being handled more gracefully by one card than the other. And if you only ever develop for one specific manufacturer and not even testing it a single time on any other card, you get this kind of half-*cheeked* public beta job.

My statement about GPUs is a truism. I can't help you any more with that.

7 minutes ago, Prpn said:

 if you only ever develop for one specific manufacturer 

You have to understand the meaning of the term 'Abstract'. If you follow my post you should have learnt that there's no way to target specific manufacturers in Windows. So sorry if you don't understand the technical detail, but that's the truth of the matter. 

4 hours 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.

 

 

Hi Tadeu, where you flying online in this video?,if not, how did you make your ai (KLM 777) to make that precise pushback. Great video by the way!

For those wondering about hardware abstraction:

In Windows, any manufacturer can make a DX12 capable graphics card, but that must comply with the DX12 system. The card would come with a driver specifically written for that GPU so that it appears to any software the same as everyone else's GPU card. That way a program is written to target the graphics subsystem without knowing what that hardware is.