-
Notifications
You must be signed in to change notification settings - Fork 80
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
Crash unless meshlets disabled #577
Comments
Lemme guess... AMD graphics card? (And I answer it myself: AMD Radeon RX 6800 XT) |
AMD commercial driver has fully broken mesh-shading unfortunately. If you have time - please send bug-reports to them, as we need a driver fix. |
Could you elaborate on what the issue is? I couldn't find anything in Google. |
AMD seems to no care much about these reports though. We sent one already. I think they disagree with that being their fault, even though OpenGothic runs on Intel and NVidia cards just fine. |
Even though OpenGothic runs on same hardware with opensource driver just fine :)
Consequence is performance. On a bug side - pretty certain that it's AMD bug. When engine calls to |
I can try to debug the issue to figure out what exactly causes it and whether the shader can be modified to compile. But I don't see any instructions for building and debugging the project in Windows. Does anyone have experience with it? |
MSVC 2022 and the project downloaded off a private fork. There were some dependencies to fulfill, but that was a while ago I had to do that. Try these easy steps first and then we will see what's missing. Likely you will need:
Likely I forgot something, but this is a good start to minimize the problems. |
cmake + VulkanSDK + windows-sdk should be enough. CMakeLists.txt can be opened with Visual-Studio (open folder) and should work just fine. If there is any issues with bring up - let me know. Shader that you interested in is |
I've got some results. The culprit is this line: I managed to get the shader to work by replacing it with this:
Assigning pos or normal directly |
Thanks @hwnde , for investigating it!
This is an unease split:
My suggestion here is to report this issue again, to AMD: someone who owns their gpu can use https://www.amd.com/en/support/kb/faq/amdbrt# I'm not really aware, if they have other way of bug reporting specifically for game-developers, who does not own their gpu. Secondary option: disable mesh-shader on AMD by default - call it broken. Two major downsides here: I'm not happy to have conditionals with HW-vendor names, and we will ruin performance for MESA users. |
I think this is where such issues are reported: https://community.amd.com/t5/opengl-vulkan/bd-p/opengl-and-vulkan-discussions I can post an issue and see if AMD responds. However it's still an open question what to do with this issue. There is no guarantee that AMD will do a fix any time soon or ever. |
Started a post on AMD for forum: Feel, free to join discussion :)
I'm still worry, about maintaining it, since shader code is always something to edit. Let, see how fast they will respond to the report; |
I'm an OpenMW graphics developer who's been sent a link to this, and have a couple of recommendations:
|
Hi, @AnyOldName3 and thanks for recommendation!
That would be nice. Unfortunately can't take opportunity myself - due to lack of AMD gpu. And one more option: sneak a test to Vulkan-CTS, that uses mesh-shader + vec3 :D |
Windows 11, fresh install, commit 26b816e
Game crashes when starting a new game or loading an existing save. Disabling meshlets resolves the issue.
crash.log
The text was updated successfully, but these errors were encountered: