One of the problems that many animations have is that they are too clean. Too smooth. Too perfect. In real life, things are very rarely, if ever, perfect. There's always 'noise'. Noise is that 'thing' that breaks up what should be perfect. Whether it's the dust on a counter top, skips on a CD, the slight shake of a camera, the variation in the gate of someone's walk, basically just the slight bit of randomness that is in everything around us.
If your scene has a moving camera, it's very rarely as steady as a stationary camera. There's always some degree of shake. Sometimes a lot, sometimes just a very small amount, but it's almost always there. CRYENGINE provides a solution for adding noise to your camera to give your dynamic cinematic scenes a more realistic effect. You can add a Camera Shake track to your Camera entity in Track View.
However, to get the desired effect, you cannot just turn on and turn off the shake in Track View. You need to tweak the exposed values below to get a realistic result:
Shake > AmplitudeA, AmplitudeB, FrequencyA, FrequencyB
AmplitudeA (ampA), and AmplitudeB (ampB) are just multipliers that multiply the camera's AmpA and AmpB parameters!
They are separate overlapping and accumulating multipliers of the amplitude camera parameters that generate the final camera orientation!
The following non-animatable parameters exist on the camera entity:
So here above is the Yaw, Pitch, Roll or in CRYENGINE: Z,X,Y. These are in the parameters of the Camera Entity and are not exposed in trackview. In Track View AmpA track is a multiplier that multiplies the Amplitude A camera parameter.
Above the AmpA is 0,0,0, so no matter how much one cranks the Amplitude A in Trackview, it will still be multiplying 0,0,0 and the camera will not shake.
Here is a video that better explains the relation between the amplitude camera parameters and the track multiplier in trackview. This camera motion is playing directly from trackview, the track AmpA multiplier is always 100, but the x,y,z camera parameters are changing:
Frequency is sort of what it means, how frequently the camera changes orientations. Here's a video cycling through frequency multipliers of 1,5,10:
First let's take a look at something that looks good:
Why does this look different than most other times you see something heavy fall in the game? Because the curves were tweaked to achieve the result.
To achieve really good camera shake, it is important to edit the fCurves. When you add a shake keyframe in Track View, the default fcurves have wide tangents which causes extreme easing in and out.
Notice that the value takes a really long time to get to the desired peak. Most of the time the intention is to have a quick impacting shake (like a punch in the face); with many explosions, shakes or jolts, we want the effect to be immediate!
So how do we get this more immediate jolt? Compare the two curves below:
So now we have a 'punchy' hit. In order to get a visually linear falloff of shake, the curves are tweaked until they looked like this: