Oculus Compat error on startup - CTD every time
Hello, currently battling this error;
Error: java.lang.NoSuchFieldError: TESSELATION_SHADERS
Happens when i turn on shaders, still testing if its all shaders but once this happens i cant even open the game anymore and i have to clear my shader folder to get it to launch again. Anyone familiar with this and know of a fix or if i have anything that i shouldnt?
Current suite of the main related mods is Embeddium, with the embed extras options and dynamic lights, oculus 1.7.0 for DH, iris/oculus flywheel and geckolib compats. I am running EMF and ETF which is working for fresh animations, but im unsure if related, i dont think so, as it works after removing shaders again
Please see below for my current problem, will come back to this if necessary
8 Replies
Going to just attach this here as a secondary issue, attempting a rebuild of my modpack to see whats causing what from above, but now im running into this error:
org.spongepowered.asm.mixin.transformer.throwables.MixinTransformerError: An unexpected critical error was encountered
"Caused by: org.spongepowered.asm.mixin.throwables.MixinApplyError: Mixin [mixins.oculus.compat.dh.json:NonCullingFrustumMixin] from phase [DEFAULT] in config [mixins.oculus.compat.dh.json] FAILED during APPLY"
.
fresh installs of literally everything so im not sure whats doing this
do i have the wrong version of DH?
it keeps referencing the oculus compat in every crash but most of them vary slightly
i have the same thing.... i think its a mod thats a mod incompatibility
im not sure tho
Solution
changing distant horizons to version 2.1.2a works as a fix for now
im already on that beta branch as of now
yeah its definetly Oculus, i turned it off and it launched
turned it on and same crash error
i rolled DH back and it still does it yet
always something to do with "[mixins.oculus.compat.dh.json:"
getting all my mods from curseforge right now and as far as im aware thats where the up to date stuff is, unless DH still has a separate download
ignore me i had a delayed onset of dyslexia, i was on 2.2.1a
it did launch on 2.1.2a
well that explains it
mega oof
ah well, that sucks, gotta wait for Iris, and then Oculus..... AGAIN
on the brightside i still dont have to do all the janky stuff i did to get it to work before 2.0