1 hour ago, RALF9636 said:

I never had a CTD with 4.5 and I don't see any thread an avsim about widespread CTD-issues of users of 4.5.

So an older version of an Flightsim is taxing the System (which has stayed the same) less than an newer version with advanced engine. Surprise.

The v5 stock scenery is double the size of v4, and v5 uses DX12 whereas v4 is DX11 - so these simulators do not compare.

has anybody noticed more jagged lines lately?  Seems like it came around the time I moved up to win 2004.  It seems anyway.  Still running 2 SSAA

Another reason to make sure the NCP is defaulted.

no not for me.  8MSAA seems to be doing better than the 2SSAA i was using

14 hours ago, johncott said:

I do know if you have an older graphics card that only has 4GB of ram, you're going to have issues.  One fancy plane with hi-res PBR textures and sliders towards the high side, you will run out of VRAM and a CTD. in this case is LM the problem or your computer?

John C.

It’s not a “bug” it’s simple mathematics. “Hi Res PBR textures” consume VRAM. Setting graphics sliders to high will consume even more. DX-11 would handle that by switching to (slow) system memory if all VRAM was consumed. DX-12 will crash if a call for additional VRAM goes even one byte over what is installed on the GPU.

If you try to store 10 gallons of water in a 5 gallon bucket and find it won’t fit, it’s not because the bucket is “defective”. It simply means that you need to get a bigger bucket. Any DX-12 game is going to require a GPU with as much hardware VRAM as possible.

As Rob Ainscough has pointed out, GPU manufacturers are doing consumers no favors by the markups they apply to the cost of cards with higher amounts of VRAM. The actual cost of hardware chips to add 2 or 3 GB of VRAM to an existing GPU is well below $100, but the price increase for a GPU with 8 vs. 11 GB VRAM is typically measured in the hundreds of dollars.

Aircraft and scenery developers play a role too. In V5 it is now more important than before to optimize the use of textures whenever possible. In DX-11 V4, developers could simply make every texture in their product 4096, with no danger of crashing the sim if VRAM was exhausted - it would simply result in stuttering or frame rate drop. That’s no longer the case.

The V5 PMDG 747 installed on my system only uses 500 KB more VRAM than the default F35 (2.7 vs. 2.2).

The new V5 version of the Leonardo Maddog uses 2.9 GB (with the optional 2048 cockpit textures).

Similar “reasonable” VRAM use for the A2A Comanche and Bonanza.

The TFDI 717 by contrast uses 4GB just for the aircraft alone, and 6 GB if TrueGlass and RealLight are enabled. Definite need for optimization there!

A DX12 program keeps note of the VRAM budget and does not load anything larger than what's left in the budget. Those with galloping VRAM overuse should check the addons they are using since some graphic objects can appear to have smaller size than they are.

Also a DX12 VRAM budget can be made up from Shared memory if it likes.

Imagine that Prepar3D keeps on blindly loading up stuff even though the memory is all used up?

If it does that by mistake it will take LM most of 5 seconds to fix it, but a lot longer to scroll through the code to find the place where they missed out the call to current memory use.

11 hours ago, Chapstick said:

Sounds like you’re unaware that the sim has CTD issues even if you do everything right: stock settings, compatible add-ons, adequate hardware, etc. But now you’ve learned something new today! Glad I could help. 

For how many users? This is equivalent to stating that people get poor frame rates with the default settings. Sure, SOME people do.

These discussions go on for a long time, whereby there's little or no elimination of anything, including "compatible addons".

Device hung can be many things, faulty hardware, overstretched overclock, corrupt texture. CTDs usually come from adding DLLs or gauges to the simulator.

So best to start with knowing that on good hardware with known stability there's no CTDs, or device hangs.

Maybe there is with a particular place or aircraft that gives an error.

So by elimination that means to fly elsewhere and with another aircraft on a stock system. If it can be found that there is a fault in a stock scenery file (I found at least one place) or a fault in a stock aircraft, then that would be useful for LM to know that.

 

Anyone who was with P3D when version 4 came out will remember that it took a while to iron out the many crashes and other issues that affected it. Well think v5 as a new born baby that needs to develop to reach maturity. When I bought it I knew that  there would be some problems and lI had no  had no crashes with some payware ga aircraft, even managed to do a flight with a pmd747,which lasted all of one hour before it crashed. I can see people complaining about the money they paid, but that cost will stay put during the many versons of v5. If you have the latest v4.5 enjoy that as it's working splendidly and you can continue to enjoy your addons until v5 gets updated and performs better. Loads of developers are very likely updating those addons that can be fully compatible with v5, that will take some time. Take a deep breath and have a Martini on the rocks.