Looks like it's just me? https://gitlab.freedesktop.org/mesa/mesa/-/issues/13063#note_2888258
And I'm supper ignorant about d3d in general. Someone said this is actually a dxvk issue.
Is there an issue open in DXVK tracker for this? If so, this should be closed.
Is it more than just rumor that this is the right thing to do?
I know this isn't the correct place to ask, but this is the path I'm on. Does the debug here mean that debug prints MORE messages than info? DXVK_LOG_LEVEL=none|error|warn|info|debug
I have confirmed dxvk, but I'm not opening a third issue... I'll work with the dxvk ppl, but you guys are old enough to run your own circus the way you want and I want not part of it.
A dxvk dev have already poked a bit at the Modulus Demo issue, but i don't know much (well understand more like) more than that at the moment
https://gitlab.freedesktop.org/mesa/mesa/-/issues/13049#note_2886860
I guess the app is having trouble going full screen, downgrading to debian's mesa fixes it and I can go back/fourth. Notably the top panel vanishes, but my apps that are panels and the other windows still work. I never get any sound.
Software information
Dyson Sphere Program, Modulus Demo, Starfield(the main menu, is expected to work)
System information
Ignore the
mesa v: 25.0.4-1, the-1indicates it's a Debian library version ID and because of the way Debian works the i386 and the x86_64 versions must match, so mesa git and rc versions are built with a debian sid version ID.Log files
https://gitlab.freedesktop.org/-/project/176/uploads/08a6d64c2aca402f3b6e83845fb76973/dmesg.txt.xz
https://gitlab.freedesktop.org/-/project/176/uploads/bbde1e977b9eb0ed4d057ff3a28372c9/data.txt.xz
https://gitlab.freedesktop.org/-/project/176/uploads/29f1719f9d4410a3a9de81c21a828024/1745544061_err.txt.xz
https://gitlab.freedesktop.org/-/project/176/uploads/387264402578ac09d9bef8a69d8d5941/1745544061_vk.txt.xz
Tapani Pälli
13 hours ago
With "Modulus Demo" we hit an assert in common vulkan runtime code. Issue is that app or proton supplies VkImageViewUsageCreateInfo that is not a subset of usage flags given when creating the original image. Vulkan spec: "The implicit usage can be overridden by adding a VkImageViewUsageCreateInfo structure to the pNext chain, but the view usage must be a subset of the image usage.". This workload likely fails on other drivers as well (?)