The interface for setting the FOV and clip planes can be very sensitive. Errors are most often seen as no sky dome or far away objects not showing up. (The skydome is usually your furthest object)


In 2b16 you will get this error message in your error log:

WARNING: Bad FOV paramaters, camera will use default fov and clip

Unfortunately prior to 2b16 we were not checking the return value for the camera, and thus it is silently useing the default values.

In release 2b16 we also converted the default FOV values to be 45, -1. This will cause the software to use a 45 degree FOV and compute the aspect ratio based on your display properties. You should never get an error with 45,-1 as FOVparams.

[B]The major problem that users are going to have, is that if the FOV values are bad and cause a silent error, the clip plane values are silently set to [0.1,1000] causeing the skydome to be "clipped"[/B]



Again the workaround is:

1) FOV params = 45,-1
2) clip planes = whatever values you want, but .5,5000 is recomended.

These values are found in Visuals.cmp or VisualsChaseCamera.cmp, whichever you are using.

Larry