Animation and Rigging Tools: FAQ, Known Issues and Feature Roadmap

[ernstAlert]

@Efrye;220112

So if I got that right the 60 FPS setting is not meant for animations that are animated with 60 FPS, but rather to export 30 FPS animations for a 60 FPS game. Since I already have Maya set to 60 FPS I don’t need to double the frame range before exporting, so I’m using it a bit differently. Maybe I should just set Maya to 30 FPS and double the playback speed in Maya and UE4?

As for the second, more important issue: Rebuilding the skeleton worked! I didn’t even have to rebuild the rig file - simply going back to skeleton placement in the export file already did the trick. I should probably rebuild the control rig either way just to get everything up to date, but that’s going to reset the changes I made to the rig and in turn mess with my animations. I guess for situations like this it would be good practice to keep track of all changes I make so I can replicate them easily.

Placing the weapon file in the project folder solved that problem as well, but for some reason it doesn’t export any scaling in the animations. There are keys on scale in the exported FBX, but they’re all at 0. Exporting the weapon animation manually keeps the scaling intact, so I guess it’s not because of my FBX exporter settings.

Thanks again for your support , it’s much appreciated.

You are correct on that first part. Our animators would animate in 30 fps in Maya, and export to 60 or 120 for more fidelity (since the engine will interpolate between frames, getting more data in there, while making the file bigger, also means less interpolation for the engine to do, and thus less chances of it doing something you don’t want!)

I’m betting I wrote the weapon animation exporter before the engine supported scale It should be trivial to add. I’ll take a look tonight!

Thanks again for your support , it’s much appreciated.

Anytime