[posila] [2.0.21] Vulcanus fog updates at lower frequency

[miniroot]

I noticed that fog on vulcanus starts to render at a lower FPS while the game still runs at perfect 60, i loaded a save where my factory was significantly smaller and there fog movement was smooth, so i think that game starts to cut of expences. Turning off all graphics options except fog doesn't help to make fog smooth again.
I dont want to turn fog off, it adds a lot to the picture, but i cant tolerate seeing it move at like 15-20 fps. Any ideas how to make that fog run smooth? I have no issues on gleba btw.

And btw i reached shattered planet, and even managed to get back, just an important bit of information on fog issue =D

[posila]

Hello, I suspect some floating point precision issue with time parameter in the fog shader, what is playtime on your save?

[miniroot]

Hello, I suspect some floating point resolution issue with time parameter of the fog shader, what is playtime on your save?

Thanks for answering. I have 470h playtime when i starts to notice that fog slowdowns and twitches, but it may started earlier, cuz last ~100h i payed little attention to vulcanus. I have a save of a same playtrught at 80h where there is no issue.
Disabling mods have no impact on the issue.

My specs are: i5 8400, GTX 1060 6gb, 16GB RAM.

Here is how it looks like ( FPS at steasy 60)

[miniroot]

And here is a save. I am realy hoping, that i get some kind of sollution for that issue, cuz right now im cosidering abbadoning my ~500h save to start over in hope that that time table or watever will not bug out.

[miniroot]

Since topic was moved to bug reports, i am adding log file, as it should be in all topics here.

[posila]

Since topic was moved to bug reports, i am adding log file, as it should be in all topics here.

Thanks you for the save and log, I'll try to fix it quickly. In the meantime, you can disable fog in graphics settings.

[miniroot]

Its a pleasure to be noticed by great and mighty factorio stuff, thank you -)

[posila]

No, thank you! For the reporting the issue.

It's fixed for 2.0.23