Describe the Bug

many items in the game appear to be having trouble rendering properly, belts randomly show as not moving even when functioning properly, vanilla chests and shulker boxes also will randomly have parts of the model blacked out, and I'm sure you can find more rendering issues if you look for them.

Reproduction Steps

1. Using a AMD Graphics card start minecraft on forge with create installed on the specified versions
2. place a couple of chests or shulker boxes to show the problem

Expected Result

some of the chests/shulker boxes should have blacked out textures

Screenshots and Videos

Crash Report or Log

No response

Operating System

Windows 11

Mod Version

0.5.1f

Minecraft Version

1.18.2

Forge Version

4.2.10

Other Mods

I have tested this with only create even though the screenshot shows chests from quark

Additional Context

I believe there was a recent AMD driver update that could have been the source of the problem, I seem to remember something similar breaking about a year ago when AMD did a driver update.

My friend had the same problem, thanks to you, we can play together again, thank you!

I was wondering if this was an AMD problem because I have the 6800xt and I'm having this problem too.
Forge version; 1.20.1-forge-47.2.20
Create version; 1.20.1-0.5.1.f

I was playing with the Fabric fork and came across this same problem and I reported the bug with them too.
I thought this OG Forge version would be ok, but as I said, I'm getting the same issues.
I've not seen what else this effects as I'm early to this world.
FYI, I made a full clean profile and only had Create installed for Forge.

My image;

Try switching flywheel backends by running /flywheel backend batching or /flywheel backend instancing

switching to "/flywheel backend batching" seems to have fixed the issue, is there anything that will be effected by switching to this over instancing?

switching to "/flywheel backend batching" seems to have fixed the issue, is there anything that will be effected by switching to this over instancing?

Nope! it should be perfectly fine, batching batches the render calls to your gpu where as instancing just draws alot of things with a single call, since GPU's varry so much and always have their quirks (their drivers included) sometimes instancing doesnt work so you need to use batching, however this should be reported to https://github.com/Jozufozu/Flywheel so it can be fixed if possible

Gotcha, Appreciate the help @IThundxr, I'll be sure to leave a report over there!

Having tried the same;
/flywheel backend batching
My frames drop from 500+
right down to just under 30fps when setting to "batching"
and turning it Off drops it to around 20fps.
While both fix the graphical glitch, I'm not sure it's a good fix/workaround.

This was testing with the Fabric fork fyi.
I think I'll stick with leaving it on "instancing" till something better comes around.
I appreciate the help and extra info too

I didn't notice any crazy frame drops on the forge version after switching although I was just on a fresh world for testing and didn't have any contraptions or tile entities around, I'll do some more testing to make sure the fps is stable

Have yall found a fix either than the /flywheel command? Because im trying to play the Create Mod in 1.20.1 but its ruining my experience!

My frames drop from 500+ right down to just under 30fps when setting to "batching"
This was testing with the Fabric fork fyi

also used the fabric version and the waterwheel seems to be a problem. I don't have a pc capable of 500 fps but mine drop from 80 to 15 when there are more than 10 waterwheels present loaded or unloaded

Edit: any blocks that move (steam engines, water wheels, cogs, shafts) seem to be draining FPS