Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shader initliazation issue with new build of 0.49 #51

Open
FailedTalent101-1 opened this issue Jul 12, 2024 · 5 comments
Open

Shader initliazation issue with new build of 0.49 #51

FailedTalent101-1 opened this issue Jul 12, 2024 · 5 comments

Comments

@FailedTalent101-1
Copy link

Had to reinstall OpenMW 0.49 for a mod, so I went to the OpenMW website and downloaded the build from Development Builds for Windows. Now whenever I try using this shader pack, it says "failed initializing shader: fullscreen_tri". With my very limited coding experience (still learning), I have done my best to see what could be wrong, but I'm too dumb to figure it out.

@khirasier
Copy link

same issue here

@nitroinferno
Copy link

Looks like the issue is stemming from line #9 in shaders\lib\core\fragment.h.glsl

The regular shaders\lib\core\fragment.h.glsl has:

#if @waterRefraction
vec4 sampleRefractionMap(vec2 uv);
float sampleRefractionDepthMap(vec2 uv);
#endif

new one has:

#if @refraction_enabled
vec4 sampleRefractionMap(vec2 uv);
float sampleRefractionDepthMap(vec2 uv);
#endif

I'm a complete noob at this stuff - but I'll see if I can't get some kinda fix where it allows the shaders to work once again in 0.49

@nitroinferno
Copy link

Well I got the game to load after fiddling with some of the files after parsing through numerous errors on startup the result:

Screenshot 2024-09-06 211004

This is way beyond my league of ability to fix haha

@J-Aziahni
Copy link

Had to reinstall OpenMW 0.49 for a mod, so I went to the OpenMW website and downloaded the build from Development Builds for Windows. Now whenever I try using this shader pack, it says "failed initializing shader: fullscreen_tri". With my very limited coding experience (still learning), I have done my best to see what could be wrong, but I'm too dumb to figure it out.

Here to ask if there is a fix found or made for this yet?

@Dusterrr
Copy link

Also checking to see if a fix has been found please

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants