Hello,

Question for Flyers which have installed EDDL 2.1 from Justsim.
When i come into the near of this airport my sim crash with the Nvidia device hung.
when i takeoff from this airport (23L or R) and turn left, the sim will crash also.

I have an 1080TI with 11 GB, my sim shows me it uses 4,5  from 10 Gig. And it crash.
 When i deactivate this schenery the sim run and run and run without troubes in these region.
Also installed: ORBX Germany Noth and South, the ORBX EDDL-Files are deactivatet.
The sim only crash with Justsim EDDL2.1 activated. Which plane is irrelevant.
It crash with PMDG and also with the default F35.

can anyone confirm? please let me know.
when i am not alone, then Justsim will look into this.

thanks,

thomas

Do you have Trueglass installed in the sim?   It's installed with a number of acft--TFDi 717, Leonardo Maddog, QualityWings 787, Milviz KingAir 350i etc.

If so, disable it by renaming or removing the trueglass.dll file in your P3Dv5 gauges folder.

12 minutes ago, w6kd said:

Do you have Trueglass installed in the sim?   It's installed with a number of acft--TFDi 717, Leonardo Maddog, QualityWings 787, Milviz KingAir 350i etc.

If so, disable it by renaming or removing the trueglass.dll file in your P3Dv5 gauges folder.

yeah...I wish tfdi would get their act together and solve this. When your product is distributed to several prominent airliners, you have a certain responsibilty to keep it updated....

14 minutes ago, w6kd said:

Do you have Trueglass installed in the sim?   It's installed with a number of acft--TFDi 717, Leonardo Maddog, QualityWings 787, Milviz KingAir 350i etc.

If so, disable it by renaming or removing the trueglass.dll file in your P3Dv5 gauges folder.

Exactly what I did and since then not a single CTD anymore. Except when I am playing around with the volumetriccloud.cfg and use excessive settings just to test...but THAT is just MY fault and not necessary P3D 😉

Thanks for posting this.  

Edited November 22, 20205 yr by mpo910

36 minutes ago, w6kd said:

Do you have Trueglass installed in the sim?   It's installed with a number of acft--TFDi 717, Leonardo Maddog, QualityWings 787, Milviz KingAir 350i etc.

If so, disable it by renaming or removing the trueglass.dll file in your P3Dv5 gauges folder.

thanks, i will disable this, report back, im testing.

disable trueglass did not help. maybe an other Problem:
My sim crash when GPU memory goes over 4,5 Gb.
Is there any way to thest the Vram from a 1080 TI?

 

Reallight? 

 

Hi Thomas, just checked it with EDDL2.1, PMDG737, Orbx GEN and GES, LCEurope, AIG-Traffic, P3DV5.1HF1, AS incl. ASA (trueglass off) - no problems! 

Edited November 22, 20205 yr by LarsA

54 minutes ago, Alti said:

disable trueglass did not help. maybe an other Problem:
My sim crash when GPU memory goes over 4,5 Gb.
Is there any way to thest the Vram from a 1080 TI?

The OCCT test suite has a GPU stress test that should give you an idea if your VRAM is a problem.

Another thought, though--are you using a factory-overclocked GPU?  I have twice run into issues with a factory overclock on a GPU slowly losing its mojo, and slowing the GPU down towards the chipset's design frequencies fixed it both times.

33 minutes ago, fluffyflops said:

Reallight?

I've not run into problems with Reallight, though I sorta expected to.  Trueglass...whole different story there.  Pretty much a no-go if you need VSync on P3Dv5.x

36 minutes ago, w6kd said:

and slowing the GPU down towards the chipset's design frequencies fixed it both times.

Hey Bob,

How do you do that. I'm having a terrible time with this error.

Thanks,

Jesse

8 minutes ago, JesC said:

How do you do that. I'm having a terrible time with this error.

I use the EVGA Precision X1 utllity.  I think MSI Afterburner will do the same, and nVidia Inspector as well.

Another thing that has helped in the past is to relax the TDR timeout settings in the registry.  See:
https://docs.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys

Part of my standard system build with Win 10 is to set TdrDdiDelay to 20 and TdrDelay to 10

2 minutes ago, w6kd said:

use the EVGA Precision X1 utllity.  I think MSI Afterburner will do the same, and nVidia Inspector as well.

Thanks for the suggestions. I'll look into it.

Hadn't had much trouble with this till moving to 5.1 HF1. Then started having consistent crashes at or in the vicinity of certain airports even with a completely in clean install of the default. Moving back to original 5.1 then started producing the same errors. Have spent hours looking for a cause and seem to be coming up dry. So this may have some real merit in my situation.

Thanks Again,

Jesse

1 hour ago, w6kd said:

slowing the GPU down towards the chipset's design frequencies fixed it both times.

I assume we're talking about the core clock rather than the memory clock? I'm guessing this will become more obvious once I get into it, but your guidance is appreciated. This is a bit outside my comfort zone.

Jesse

5 minutes ago, JesC said:

I assume we're talking about the core clock rather than the memory clock? I'm guessing this will become more obvious once I get into it, but your guidance is appreciated. This is a bit outside my comfort zone.

Yes, but the memory clock is not off the table if it's overclocked above nVidia's stock specs.

Underclocking the board from the OEM settings isn't risky...it's just tweaking the clock multipliers down. 

When you start messing with increasing the GPU voltages, then you have to be more careful.

I would start by bumping the boost clock down in small, say 10 MHz increments.  If you get down to the nVidia stock clock, then do the same with the memory.