search

Vivecraft / VivecraftMod

An experimental port of Vivecraft to Forge/Fabric
Other
168 stars 42 forks source link

vivecraft has been crashing my pc #187

Open Nathan22211 opened 11 months ago

Nathan22211 commented 11 months ago

I'm quite honestly not sure what's causing this, but periodically the 1.20.1 version of the mod has been causing my PC to crash, not so much as a blue screen it just resets itself.

I have the following for this (of what I narrowed it down to: forge 47.1.3 on 1.20.1, would use newer but sintra connector only works for that version. I recall having a crash on a newer version too but could be wrong vivecraft, vivecraft compact + deps, and JEI meta quest pro + virtual desktop rx 5600xt for a GPU r5 3600x for a CPU Windows 11

I do have razer cortex running in the background as well, but I don't know if that's a cause yet

fayer3 commented 11 months ago

I don't think such a thing would be caused by vivecraft can you check that your cpu/gpu are not overheating? if those are fine, I would suspect a faulty power supply

Nathan22211 commented 11 months ago

It's only occurred when playing vivecraft, and my system is like 4-5 years old. I could try a driver update and see if that's the case

Nathan22211 commented 11 months ago

ok turns out vivecraft has a myriad of issues when playing with iris/oculus

with forge if you use oculus with a shader in the shaderpack folder v1.0.0 will crash the game on world load but 1.0.1 will crash the system fabric with 1.0.0 with iris will crash the game while it's loading up, I'd imagine something similar will occur with 1.0.1

fayer3 commented 11 months ago

1.0.1 was made to fix iris 1.6.5+ if you don't post any logs I can't help

Nathan22211 commented 11 months ago

https://gist.github.com/Nathan22211/28c78d745973608b802bb04dc7852e59 mind you where it cuts off is when my PC crashes

fayer3 commented 11 months ago

can you try without vivecraftcompat

ferriarnus commented 11 months ago

It could be an outdated AMD graphics drivers from 2022. Updating to the latest "WHQL Recommended" (aka stable) version could fix your issue. https://www.amd.com/en/support

Nathan22211 commented 11 months ago

I just did a fresh install of Windows last month and apparently I'm not the only one with this issue. ask Xee in the discord, they have the same issue but using embedium rather than rubidium fixes it. might be related to a rubidium bug on AMD GPUs