FBX frame rate issue

FBX frame rate issue

Anonymous
Not applicable
6,261 Views
6 Replies
Message 1 of 7

FBX frame rate issue

Anonymous
Not applicable

Hello everyone,

 

I'm trying to export a fbx file from a 12fps scene for a VR project.

The problem is the export is actually 30fps.

When trying with a scene with 24, 25 or 30fps, the fbx export has the right framerate, but not the other scene frame rate.

Do you have an idea on how to solve that issue ?

 

Thank you!

0 Likes
Accepted solutions (1)
6,262 Views
6 Replies
Replies (6)
Message 2 of 7

sean.heasley
Alumni
Alumni

Hi @Anonymous and welcome to the community!

 

Have you tried setting the frame rate export setting in you preferences?

 

Also, if you create a new scene and try to export from there does the same issue occur?

 

 

0 Likes
Message 3 of 7

mspeer
Consultant
Consultant

Hi!

FBX export works based on predefined fps values (limited entries).

Although there is a variable reserved for a custom framerate it's not used by Maya.

0 Likes
Message 4 of 7

sean.heasley
Alumni
Alumni

Hi @Anonymous

 

I'm just checking in to see if you need more help with this. Did the suggestions that @mspeer and I provided work for you?

If so, please click Accept as Solution on the posts that helped you so others in the community can find them easily.

 

 

0 Likes
Message 5 of 7

Anonymous
Not applicable

Hello,

 

Yes, I did indeed change the frame rate in the preferences as 12fps, and this with a brand new scene also, the same problem occurs : the fbx exported is 30fps for a frame rate of the scene at 12fps.

0 Likes
Message 6 of 7

Anonymous
Not applicable

Hi mspeer,

 

But is there a way to force maya to use a custom framerate?

0 Likes
Message 7 of 7

mspeer
Consultant
Consultant
Accepted solution

Hi!

If you choose a framerate that's not part of the predefined values you will get 30 fps as default.

I doubt you can force Maya to use the custom framerate either for saving or for loading.

 

Also Maya 2019 seems to ignore any framerate setting (looks like first bug found).

0 Likes