I have an Orthographic camera animation that I have imported and I need a different Ortho width on each frame. I see via the camera details and the sequencer that I can key in the values for each frame, but I have hundreds I need entered.
I can get a list of the values I need from 3ds max, but I would like a way I can get them into unreal and applied to the animation with out having to do it manually one frame at a time.
Can you export an fbx from 3ds max and import that onto the camera track in sequencer?
Currently I’m importing the camera via datasmith as it seems to easily import the camera location and animation (minus the ortho width) when I tried an fbx the rotation was all off and it didn’t look like a regular camera actor. not sure what it was.
I actually think I’ve partially solved my problem I just need to iron out some kinks. what I’ve done is is made a spreadsheet of the time values and width values I need in the animation and imported that as a float curve. I then plugged that into the timeline which then controls the ortho width of the camera. It mostly accomplishes what I need, but it seems to possibly be offset or something. It kind of looks like the ortho width is being applied to the wrong frame or if its not doing the exact value I entered in. I set the points in the curve to be constant so there’s no interpolation between them, but there’s still something going on.
Part of the reason I think is because the camera keys are displayed as frames, but everything in the timeline as far as I can tell can only be listed as actual time so I’m having to convert those in the spreadsheet.
so I’m currently trying to figure out if the issue is just an offset in unreal, or if my time conversion is not accurate enough.
So it seems to finally be working properly. I had to adjust the time values on the spreadsheet as previously I think excel was rounding the numbers differently than I needed which was throwing it off. but I found a standardized conversion for frames to time and used that. I also had to put some extra points at the beginning and end of the string to make sure the first and last frames used the correct values. After that it seems to be working.
