-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Shaders Crash #147
Comments
The other person is using ubuntu |
Disabling shaders in the mwc config fixed the issue, may have been to do with integrated graphics. May be fixed in the future, to be confirmed. |
For me, just disabling
worked. |
this also means that the scopes don't work for me |
this fixes my crash aswell, specs: intel i5-12600k, 32gb ddr5, amd rx 6650xt |
It will be fixed soon don't worry |
Nice! |
Yes Integrated Graphics are not currently supported |
Its better, as now scopes work, but unless I disable these shader config settings:
my game crashes. I've tested every option in the shader section of the config file, with just mwc dev 16 and redcore. When I enable flash shaders, and use a gun, I get this log: This happens with any of the options above enabled though. I also get this message when I try to use a different game: If you need any more info, let me know. |
looking at the log, the problem still seems to be caused by 'Error creating fragment shader: mwc:shaders/postflat' as in the original post on june 2nd |
Yeah this might be another different issue, I will keep this closed for now at least |
Will reopen to remember to take a look tomorrow, but will close if I don't see anything obvious. Note to myself: |
Same exact issue here on Fedora Linux
|
Attempt to close HDR Buffer and Screen Shader |
Interesting that it also happens with dedicated graphics cards |
Lasers are also completely broken, causing immediate crashes |
From what we can see it only happens with Mesa drivers, report it to them |
Ok, thanks |
https://gitlab.freedesktop.org/mesa/mesa/-/issues/10942 |
The mesa devs think that the problem could be this: 3263992: warning: 0:133(2): error: |
Well it seems to only happen on Mesa so my guess would be it's a Mesa issue, but it could be that AMD and NVIDIA windows drivers have a bug/out of spec behavior that makes it not crash, so honestly only them could tell |
Looking at the method/function, when it returns -1, would its type be an int or a float? Because that could be the error? https://github.com/Cubed-Development/Modern-Warfare-Cubed/blob/main/src%2Fmain%2Fresources%2Fassets%2Fmwc%2Fshaders%2Fpostflat.frag#L133 |
wat Yes that is indeed not right, why the hell does it not crash on any other driver??? |
Lol, other drivers do not have the same quality level as Mesa. |
Fixed in 0.1.6 Click here to see on CurseForgeClick here to see on Modrinth |
Describe the bug
With just mwc installed, on opening a world - both new and old worlds - the game crashes as soon as something from mwc is loaded in. For me, it tried to load in a terrorist, and for the other user, it was the item used at the top of the mwc tab when they moved onto the second page of the creative inventory.
I was trying to recreate a bug for another linux user. I use Arch. I am not sure what they use.
Looking at the crash report and logs, in both cases it was caused by 'Error creating fragment shader: mwc:shaders/postflat'
Reproducibility
I reproduced this issue with no other mods installed.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Doesn't crash
Logs or/and crash reports
Latest.log:
https://mclo.gs/6eE1te9
Crash Report:
https://mclo.gs/N7hEqR8
Versions
Specification:
All of these info below are not necessary but may become necessary depending on the issue
The text was updated successfully, but these errors were encountered: