The asset is not a player controller; it's simply a camera dolly with some real-time controls to fundamentally implement a "flying effect" around a 3D environment at runtime. The point was to drop an asset on the primary camera, then click go to have those easy controls.

"Time.deltaTime" is a great idea, I'll try to get the asset updated soon with the change.

I was looking at this review recently and wanted to be clear that movement in Generic Move Camera is based on the angle of the camera. So Q/Z is a local up/down pan, A/D is a local left/right pan, and W/S is a local forward/reverse. * If the camera is horizontal, then Q/Z moves up and down, A/D moves left/right, and W/S moves forward and backward horizontally. * If the camera was pointing down, the Q/Z and A/D provide horizontal pans while W/S move up and down the Y axis. For me, this produces a much more natural way to visualize and navigate a 3D scene. But as you pointed out, there are ways to modify the script to make Q/Z move up and down only on one axis. As for going underneath the terrain ... the best the script can offer is an X/Y/Z limit to force the camera into a layer or box in 3D. If you want the camera to be smart enough to roll along the terrain, it's best to simply implement a collider on the terrain and a rigid body on the camera. For others, the script works by calculating multiple movement vectors and rotations then merging them into a single movement vector and rotation that is applied to the camera. This allows the camera to be panning down and backward while rotating to produce very smooth transitions of all the vectors and rotations. When these are applied with other features such as Camera Leveling, X/Y/Z limits or using the horizontal pan modifier, the result can be faster than expected horizontal movements.