Enabling shaders with Oculus breaks Tinker's buckets rendering

[rafaelkai]

What happened?

See Tinker's bug report here: SlimeKnights/TinkersConstruct#5616

Screenshots

No response

Relevant log output

Minecraft Version

1.20.1

Oculus Version

1.8.0

Rubidium / Embeddium Version

0.3.31

Operating System

W11

What is your GPU?

AMD Radeon RX 6600

Java Version

Java 8

Additional context

It wont be fixed by Tinkers devs.

[KnightMiner]

To be clear, they do not just break Tinkers bucket rendering. They break any mod using the forge dynamic fluid container, which includes not just tinkers but also other mods that have fluids with luminosity. Plus includes not just buckets but anything that renders fluid on an item using the Forge model.

Issue is the classic shader issue where if mods add a custom shader it just gives up, though in this case its Forge adding the custom shader. Since Oculus claims to work with mods, you really should add a way to still render custom modded shaders even if the shader pack doesn't handle it. Better for it to look unshadered than invisible.

[rafaelkai]

Iris, the mod Oculus is based on, has a property in its properties file "allowUnknownShaders=true". When set to true it fixes the custom shader issue. Sadly, Oculus properties file lacks this issue and including it manually makes no difference (the file resets when game loads and removes the manually added line). It has been fixed in a PR which its been open for months already #809