Vivecraft
Crash with Monado + OpenComposite on Linux
When trying to enter VR mode, the game crashes. The game plays as normal with both mods installed when playing outside of VR. Mod versions tested with:
- Vivecraft 1.2.5
- Sodium 0.6.9
Tested in Fabric 0.16.10, Minecraft versions 1.21.1 and 1.21.4. This crash only happens when I run Monado+OpenComposite. When I use SteamVR instead, there is no crash and the game works as expected. My system information:
- kernel 6.13.4-arch1-1
- Java 21.0.6
- Mesa: 24.3.4-arch1.1
- Monado: v24.0.0-373-g0d0e3704e
- OpenComposite: commit 175e3b3
Crash log: https://gist.github.com/CameronClarry/fb53ba516b2bca2f4916fefbf4aacfde
I can't understand their (opencomposite) stack trace, as to what of us would cause the crash, if you want you can ask them, and report to me. then I can see if something can be done about that.
It's somehow related to Sodium, as I can play in VR with Monado+OpenComposite just fine if I don't use Sodium. I'll also post this issue to the OpenComposite gitlab.
hm, that would be weird.
can you post the hs_err_pid log it mentions?
/home/USER/.local/share/PrismLauncher/instances/TEST/minecraft/hs_err_pid7873.log
make sure your session token isn't in there before posting, they sometimes are
Here's the log: https://gist.github.com/CameronClarry/00c6e52796266c08a14b50173073025a
okay, unlike on windows where it crashes on init, this crashes when submitting the frame to the runtime. maybe some interop issue from opengl to vulkan, would still say that is an issue from opencomposite/monado
I don't know where exactly in this “stack” the issue actually lies, but this is very much still present. On db.vronlinux.org compatibility is supposedly good, but only in combination with Sodium it appears to cause the game to crash, as soon as it actually attempts to submit frames to the runtime. That's why it works just fine until I enable VR mode. I think this needs more investigation, just that I don't think that I am capable of really doing much here. Kind of just bumping this issue as it affected me very recently.
EDIT: Has this been reported to OpenComposite for further investigation? Because that might be important.
I have done nothing like that. and also will not do it, since I don't use linux, and cant produce the issue because of that.
I have done nothing like that. and also will not do it, since I don't use linux, and cant produce the issue because of that.
I wondered whether @CameronClarry might have reported this to OpenComposite, as they were instructed to, as this might very likely be related to that rather than Vivecraft itself or maybe even Sodium. But I guess I could check myself, even though I may or may not actually come across it, even if it has been reported.
EDIT: I just checked, and it has indeed been reported there by Cameron Clarrry, so this will have more discussion there. I'll read the conversation over on the OpenComposite repository to get informed on the current state of the issue. I am sorry for the disturbance.
EDIT 2: It appears that this has no discussion over there either. I bumped it by commenting, but I'll have to see whether anything will happen, as I will likely not be able to troubleshoot or trace the source myself.