@Ragnar_Svensson What’s the reasoning, if there is one, for the -1 to 1 default camera render range? Are objects outside of the range actually ignored, or just clipped like what happens with sprites?
1 Like
They are clipped but still active. If you put a script on a game object and print() in each update() call and move it outside the camera range you should still see the prints in the console.
2 Likes
The reason for the particular -1,1 range is quite weak. You need a bounded interval to define the rendered frustum. You can basically pick any interval, but you need to pick one. We just picked -1,1 as the default because it is numerically small (which has an impact on depth resolution) and one of the only “intuitive” boundaries we could think of. [0,10], [0,100], [0,1000], [-100,100] would all have been even more arbitrary. As @britzl says, it only has an impact on rendering and can be easily changed in the render-script by modifying the two last parameters to vmath.matrix4_orthographic (near and far), which is used in render.set_projection.
3 Likes
Thank you for clarifying!
1 Like