[dstanton]

Anyway to set a hard padding to where the camera can go?

[Duion]

Yes.

[Caleb]

Yes.

Riveting.

@ dstanton
Try playing with the "cameraMinDist" and "cameraMaxDist" values in the player's datablock, or whatever the current equivalent is (I'm a few engine versions out of date).

[LukasPJ]

Yes.

Well that's just rude Duion. Please don't answer, if you don't intend to contribute to the discussion.

In the topic, I don't know how to avoid this issue, but there might be something in the documentation :
http://docs.garagegames.com/torque-3d/official/

Under scripting - > advanced, there is a guide called "Camera Modes". Might be that it can help you a bit.

[Duion]

Well look into the "theLevelInfo" in the scene inspector, in that you will find a value called "nearClip" which is set to 0.1 (10cm), this is the distance the clipping happens and if your camera gets closer you view through the surfaces.

You can try changing the value of nearClip to fix that, but the nearClip value is already set to a quite ideal value, so you are left with the alternative of preventing the camera getting too close, like with playing with the camera distance values, but that is not going to the root of the problem.

The ideal solution would probably to have some kind of collision box for the camera of 10 or maybe better 20cm so the clipping will never happen, I think the current camera is just a point.

If you are a pro you can also try to change the clipping algorithms in the source code, it needs a fix anyway, since it is slightly different in openGL and directX at least it was like that a while ago, I could not remember if we fixed that.

[dstanton]

The attribute 'nearClip' effects values for every object and terrain piece (not just the camera) and makes it all funky if you go below the value .1. I'll look into wrapping the camera with a collision and report to this thread if it does anything for me.