insane performance impact with just placing one block
yuma-dev opened this issue ยท 8 comments
Describe the Bug
When just placing down for example a watermill block the FPS will more than halve leading to create being unplayable
Attached is a manual Crash report directly done after the video
Reproduction Steps
- Place Create Block
- Watch FPS go down
Expected Result
- Place Create Block
- Watch FPS be stable :D
Screenshots and Videos
Replay.2024.01.09.22.36.08_00m50s550ms-00m58s150ms.mp4
Crash Report or Log
https://gist.github.com/yuma-dev/a994a1973f72dc09df216b37c1f335d4
Operating System
Windows 11
Mod Version
0.5.1d
Minecraft Version
1.20.1
Other Mods
https://gist.github.com/yuma-dev/8df9e35b15e8daf17379f275775acba5
Additional Context
Running with Iris Shaders
are you running a fork of create?
currently create 0.5.1d sodium 0.4.10 fabric api 0.88.1 iris 1.6.4 and indium 1.0.21 are the precise versions you want, and those are not the versions you have.
Enabling shaders disables Flywheel's optimizations. Nothing we can do about it. Check f3 and make sure your 3060 is listed on the right side.
or you can use iris flywheel compat to keep flywheel enabled when shaders are used
are you running a fork of create?
currently create 0.5.1d sodium 0.4.10 fabric api 0.88.1 iris 1.6.4 and indium 1.0.21 are the precise versions you want, and those are not the versions you have.
I am not running a fork of create, just the official one from modrinth
Enabling shaders disables Flywheel's optimizations. Nothing we can do about it. Check f3 and make sure your 3060 is listed on the right side.
My 3060 is listed and the weird thing is that this fps drop is completely new, i never had that problem with shaders and fabric create before
or you can use iris flywheel compat to keep flywheel enabled when shaders are used
Sadly didn't fix anything :(
you may need to experiment with /flywheel backend
to see if another setting works better for you case
my last idea is to use spark to get a profile. maybe this will help pinpoint the pain point