Using deceased craft v5.5.5, with a complete stock installation (no settings changed apart from enabling complimentary shaders, fresh world, no additional mods installed), enabling Complementary Shaders and activating a create contraption (in this case a mechanical bearing, a creative motor, and a polished granite block) causes the contraption to become completely invisible.
Disabling the flywheel backend (/flywheel backend off) makes the contraption visible again, but causes some artefacting which I suspect is related to entity culling (it primarily happens when said contraption is out of the players FOV, which was quite noticeable with a 5x5 create elevator).
Disabling Oculus Flywheel compat (rename *.jar to *.jar.disabled, done via PrismLauncher) fixes the issue - the instancing backend can still be used (verified with /flywheel backend, which prints the current backend in use) which has noticeably better performance (as expected), and as of yet no visual artefacting.
The Fix:
As of right now, there seems to be no downside to simply disabling Oculus Flywheel compat. If you previously disabled the flywheel backend, remember to run /flywheel backend instancing to take advantage of the performance gains.
Technical info
With a stock pack (OFC and shaders still enabled), activating the contraption caused tons of OpenGL errors to be spammed in the logs:
Update: After playing a bit more, it turns out the graphical artefacts are still present after disabling Oculus Flywheel Compat. I again believe it may be due to entity culling, but I'm not entirely sure.
Using deceased craft v5.5.5, with a complete stock installation (no settings changed apart from enabling complimentary shaders, fresh world, no additional mods installed), enabling Complementary Shaders and activating a create contraption (in this case a mechanical bearing, a creative motor, and a polished granite block) causes the contraption to become completely invisible.
Disabling the flywheel backend (
/flywheel backend off
) makes the contraption visible again, but causes some artefacting which I suspect is related to entity culling (it primarily happens when said contraption is out of the players FOV, which was quite noticeable with a 5x5 create elevator). Disabling Oculus Flywheel compat (rename*.jar
to*.jar.disabled
, done via PrismLauncher) fixes the issue - the instancing backend can still be used (verified with/flywheel backend
, which prints the current backend in use) which has noticeably better performance (as expected), and as of yet no visual artefacting.The Fix:
As of right now, there seems to be no downside to simply disabling Oculus Flywheel compat. If you previously disabled the flywheel backend, remember to run
/flywheel backend instancing
to take advantage of the performance gains.Technical info
Tech Specs:
Version details:
Broken modpack zip (in PrismLauncher or curseforge format) available if needed :)