Describe the Bug

When testing out the Colorwheel and Flywheel + Oculus compat mods with Vivecraft's VR, I ran into a common issue.

On some shaders, Create's components are either invisible or only rendered in one eye. This does not happen when flywheel's backend is set to OFF. I had posted this issue on Vivecraft's repository a while back, as well as on Complementary Shaders, but none could do so much.

As such, even if the use case is extremely unlikely and the priority is so low I don't even know if it's worth posting,
I shall still mention it. Flywheel is pretty strange with Iris on VR.

Reproduction Steps

1. Obtain Minecraft 1.20.1 and Forge 47.4.8
2. Install and utilize Colorwheel / Flywheel & Oculus Compat fully with Create and Vivecraft
3. Join the world, and find or place a Create Block Entity
4. Turn on Complementary Shaders
5. Observe that the Block Entity is only rendered in one eye...

Expected Result

Create's blocks should be rendered in both eyes. Or rendered at all.

Screenshots and Videos

No response

Crash Report or Log

https://mclo.gs/9q1KQwe - In this specific instance, Colorwheel crashed on its own backend due to likely incompatible shaders

Operating System

Windows 11

What is your GPU?

Radean 7700 XT

Mod Version

0.6.8.a

Minecraft Version

1.19.2

Loader Version

1.20.1 Forge 47.4.8

Other Mods

Many too many. But they're likely irrelevant.
For testing, my modpack is readily available: https://modrinth.com/modpack/vortex-foundations
However it may be impossible without a headset, alas. So I'm always willing to help on it if need be.

Additional Context

I view VR as a fun gimmick to check out buildings and achievements through a different perspective. I simply found this issue pretty odd.

In any case, just putting this out there, because the effect is really trippy-
If it is the wrong place, sorry then-

Using latest versions of all mods involved

• create-1.20.1-6.0.6.jar
• vivecraft-1.20.1-1.2.5-forge.jar
• colorwheel-forge-0.2.3+mc1.20.1.jar
• oculus-mc1.20.1-1.8.0.jar

Do the issues happen with iris/colorwheel uninstalled? If not please report to colorwheel

Well what a magnificent misclick-

I'm sorry, I'll attempt to test it with a clean slate tomorrow.

The issue only arises when VR and Shaders are both on... With at least one compatibility mod in the mix. So far this is what I have.

I will follow up on more info as I gather them- Can this be reopened? GitHub isn't practical on mobile devices...

oops, that did it quick. Anyhow - Testing without Colorwheel
Logs are here: https://mclo.gs/yHCJm2L

This is the modrinth instance.

Flywheel is unavailable with Oculus installed.

As previously observed, when Flywheel's backend is set to off, no rendering issues happen. Impossible to turn it on without Colorwheel or Iris installed, however

Next up, testing without Oculus

@Jozufozu I've done testing

Testing without Oculus
Logs: https://mclo.gs/GULeJph

Without Iris & Oculus, Flywheel functions without issue...

Well, I suppose I should put it over there? Maybe I'll try and test it on Fabric.

On Fabric, this issue is not present. This is then the fault of Oculus itself if I would have to guess?

Issue opened on Oculus - github.com/Asek3/Oculus/issues/832