3 hours ago, Chapstick said:

Also, I've CTD'd twice in a row now since using these shaders. Could just be a coincidence. EA still sucks anyway so back to regular EnvShade shaders and EA off for me. Guess we'll see what 5.2 brings in 5 months.

Out of curiosity what are your settings and your gpu vram?

mike

6 hours ago, micstatic said:

I'd have to see some pictures.  But their are countless other PBR airplanes that don't seem to have as many issues that the 787 has ever since V5. 

Nvm figured it out , I just had to turn off dynamic reflections in P3d settings.

cheers 

mike

6 hours ago, micstatic said:

I'd have to see some pictures.  But their are countless other PBR airplanes that don't seem to have as many issues that the 787 has ever since V5. 

Nvm figured it out , I just had to turn off dynamic reflections in P3d settings.

cheers 

mike

2080ti, fslabs and game ready.

Thanks

21 minutes ago, grandfred29 said:

2080ti, fslabs and game ready.

Thanks

Yup thought so.   

Remove the game ready drive and use the studio drivers instead. 

This has happened to myself and 3 other guys. 

Why the 1080ti,2080ti,3080ti    do this on some rigs is anyone's guess. But the studio driver is the way forward. 

LM will blame ndivia and ndivia will say its not their responsibility. In short no one's going to admit their coding is bad. 

Welcome to the land of liability where its easier and cheaper to blame someone else rather than paying or using your manhours to investigate the issues. 

Remember the gsx / canada CTD?  A combination of a gsx issue and bad airport data from LM.  

In the end it was a group of us on here that narrowed the issue and vitali fixed it.  No help from LM at all.  The minute they put admit it's their fault (bad airport data in the bgls) you've lost  a member of staff looking at it.  That's money.   So they never bothered.  Why waste staff a member on it.  So they stayed quiet and stayed out of it. Who can blame them. 

Same with this dxgi issue.  No ones going to admit it's their issue. So it's up to the 'community' to find a work around.  Which is the studio driver.

People will believe any old rubbish if some pc guru puts fancy words in it.  Short of it, we will never know why the TI cards are doing it because no one wants to admit the liability.  

 

 

 

 

 

 

Edited December 5, 20205 yr by fluffyflops

On 12/4/2020 at 9:27 AM, Shomron said:

Just update Envdir and it will prompt you to update Envtex

Thanks.

7 hours ago, fluffyflops said:

Yup thought so.   

Remove the game ready drive and use the studio drivers instead. 

This has happened to myself and 3 other guys. 

Why the 1080ti,2080ti,3080ti    do this on some rigs is anyone's guess. But the studio driver is the way forward. 

LM will blame ndivia and ndivia will say its not their responsibility. In short no one's going to admit their coding is bad. 

Welcome to the land of liability where its easier and cheaper to blame someone else rather than paying or using your manhours to investigate the issues. 

Remember the gsx / canada CTD?  A combination of a gsx issue and bad airport data from LM.  

In the end it was a group of us on here that narrowed the issue and vitali fixed it.  No help from LM at all.  The minute they put admit it's their fault (bad airport data in the bgls) you've lost  a member of staff looking at it.  That's money.   So they never bothered.  Why waste staff a member on it.  So they stayed quiet and stayed out of it. Who can blame them. 

Same with this dxgi issue.  No ones going to admit it's their issue. So it's up to the 'community' to find a work around.  Which is the studio driver.

People will believe any old rubbish if some pc guru puts fancy words in it.  Short of it, we will never know why the TI cards are doing it because no one wants to admit the liability.  

 

 

 

 

 

 

Completely different topic I suppose but can you tell me the difference between game ready and studio are/is?  I have a 1080ti.  Where would I find these Studio Drivers for the 1080ti?

Thanks...running windows 10 64  20H2

Hi:

I'm using the recent update in v5.1 HF but my PMDG 737 NGXU night lighting is way too dim.  Not sure how/what to adjust.  

Any ideas.  Thanks.

Edited December 6, 20205 yr by Dreamflight767

13 minutes ago, Dreamflight767 said:

Completely different topic I suppose but can you tell me the difference between game ready and studio are/is?  I have a 1080ti.  Where would I find these Studio Drivers for the 1080ti?

Thanks...running windows 10 64  20H2

Ive no idea I'm afraid. 

All I know its an issue with 'long frames'  I'm sure one of the gurus here can explain what that is, and I'd be interested to hear why a game ready driver causes them and a studio driver doesn't.  Because I'm yet to hear a proper answer why. Or whose issue it is. LM vs Ndivia. 

Alas 

https://www.nvidia.co.uk/Download/index.aspx?lang=en-uk

Click on 'download type' choose studio driver not game ready driver. 

Good luck. 

15 minutes ago, Dreamflight767 said:

Hi:

I'm using the recent update in v5.1 HF but my PMDG 737 NGXU night lighting is way too dim.  Not sure how/what to adjust.  

Any ideas.  Thanks.

I have the same thing.  🤔

No CTD’s here with any GR driver. 
Using a 3090 in each pc. As sc I am flying the Prosim 737-800 (no instruments onscreen).

Quote :

“NVIDIA Studio Drivers provide artists, creators and developers the best performance and reliability when working with creative applications. To achieve the highest level of reliability, Studio Drivers undergo extensive testing against multi-app creator workflows and multiple revisions of the top creative applications from Adobe to Autodesk and beyond.”

So the Studio driver is basically the same as the GR driver, but optimized for app workflows and several specific mentioned apps.

If P3D can benefit from the Studio driver, if you experience CTD’s  why not ... 👍

You could also try Performance instead of Quality in the NVCP of the GR driver to see if that helps.

Edited December 6, 20205 yr by GSalden