The tutorial above is more of a dirty way of doing it
, or when you are doing cameras for a track you don't own the fbx for. BUT:
1/ if you DO own the fbx, then for full control, I recommend using the SDK editor.
Load the fbx in the SDK, then load the fastlane and go to cameras. You can define exactly the in and out point for each camera.
2/ if you DON'T own the fbx, you can try to adjust the file manually, more of a trial and error process. If the camera switchs too late, you might want to subtract a constant from the current IN/OUT points. For example:
BEFORE:
Camera_0
[..]
IN_POINT=0.9
OUT_POINT=0.2
[..]
Camera_1
[..]
IN_POINT=0.2
OUT_POINT=0.3
[..]
Camera_2
[..]
IN_POINT=0.3
OUT_POINT=0.4
[..]
..and so on.
AFTER:
Camera_0
[..]
IN_POINT=0.8
OUT_POINT=0.1
[..]
Camera_1
[..]
IN_POINT=0.1
OUT_POINT=0.2
[..]
Camera_2
[..]
IN_POINT=0.2
OUT_POINT=0.3
[..]
..and so on.
If still too late, then adjust some more. It's like when trying to sync subtitles
1/ if you DO own the fbx, then for full control, I recommend using the SDK editor.
Load the fbx in the SDK, then load the fastlane and go to cameras. You can define exactly the in and out point for each camera.
2/ if you DON'T own the fbx, you can try to adjust the file manually, more of a trial and error process. If the camera switchs too late, you might want to subtract a constant from the current IN/OUT points. For example:
BEFORE:
Camera_0
[..]
IN_POINT=0.9
OUT_POINT=0.2
[..]
Camera_1
[..]
IN_POINT=0.2
OUT_POINT=0.3
[..]
Camera_2
[..]
IN_POINT=0.3
OUT_POINT=0.4
[..]
..and so on.
AFTER:
Camera_0
[..]
IN_POINT=0.8
OUT_POINT=0.1
[..]
Camera_1
[..]
IN_POINT=0.1
OUT_POINT=0.2
[..]
Camera_2
[..]
IN_POINT=0.2
OUT_POINT=0.3
[..]
..and so on.
If still too late, then adjust some more. It's like when trying to sync subtitles