DXGI Prepar3d V4 Help!!

[AnkH 2,263]

Ok, after 2h flying with the Carenado Saab from EDDH to LSZB, my sim also showed this nasty DXGI remove error and I had to cancel the flight. Never had this issue since I switched from FSX, means more than 2 years now. Is there any reasonable "solution" to this by now?

[Cargostorm 151]

Some people eliminated the error by switching to an other video card driver. But the error can also be produced by an add-on that generates "long frames"

Edited July 10, 2018 by Cargostorm

[AnkH 2,263]

In the LM Forums I read that it can also be related to the use of nVidia Inspector or its framelimiter. Will try without the next time.

[Albin 7]

1 hour ago, AnkH said:

In the LM Forums I read that it can also be related to the use of nVidia Inspector or its framelimiter. Will try without the next time.

That's exectly what causing my DXGI error. With NV inspector I use framelimiter and every time now I get the error. Without NV inspector no problems. 

[AnkH 2,263]

22 minutes ago, Albin said:

That's exectly what causing my DXGI error. With NV inspector I use framelimiter and every time now I get the error. Without NV inspector no problems. 

Can you elaborate this a little further? Is it only related to the frame limiter of NVI or to any of the NVI options? I use two, three other things via NVI (GSYNC off, Triplebuffer on), does this work?

[Albin 7]

2 hours ago, AnkH said:

Can you elaborate this a little further? Is it only related to the frame limiter of NVI or to any of the NVI options? I use two, three other things via NVI (GSYNC off, Triplebuffer on), does this work?

Well I really just know that the frame limiter doesn't work. I don't use other settings in NV inspector

[Flic1 976]

I have also been getting this error since downloading one of the latest drivers several weeks ago.  I can confirm that for me it was also a conflict with Nvidia Inspector.  I only used it to limit frames and did not use any other settings.  After disabling NVI, I have done four 2+ hour flights without a problem.

[AnkH 2,263]

How do you "disable" NVI? Simply putting all driver defaults for prepar3d.exe? Or uninstalling it?

[georgio1952 52]

The Golden Rule of Drivers... If it Ain't Broke ,DON'T FIX IT.. I refuse to update the latest GPU drivers, unless a solution is found with NVidia Inspector Limiter...

[georgio1952 52]

7 minutes ago, AnkH said:

How do you "disable" NVI? Simply putting all driver defaults for prepar3d.exe? Or uninstalling it?

putting all driver defaults for prepar3d.exe in NVI

[Albin 7]

28 minutes ago, AnkH said:

How do you "disable" NVI? Simply putting all driver defaults for prepar3d.exe? Or uninstalling it?

Or delete the profile in inspector 

[CaptKornDog 282]

I’ll miss the NVI frame rate limiter.  1/4 refresh and locked to 37 FPS on my 144 Hz monitor worked wonders.  Locking in P3D easily costs me 5-10 FPS and is significantly noticeable, unfortunately.

[Albin 7]

Why is this causing the problem tho? It's probably not just to make us annoyed. Or maybe it is.  But now I set the frame limiter in global profile in NV inspector and see if that works.

[Boeing or not going 578]

Changing the autogen radius to one setting below max fixed this error on p3d 4.3. LM may have a bug in that radius slider an attempt to fix disappearing autogen or popping in squares autogen bugs in the past having max autogen radius could have introduced this bug. That is my guess.

Had 3 days off and completed 3 long hauls the last one a 3 hr flight then a 10 hr flight no restart between.

 

Edited July 11, 2018 by Boeing or not going

[B777ER 2,486]

On 7/10/2018 at 3:57 AM, AnkH said:

In the LM Forums I read that it can also be related to the use of nVidia Inspector or its framelimiter. Will try without the next time.

Use NI with frame limiter on a 1080Ti. Had this issue with the latest driver. Rolled back to earlier driver and problem solved. Still using NI with frame limiter.