[Bug]: Severe rendering issue with matteroverdrive:gravitational_anomaly under ComplementaryUnbound + EuphoriaPatches shaders

[firemperor]

Forge Version

14.23.5.2860

Matter Overdrive CE Cleanroom

1.0.1

Log or Crash Report

Hello,

I have found that after placing the item matteroverdrive:gravitational_anomaly as a block, it causes severe rendering issues under the shader pack ComplementaryUnbound_r5.7.1 + EuphoriaPatches_1.8.6.

Environment:

cleanroom-0.5.8-alpha

OptiFine G5

Reproduction steps

1. Do this
   install cleanroom-0.5.8-alpha+OptiFine-G5+Matter Overdrive CE Cleanroom1.0.1
   install shaderpacks-ComplementaryUnbound_r5.7.1 + EuphoriaPatches_1.8.6
2. Do that
   putmatteroverdrive:gravitational_anomaly with shaders enabled
3. Crash/Bug...

[Rsslone]

Its working under that mod configuration for me.

If you create a test world and place just the anomaly does it do it?
If you install the old CE version and create a test world with it does it do it?

If it does it on both, this was a pre-existing issue, I'll have to take a look at it further, if you can give me your pack or minimal setup to reproduce with?

[firemperor]

Q: If you create a test world and place just the anomaly does it do it?
A: Yes, the issue still occurs.

Q: If you install the old CE version and create a test world with it does it do it?
A: Yes, the issue also occurs in the old CE version.

Q: Can you give me your pack or minimal setup to reproduce with?
A: Here is my mod list / minimal setup:

[Rsslone]

I attempted to replicate exactly what you have and it crashed without baubles (hard depend I forgot to mark oops), so I assume its in the 1.12.2 folder, there has to be something else going on. I've tried my test pack, a clean pack, and the barebones template pack, it all worked for me. Either your shaders are corrupt, or there is something else different.

Grab the BareBones Template Pack and run it, then install baubles, CTM, MatterOverdrive, Optifine, and the shaders. Enable the shaders and place an anomaly.

[firemperor]

I have done some further testing and here is what I found:

Test 1: Disable dedicated GPU and use integrated graphics
Result: The issue still occurs.
Conclusion: The issue is likely not caused by GPU driver issues.

Test 2: Use the BareBones Template Pack with default settings as you recommended
Result: The issue still occurs when placing the anomaly with shaders enabled.
Conclusion: The issue is not specific to my modpack configuration.

Test 3: Re-download ComplementaryUnbound_r5.7.1 and combine it with EuphoriaPatches_1.8.6
Result: The issue still occurs.
Conclusion: The shader files are likely not corrupted.

Current speculation:
The issue might only occur under Windows 10 (or a specific Windows version). My OS version is Windows 10 22H2.

Could you test under Windows 10 22H2 to see if the issue can be reproduced?

[Rsslone]

First try this test build, extract the jar from it.

matteroverdrive-1.0.zip

Otherwise maybe we patched them differently, I used the legacy forge patcher.
Unzip and use my shaders.

ComplementaryUnbound_r5.zip

I'll try booting into my windows to just sanity check later.

[firemperor]

I tried the test build you provided (matteroverdrive-1.0.zip) and it fixed the issue. The anomaly now renders correctly with the shaders enabled.

I tested the following:

1. Extracted the jar from matteroverdrive-1.0.zip and replaced the old mod file.
2. Used my ComplementaryUnbound_r5.7.1 + EuphoriaPatches_1.8.6 shaders with Cleanroom 0.5.8-alpha.
3. Placed the gravitational_anomaly in a test world.

Thank you for the fix!

[Rsslone]

I'm still confused why I wasn't able to reproduce it but alas, it was a easy change so it will be included in the next release.
Thanks for the report!