Va Sections register extreme project limits causing AO artifacts?

[djhg]

Explorations in the post below seem to determine that Va sections create enormous project extents. This appears to require Rhino’s Ambient Occlusion renderer to spread its shading resolution across such great distances that a regular ridge pattern is rendered in closeup on surfaces which are in fact smooth.

Texture Map Renders with Landscape Contour Lines

This is the default texture on my projects. I don’t recall setting that, I think it’s a Rhino default texture or a VIsual Arq default texture. I could switch to another one and perhaps solve this, but I’d like to understand what’s happening here. As you can see, in the same Rendered Ambient Occlusion View mode, the texture is rendering ina way I’d never want it to, with contour lines in an ortho view. It renders as ridgelines on surfaces which are in fact smooth, which causes confusion. [Co…

[fsalla (Francesc Salla)]

Hi @djhg, after reading the linked post, it looks like the problem is related to invisible geometry located in far away high distance, that made the camera took a very high value. VA sections are unlimited in verticall directions. But this should not affect the camera Z location value, if there are no objects in faraway distances. I’ve opened your template posted in the other thread, replaced the Top viewport Detail (that has a big Z location Camera value), with a new Top view Detail, and the Z camera location value gets a consistent value.