Animation Bug Corrupts Frame Rate for IPC
**ATTENTION: **
v4.14 through v4.17 Animation Bug Corrupts Frame Rate for IPC
It was brought to my attention today by lion032 (thanks dude) that all the IPC curves did not have keys on the 30fps ticks when a user added them, making calculations screwy. Which my first response was no way, everything looks perfect here! 
After an hour and a half of investigation and back and forth, we realized the basic problem. Much longer to trouble shoot and quantify the exact problem and best solution.
THE PROBLEM:
There is a bug(feature? oversight?) in v4.14 and forward that corrupts and re-samples the key frames in animation .uasset files from v4.13 and earlier. At least custom attributes anyway. It re-samples the curves to what looks like about 31fps. (???) Double you tea eff. See pics below.
The current Rifle 2.7 Pack is a v4.10 project, so the animations are as backwards compatible as possible for earlier projects. This has not been an issue yet as animation assets are forward compatible - so we thought till this wrinkle.
So adding to a v4.10-4.13 project leaves the curves alone, but adding to v4.14-4.17 re-samples the curves to some random 31 something frame rate. What the heck. :mad: If you are not using the custom attribute curves it may not affect you, but it may screw up calculations if you are, or who knows what else is lurking.
THE QUICK FIX:
There is a quick fix, it’s easy.
Open up your v4.14-4.17 Project they are in and corrupted, and go to the Animation directories.
Go to the Project directory on your HDD, and into the “Source” folder where all the original source FBX files are in the “FBX” folder.
Per matching directory and animations, drag and drop the FBX files into the matching directories in the Editor. (You can select and drag an entire folder full of files at once)
You should see a succession of popups saying each animation was “successfully re-imported”.
The In-Place IPC may be the only ones necessary, but I’d do them all in case the body keys are also corrupt.
This will refresh all the animations and set the curves back to 30fps frame rate.
Fixed.
THE OFFICIAL FIX:
I will likely update the Marketplace files with an added duplicate v4.14 project with all the same files (which I have already made and updated on our www.mocaponline.com web store).
I will instruct Epic to use the v4.10 version for adding to v4.10-4.13, and use the v4.14 version for adding to v4.14-4.17. (This is automated by the vault, common place, user needs to do nothing to get the correct version.)
Epic support has been pretty slow lately, we’ll see how long it takes…
Sorry for the glitch, let us know if you have any questions! A lot of folks won’t notice any problems, first we heard of it, but for others digging deeper with the IPC this is an issue.
Opened in 4.17 - Re-Sampled:
Opened in 4.10-4.13 - Original 30fps Intact: