On 1/12/2021 at 7:15 AM, mpo910 said:

UPDATE FROM LM at their support forum - Follow first link in post above

 

 

Hi,

Thank you for this much needed fix! Do you think a similar fix can be devised for the bug that even in overcast situations sunlight is cast on every object that is above your POV? 

Thanks!

Thanks for this. But I think I will just wait for P3D v5.2. The fix for this will most likely be in 5.2.

12 minutes ago, Rob_Ainscough said:

Fix works very well, only oddity I noticed was God Rays going into hysteria on, off, on, off.

Cheers, Rob.

Hi Rob.

This I did notice without this fix as well. I had GodRays turned off due that "on" "off" "on" "off" behavior. This is within VR and depending on the view "panning" left-right or up-down.

Do you really think this is related to this values?

Marcus

1 hour ago, mpo910 said:

Hi Rob.

This I did notice without this fix as well. I had GodRays turned off due that "on" "off" "on" "off" behavior. This is within VR and depending on the view "panning" left-right or up-down.

Do you really think this is related to this values?

Marcus

This I only have seen 2-3 times, both in the sky as on the ground. After a reload of P3D it was gone. So I have them on.

The moments it appeared was when I had changed views multiple times.

Hopefully LM can fix this for good. Plus the orange skies and low res early dawn/ late dusk clouds...

23 minutes ago, Rob_Ainscough said:

 AMD 5950X and nVidia 3090 can do (and a AMD 5950X and 6900XT)  ... yes the "out of stock" wait is killing me 🙂

On an unrelated side note, has anyone noticed the EA clouds move very quickly during high winds?  Not sure if this is my VolumetricClouds.cfg modifications or something else in HiFi ASP3D?

Cheers, Rob.

With the AMD I could help you out to get one quicker as waiting for Stock in USA. If you are interested, PM me. In Germany it is in Stock at a very well known supplier for round about EUR 973,- (in Stock Status 2 minutes ago).

Yes. The cloud movement is noticeable at my end too. I use ASP3D latest build. Update interval set to 5 minutes.

I think this is what happens (but maybe you did not mend the update interval set in your ASP3D app).

At low wind speeds "at cloud level" this is also noticeable, but then they are not moving so fast and not so long/far.

At high wind speeds "at cloud level" this becomes very noticeable. Clouds "have to travel" further and due the higher wind speeds faster, from the prior "updated interval location" to the present updated "location". At high winds, the clouds have to travel further and faster, this is what I see (in a short time compressed), at least I assume this.

So it seems that at higher wind speeds and bigger difference regarding cloud location, before and after the update, the movement speed is bigger too.

But I see here a big chance too.

As performance reduction during this update and movement is negligible, maybe updating much more often will reduce this. I think about updating every 10 seconds? Or even more often? Realtime?

This would be great but I really don´t know which restriction there are also.

But I like the idea that truesky has possibilities to update per movement and not redrawing suddenly at the updated cloud location.

Marcus 

 

 

Edited January 13, 20215 yr by mpo910

@mpo910

Awesome post thank you so much  !!

8 hours ago, Rob_Ainscough said:

It's very possible the hysteria issue with God Rays was a coincidence.  I had reported the God Ray hysteria early on in the Beta with video ... it's a difficult issue to replicate as it's not consistent.

But relative to the shader code changes, it's a big improvement!! (I'll give up God Rays for it)  ... even more so if one uses ChasePlane with gimble off (where the original problem was very apparent.

Yes, still lots of other issues to be fixed but the dev team is back and working on it.  I'm still blown away by the performance of P3D V5.x even on my now "dated" hardware (9900K and Titan RTX) ... can't wait to see what an AMD 5950X and nVidia 3090 can do (and a AMD 5950X and 6900XT)  ... yes the "out of stock" wait is killing me 🙂

On an unrelated side note, has anyone noticed the EA clouds move very quickly during high winds?  Not sure if this is my VolumetricClouds.cfg modifications or something else in HiFi ASP3D?

Cheers, Rob.

Oh yes, as an owner of a 5950X and a Watercooled 6900XT Ican tell you I love it 🙂 P3D was never so smooth for me.

 But i was coming from a 9990XE and a Radeon VII so the 6900XT alone was nearly 100 % more powerfull then my Radeon VII 

On 1/12/2021 at 8:56 PM, mpo910 said:

Maybe I am a little picky now....but this is most likely not the final solution. It is communicated by LM to be a "work around" until they fixed it with the next release.

I can not say if this provided workaround will taken as the final fix. 

Just to be aware off incase of any future updates. 

Fiddling with the core shaders is not a good way and can cause instable situations if not done properly.

😉

Regards

Marcus

Thanks Marcus but how does one edit a fxh file? 🤔

2 minutes ago, Shomron said:

Thanks Marcus but how does one edit a fxh file? 🤔

Notepad++ is free to download. 

On 1/12/2021 at 1:51 AM, Rob_Ainscough said:

Thanks Marcus!

Summary:

Modify from your P3D install i.e. - D:\Lockheed Martin\Prepar3D v5\ShadersHLSL\FuncLibrary.fxh

Line 781 - replace (one line)

vProj[2][2] += ZBias * 4.76837158e-7;

with (3 lines)

float zBiasOverride = ZBias;
if (ZBias < 0) zBiasOverride = -1 + ZBias * 0.03333333;
vProj[2][2] += zBiasOverride * 4.76837158e-7;

Clear out the shader cache (delete folder here %LocalAppData%\Lockheed Martin\Prepar3D v5\Shaders)

Cheers, Rob.

For those using Envshade, the code of interest will not be at line 721, as Envshade does modify this file...in my case it was at line 821, but its precise location in the file may vary depending on how you have Envshade configured.

Also, you will most likely have to go back in and reaccomplish this edit if you use Envshade to modify the shader settings again later.

FWIW, for those using the Lorby-SI P3D Addon Manager, under the "Tools" tab there's a handy one-click "Clear the Shader Cache" function there many may not have noticed.

 

Performed this fix today... what a great edit!!!   Makes it difficult to find the airport in the fog/haze...  thanks!!!

3 hours ago, w6kd said:

For those using Envshade, the code of interest will not be at line 721, as Envshade does modify this file...in my case it was at line 821, but its precise location in the file may vary depending on how you have Envshade configured.

Also, you will most likely have to go back in and reaccomplish this edit if you use Envshade to modify the shader settings again later.

FWIW, for those using the Lorby-SI P3D Addon Manager, under the "Tools" tab there's a handy one-click "Clear the Shader Cache" function there many may not have noticed.

 

Using Envshade, mine was at that line (821) too. And you are right, changes in Envshade settings require to accomplish the mod again. But usually, I don't play with Envshade settings too much.

2 hours ago, Nemo said:

Using Envshade, mine was at that line (821) too. And you are right, changes in Envshade settings require to accomplish the mod again. But usually, I don't play with Envshade settings too much.

I always search for words. Very easy and it doesn’t matter what line number

Edited January 15, 20215 yr by GSalden

I cant seem to get this to work. I have made the changes to the file and deleted the shaders. When I take off from LGAV (fly-tampa) the autogen on airport and in surrounding area/ city bleeds through the clouds.  Nothing has changed. What am I doing wrong?

12 minutes ago, LGKR said:

I cant seem to get this to work. I have made the changes to the file and deleted the shaders. When I take off from LGAV (fly-tampa) the autogen on airport and in surrounding area/ city bleeds through the clouds.  Nothing has changed. What am I doing wrong?

Can you quote all the lines you have at that section of your shader file please? Must be all the lines between the empty lines regarding this change. 

Marcus