mojira.dev
MC-262060

Fire animation is not smooth

The bug

The fire animation does not smoothly transition from the last frame to the first frame, leading to a choppy animation. It used to be smoother in 1.4.

Attachments

Comments 10

⚠️ Please do not mark Unreleased Versions as affected. You don't have access to them yet.

-- I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on Discord or Reddit

Please give me the resource pack for this issue.

Also, to make the report as effective as possible, please include steps to reproduce:

Steps to Reproduce:
1.
2.
3.

Observed Results:
(Briefly describe what happens)

Expected Results:
(Briefly describe what should happen)

It's the normal textures that are affected 

Cannot reproduce, all frames that exist in the texture file are visible for me.
That said, the animation isn't 100% smooth.

Go to release 1.4 and look. the texture is the same as fire_1 but the animation is smooth

 

In 1.4 the texture was still hardcoded and there was no actual texture file.
Sure, it's different, but that's not the same as frames being skipped. As of 1.5 and higher the texture was no longer hardcoded, and all frames in the texture file get used.
What you're reporting (frames being skipped) is simply not true; what is true is that some frames are missing altogether compared to 1.4.

Then why does it only play like 7 frames of animation before looping. In 1.5 there was a txt file for the fire animation that had only 7 frames in the txt file and looped quickly cause frames weren't playing. it was improved in 1.6 slightly but never fixed and it still that way to this day also you never looked each frame individually in the png 

There is no issue with the amount of frames that are played on the fire animation, the issue you're seeing is a poor attempt at trying to loop a snippet of the fire animation from 1.4 and below during the 13w02a switch to actual textures for animated textures, which used to be procedurally generated purely based on code.

Here's an edited fire animation containing numbers on the texture which demonstrates the frames being counted one-by-one:

[media]

Wait so are we missing frames or they just didn't convert fully? 

All 32 frames are used. However, since it's a snippet of what was technically an infinite animation before (to make them changeable using texture packs) and since there was lack of art skills and artistic knowledge it is now a not-so-smooth animation from the last frame to the first one.

DeadbushCarrot

(Unassigned)

Confirmed

Textures and models

rendering, texture

1.19.4, 23w18a

Retrieved