are near_clip & far_clip inactivating OB3D from the openGL context ??

Hi there,

I have my routine that track the distance between ALL my objects & my current position (cam position)
This updateDistance() routine is launch when an object’s position change and when the cam position change.

if the distance is beyond a particular limit, the object is disable from the OpenGL context, which reduce CPU job (and thus makes me quieter :p)

BUT I just thought about near & far clip.
Does they work only for visuals purpose ?
Is an object not currently visible processed yet by the CPU ?

Any ideas around this would be appreciate.