I have not seen any problem mine works very well and smooth like butter, with plenty of add-ons and all my settings at max ____________________________________________________________________________________________________________ OPERATING SYSTEM: MS Windows 10 Professional | CPU : Intel Core i9-1...

So far it works normally..



OPERATING SYSTEM: MS Windows 10 Professional | CPU : Intel Core i9-10900X 10-Core 3.70GHz (4.5GHz TurboBoost) | MEMORY : 32GB CORSAIR DOMINATOR PLATINUM | GPU : NVIDIA 8GB GeForce RTX 3060 Ti | SIMULATOR : PREPAR3D v5.2

Update for my Post : I just read the post from Poppet solved for me the problem .

Thank you Poppet

I have two drives in my PC . SSD and HHD Drive . My question is if i install P3D V5 on the second drive (HHD)? Because i need the Primary drive (SSD) only for windows

Thank you

Hopefully I'll have a i9 9900K at 5.5 to 5.8 Ghz around early October and will report back on the results from that CPU vs. my i9 7900X at 5.0 Ghz (HT OFF). I've ordered two 2080Ti that are schedule to arrive around early October also ... not sure I understand how Georgio52 is getting a 2080Ti in 1...

In 10 days I will try this rig..

CPU : I7-7800X six core
MEMORY : 32 GB DDR4 Quad
HDD : 512 GB SSD
HDD : 4TB SATA
ASUS X299
PS : 1000 Watts
GPU : GeForce RTX 2080 Ti 11GB

stick to 397.64

I tried this method before with Registry Editor,but the problem with error remains the same for me.. As mentioned above , the latest drivers create this error. At the moment i'm with the old driver NV 397.64 and i'm fine..

I hope NVidia makes driver to work with P3D without being dependent on NI settings..These settings may become available in NVidia Control Panel in future , but now without the use of NI have a lot stutters in P3D..Any way I downloaded back the 397.64 driver again by using NI and P3D v4.3 works smoot...

The Golden Rule of Drivers.. If It Ain't Broke, Don't Fix It . My mistake was that I did the GPU driver update..I'm goin back to 397.64 to calm down.. enough BS with all these problems..


George

I'm thinking of downloading back again driver 397.64 never had a problem and worked very nicely … ultimately all these updates only give us problems...

I did not have a problem until 397.64 driver I used NVidia and NI together.. the problem started from 397.93 driver .I did not use default settings in Prepar3D ,the problem starts with error DXGI after 5 - 20 min in flight. I don't open a new window ,and I did not open window to new display.. Now I ...

the problem is between NVidia and NVidia Inspector Limiter setting.. I tried all the last NVidia drives " 397.93 , 398.11 , 398.36 , with NI BUT no positive result . I tried also NVidia 397.64 drive with NI ,and I did not have error .. I also tried the NVidia forum but no one gives a positive s...

I can confirm that NVidia 397.64 works well without showing DXGI ERROR_DEVICE.. the other 2 drivers 397.93 and 398.11 have the problem.. Regards George So this beggs the question: Does LM have to catch up to NV, or did NV mess up? I think NVidia is wrong because some other games have the same probl...

I can confirm that NVidia 397.64 works well without showing DXGI ERROR_DEVICE.. the other 2 drivers 397.93 and 398.11 have the problem..

Regards
George