mojira.dev

kekpafrany

Assigned

No issues.

Reported

MC-226209 Performance problems in 21w19a-21w20a with high res resource pack Duplicate

Comments

1.17-pre2 still has the bug.

1.17-pre2 still has the bug.

1.17-pre2 still has the bug.

1.17-pre2 still has the bug.

So since my ticket was closed as a copy for this ticket, I would like to ask my questions here:

Quick recap: I'm working on a resource pack and it worked fine in 21w18a and prior. But when 21w19a came out with the new engine the game dropped to 0-1-2 fps, and I'm keep experiencing it in 21w20a and 1.17-pre1 versions. It doesn't help if I go deep or high.
I tried out other resource packs with similar high resolution (512 pixel) and they didn't cause fps drops. So I looked for the files in my pack that do cause them and I found that animated blocks became problematic. If I have mcmeta files for block animations, which were working in 2 snapsots ago (like kelps, shiny ores, lava etc) my fps drops.

So this new engine seems weaker to me in this situation. Is there any JVM arguments I could set up in the installation to work as in the previous snapshot and full versions?
My current line is this, but I'm not technical enough to understand every part of this:

-Xmx8G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M

1.17-pre1 still has the bug.

1.17-pre1 still has the bug.

Well, thank you, I will check that ticket. I used the search function before but since I didn't know what to look for in my case, it was impossible to find that ticket.

But my problem is it had NO performance issue at all in 21w18a and prior versions. But in the last two snapshots (with the java 16 changes) it has. I'm creating a resource pack for 1.17, that is why I want to use always the latest snapshot.

I made video about them as you asked:
21w18a https://youtu.be/Hb6-rrtJJms - it runs playable, as it should
21w20a https://youtu.be/6tQmpH6pdh4 - it drops to 1-2 fps, unplayable

21w20a still has the bug.

21w20a still has the bug.

21w19a still has the bug.

21w19a still has the bug.

21w18a still has the bug.

21w18a still has this bug.

21w17a still has this bug.

21w15a still has this bug.

I'm trying to make resourche pack for 1.17 version using the 21w13a snapshot, and this issue is still there, still unsolved. Such a small thing, it should be easily fixed. 😞 Why is this still unsolved for 2 years? You have to move 2 pixels on the texture map.