Crashing without Oculus 1.8
MC crashes stating the new DH requires Oculus 1.8.0. We're running MC 1.18.2 on forge, which doesn't support that version of Oculus. Has anyone else had this issue or have suggestions to fix it?
20 Replies
Remove Oculus
The shaders won’t work anyway
/shadersupport
Distant Horizons and Iris Shader Support Requirements:
- DH 2.1 + Iris
- Minecraft 1.20.1, 1.20.4, 1.20.6, 1.21
- Sodium 0.5.8+
- Iris 1.7.0 - 1.7.3
- Fabric API
- A compatible shaderpack: https://gist.github.com/Steveplays28/52db568f297ded527da56dbe6deeec0e
- DH 2.2 + Iris
- Minecraft 1.20.1, 1.21.1
- Sodium 0.5.8+
- Iris 1.7.5, 1.8, or newer
- Fabric API
- A compatible shaderpack: https://gist.github.com/Steveplays28/52db568f297ded527da56dbe6deeec0e
Gist
Distant Horizons shader compatibility info
Distant Horizons shader compatibility info. GitHub Gist: instantly share code, notes, and snippets.
I'll try to remove oculus and see, but the error it's giving saysbit requires oculus 1.8.0 or newer.
Of you have it you have to have 1.8+
But you don’t need anything
DH can be run on it’s own without any other mod
Not sure how/why the error stopped. While waiting for a response I tried adding the Oculus it said I needed, which resulted in the expected error that the wrong version of MC was running. Removed it, and then the game loaded.
Now it's the second part where I get the error - the server. It give a tick loop error if it's in the mods on the server.
DH doesn't show up under the mod list in game either, and doesn't seem to be functioning.
Try with just dh installed on the server, see if that works
With just? remove everything else?
yeah, see if that results in DH working. if it does, some other mod is interfering with DH. you may need to try this on a seperate server to not corrupt your world. depends what mods you have installed
I removed and then added DH back on my client side since it wasn't showing up before, and now it's back to the error saying it requires Oculus 1.8
Either update Oculus to 1.8 or remove any other Oculus versions you have
Disabling Oculus allowed DH to run on the client, but oculus isn't on the server so not sure still on that one.
Can you send logs on DH not running server side cause of Oculus 1.8 requirement when no Oculus is present on the server?
The server crashes at boot with "server tick loop" error. Oculus isn't on the server.
Send the logs an optionally crash report of that
try the nightly build from #links-n-downloads
Will the client side need to be the nightly as well or can the client stay as the current beta?
they can stay at the current beta. but when 2.3.1 releases soon, i do encourage you to advise everyone to update as well, just in case.
The nightly build for forge work, the server doesn't crash on boot. Thanks. Now to get the setting dialed in.
Nice!