Disabling & reanabling mod causes graphical artifacts

[DoctorVanGogh]

Did some tests with 0.5.1 (due to #1 & #2) and noticed that things get utterly wonky if you fire up a map with VolumetricShading enabled, then disable the mod, load the map again and even worse if you then reenable the VolumetricShading and load the map a third time:

Reproduction steps:

0. Start game fresh (*)
1. Enable VolumetricShading
2. Load a map
   (Maybe 2b?) Force rain to fall /weather setprecip 1
3. Close map
4. Disable VolumetricShading
5. Load map - some artifacts appear:
   https://www.youtube.com/watch?v=OuaujTmJVEo
   (note the flickering on the hill face ahead and house wall behind you)
6. Close map
7. Reenable VolumetricShading
8. Load map - horrible artifacts everywhere:
   https://www.youtube.com/watch?v=A3YGQTljPV8

I'm not entirely convinced this is an issue caused by VolumetricShading - might as well be some wonkyness in shader asset loading by the engine (note the issues cropping up even with vanilla shaders if custom assets were used previously). Leaving it up to you to potentially push this upstream.

---

(*) Switching the "fullscreen" option from settings will make all those artifacts disappear (presumably since this disposes lots of internal buffers in the graphics pipeline and things get loaded up clean again).

[xxmicloxx]

The flickering you see seems to be Z-Fighting in the depth buffer. The artifacts in the second video are probably caused by some shader not compiling correctly, which causes the "stuck" shadow overlay. I'm not quite sure what causes this, but a switch from/to fullscreen recreates the frame buffers so this could be a potential fix. Can you try if resizing the vintage story window also works, or if you need to use the fullscreen option in the settings?

PS: It would also be very nice to know which GPU you are using exactly. It allows me to look up any OpenGL limitations that particular GPU might have.

[DoctorVanGogh]

It would also be very nice to know which GPU you are using exactly.

It's an AMD Vega 64 running with drivers from Jan of this year.

[xxmicloxx]

(commented this on the wrong issue, see #2)