このサイトを正しく表示するには、最新のブラウザを使用し、Javascriptを有効化してください。

Image Sequence FPS locked at 12

chelizardo

Hello

I successfully brought in a series of 7 png's to use as an image sequence, and was able to add it to a slot, parent it to a bone and play it in the animation, however, when I try to change the FPS, it reverts to 12. What am I doing wrong? Thanks!

Misaki

chelizardo Hmm, I have no idea why it would be in that state. What version of Spine are you using?

Erika

chelizardo Make sure that you are keying the change, or that you have autokey on when you change the sequence FPS!

Spinebot

It seems like you are encountering an issue where the FPS for your image sequence is locked at 12 and cannot be changed. Here are a few steps you can take to troubleshoot and resolve this issue:

Check Timeline FPS: Ensure that the timeline FPS is set correctly in the Playback view. The timeline FPS can affect how your animation is exported and played back. You can find more information about setting the timeline FPS here.
Sequence Key FPS: Make sure that the FPS for the sequence key is not conflicting with the timeline FPS. As mentioned in the context, if the FPS specified for a sequence key is the same as the timeline FPS, it can cause issues. Try setting the sequence key FPS to a different value than the timeline FPS.
Export Settings: When exporting your animation, ensure that the FPS in the export settings matches the desired FPS for your sequence. If the export FPS is different from the timeline FPS, it can cause discrepancies in the frame count and playback speed.
Sequence Properties: Verify that the sequence properties are correctly set. Ensure that the sequence number and path are correctly formatted. You can refer to the sequence properties guide for more details.
Project Settings: If none of the above steps work, it might be helpful to check the project settings to ensure there are no overrides or constraints affecting the FPS.

If you continue to experience issues, you might need to review the project and images to determine the exact cause.

chelizardo

Misaki Latest version 🙂 I have auto update on

chelizardo

If I open a new project it works fine. Its just this project for some reason

Misaki

chelizardo Sorry for the late reply! Could you send us an email with the Spine project that is causing the problem?: contact@esotericsoftware.com
Please include the URL of this forum thread in the email so we know the context. Then we can take a look at what's wrong.

ErikS_in2D

I'm having the same issue!
I can not get my png image sequences to be set at anything besides 12fps? I'm currently working at a slot games studio and i'm trying to import a previously animated game character to use as reference for timing on a new character rig. The reference was originally animated at 30fps, but when imported it defaults to 12fps. I can write 30 in the box, but as soon as i click outside it jumps back to 12fps. I'm scratching my head here.

I'm using spine 4.2.36 on both an Intel Mac and a Windows PC (same problem on both machines)

Any help is much appreciated!

Nate

I see entering the number doesn't set a key, even with auto key enabled. We'll fix that. In the mean time, please click the key button next to Sequence to set a key (or update an existing key).

lucascarvalho

Hey everyone, I encountered a similar issue with my project.

During my investigation, I noticed a correlation with the use of physics. You could try removing the physics constraints and adjusting the sequence's fps. In my case, adding a keyframe change to 0 the mix setting of physics allowed me to edit the sequence successfully.

I'm unsure how to assist if your project doesn't involve physics and you're experiencing this issue.

ErikS_in2D

@lucascarvalho Thank you, that absolutely worked! That's exactly what I did, I reduced the mix value of all the physics constraints to zero and keyed them. Then the it let me set the fps to 30. Thank you!!

Nate

I didn't notice the interaction with physics, but our fix in 4.2.37 handles that too. Until then it may be sufficient to deactivate Simulate rather than set all the physics mixes to 0.