Get rid of "clip start" and "clip and"
Why do we need to have "clip start" and "clip and"? I can imagine that these features are exists to prevent slowing down the machine if we have a lot of objects. But i'm not sure. And even if so, i don't think that is an issue. Some times i have lots of objects in my viewport and it works fine. I always set "clip start" = 0.001 m and "clip and" to some very high amount and nothing bad happens. What if we just get rid of these?
6 Comments
Since Blender can store objects arbitrarily far away, clipping is required to compress the positions of objects into finite numbers.
This can not be done because it starts artifacts, it is another thing if this value was some kind of adaptive to the scene, and determines the optimal values prnt.sc/1tdxmwj
Yeah it's just a necessity of how rendering works, it's not like some random nerdev just though it was funny to make things never render on arbitrary conditions.
Did you ever get those artifacts you show on the screenshot in your usual work if not setting very huge values like 500000m? I did't. And many people who do tutorials, setting those values high (but not as high as 500000m) and low and still no artifacts. Maybe there were artifacts in some old versions. I'm using 2.92 and everything just fine. ) Maybe it's time to loose clipping viewport feature.
Or, there are artifacts but only with "clip and" and no with "clip start"? If yes then devs can delete "clip start" only.
Yes I got them. Importing a large scene for a studio project for example. It's not a matter of version, and removing the values won't change how the rendering process works. There will still be clipping no matter what you think about it.
That is bad.