I am trying to understand the rlc1 rendering process better.
Background:
If something is far enough away then it is not rendered. For instance if parts of a sky are more than about 58,300 from you then those parts won't be rendered and the default sky will bleed thru. Or say there is something you want to hide. If you put it about 60,000 away then it won't be rendered.
OK, here are the thoughts/questions. Since, things that are not seen are not rendered, is it a waste to put something so far away to hide it. Why not just put it somewhere it can't be seen, say behind a building some place close?
If you do put something real far away (greater than 60,000) then is the system smart enough to "forget about" the stuff there? If yes, does that mean the things there don't count in your max prop count considerations to reduce lag?
OK one more. Say you have a huge object. It is located so that the half farthest away from you is beyond the 60,000 point. The half closest to you is textured invisible. You won't see anything. but lag wise, is the system smart enough to ignore it or will it have to be rendered as an invisible object?
To reiterate, do things that are far enough away to not be rendered still count in your prop count?
TIA
