Closed critkitten closed 10 months ago
Does this happen on development builds too? Regardless, this seems like a bug with OpenMW, not this shader: shaders are deliberately stateless and cannot cause this sort of behaviour to occur by themselves.
Yes. 00b142eed7963940a8ec2b5b05ec5462c6f5c11b
Joshua Barretto @.***> hat am 26.12.2022 17:59 CET geschrieben:
Does this happen on development builds too? Regardless, this seems like a bug with OpenMW, not this shader: shaders are deliberately stateless and cannot cause this sort of behaviour to occur by themselves. — Reply to this email directly, view it on GitHub (https://github.com/zesterer/openmw-volumetric-clouds/issues/15#issuecomment-1365285021), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AUFOLVGP2ZG3GMEI22YIMELWPHFG7ANCNFSM6AAAAAATIAOHSQ). You are receiving this because you authored the thread.Message ID: @.***>
I can confirm this as well using the openmw 0.48.0 rc9 generic linux build from openmw.org. First experienced it when starting a new game with my partner. We were very confused. :-)
I think this can be temporarily fixed by turning 'interior mist' down to 0 in the F2 settings menu.
I had this same issue. Spent 2 hours trying to isolate which mod was causing the issue. I figured out it was this one. Your recommendation to turn "interior mist" down to 0 solved it. Thank you.
This should now be properly fixed in the latest build.
I test OpenMW-0.48.0-RC4-win64.exe on windows and branch openmw-48 @ 5b56fe8d0db108b18dcfb03ee558af5bbc495f06 on linux.
See also https://gitlab.com/modding-openmw/modding-openmw.com/-/issues/140