since it`s a script that runs the handheld camera, somehow I missed to realize where to find it (inside of AS folder\Resources\Support\scripts\menu\Camera) - it is easily modified. It surely leads to the try&error process but it is tameable.
I just want to make sure this is clear. You may already understand but I wasn't sure from the above statement. The handheld camera "Script" does NOT control the motion. It simply creates keys only on frame 0 of the camera and sets them to predefined noisy interpolation values.
You don't actually need the script at all to do the "camera shake". All of those settings can be done by hand simply keying those camera channels, setting them to noisy and changing the values (default noisy values are HUGE. The amplitude is MUCH higher than the script applies).
If you use the camera shake script you can change those noisy key settings created on frame 0 by simple selecting the keys and right clicking the key frame and choosing "Noisy" from the pop up. The current settings of the noisy key will show in the pop up. You can modify the settings (very small amounts) to try different values.
The graph editor has NO effect on noisy keys because they are controlled in a different way. The graph editor only lets you see the motion and noisiness of the motion.
Still, if you interrupt it trough the MotionGraph - it acts a bit weird since that would pretty much disturb it`s randomness and the movement gets quirky and jumpy, a lot. In my case it was unusable. Also I could not manage to convert these into the beziers which made intervention even more tricky. It was getting me closer and closer to the manual keyframing.
The movement getting "jumpy and quirky" is not because you interrupted the randomness at all, it's because the default value of a new noisy key frame is MUCH more extreme than the values inserted with the camera shake script. The default values are HUGE compared to adding keys with the script. So when you simply add a default noisy key frame, the motion is going to look way different. You need to make sure the values of new keys are "closer" to the values of the original noisy camera shake keys.
For example the default values of a newly inserted noisy key are:
The values inserted by the camera shake script are:
So if you add new keys, use the settings of the camera shake script to start with. Experiment with small changes to the amplitude and scale to get what you need.
You may just want to copy the keys from frame 0 to a later frame, then right click and modify those copied frames. That way you can see the values already set and know how much to change them.
In the following image the keys on frame 0 for the camera are the ones set by the script. Later in the timeline you can see the motion "smooths out". I added a key frame and changed the values:
Code: Select all
Frame 0
Amplitude: 0.0274
Scale: 4
Frame 54
Amplitude: 0.01
Scale: 6
The problem with setting the numbers for noisy keys is that you can't "see" what those numbers do visually, it's all trial and error guessing how much to change the numbers, playing it back, changing the numbers etc. By using the graph editor you can actually see the results of those numbers in the "zig zaggy" lines in the motion graph display (you will need to select the camera channels and scale the view in the timeline vertically to see the graph).
I hope this was helpful. You don't need to modify the script to change the values. In my opinion it would be much better to simply change the values of the noisy keys.
[edit] if you wanted to "fade" or slowly decrease the camera shake over time, simply add a series of noisy keys with smaller and smaller values then apply a "normal" or smooth key interpolation. [edit]