Created attachment 144606 [details]
Wine output from trying to run windemic.exe, it happens also with LauncherFallour.exe. It dosen't seems to be a wine issue if I run in 64-bit machine with same OS(Xubuntu 18.04) it works.
AFAICT there's a couple of things here:
- the crash
Most likely a wine bug, since the GL spec clearly says that glGetString (the only API which can give this message) can return 0/NULL on error.
- nouveau/mesa complains about unknown GLSL version
That should not happen. What hardware are you running on, do you have any changes to your drirc?
s/wine/wine or application/
Created attachment 144675 [details] [review]
Print GL profile and unknown GLSL version.
Forgot the more constructive parts:
- please attach (plain-text) the output of glxinfo
- if you can build mesa - what's the output of wine with the attached patch
Created attachment 144753 [details]
Attached the output of glxinfo, tryed to build mesa from src it was successfull, but havem't patched yet.
That patch is missing the actual version... given that this is a NV18, this should be fixed by
Created attachment 144754 [details]
patched with both suggested patches
I tried to compile with the patches and I get errors, the output of the build is attached. First patched with the getstring.patch and context.patch.
Created attachment 144755 [details]
Patched with just the latest suggested patch.
Tried without getstring.patch instead used the latest suggested patch for context.patch. It error out to, the output is attached.
../src/mesa/main/context.c:2:7: error: invalid suffix "d81f1..2734693" on integer constant
index 03d81f1..2734693 100644
Looks like your patch-application skills require some work.
You should just be able to build mainline now -- it will have the change in question already.
That is true my patching skills are horrible. I see I try the patching again let see if its builds, just because some practice can't hurt, if fails again I go with the mainline that has already been patched.
Oh almost forget tank you for the quick response to my problem.
This should be fixed in Mesa 19.1.4.
Can you try?
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1180.