I think if we actually have a Z-fighting issue, it should appear irrespective of the distance. In Sketchup, whenever there is a Z-fighting issue, it keeps showing even when I am too close to the surface, and vice versa. The fact that there is improvement with Orbit camera shows that it’s not a Z-fighting issue and something related to Shapespark rendering of that particular surface.
I happen to check in Sketchup if it’s really a Z-fighting in the modelling, but it’s not. Such errors have also come across many times before, but I did not report them eariler.
I had also done a experiement on this before as following -
- Such a rendering error occurs for surfaces which has a single face and doesn’t have it extruded/pushed.
- It appears when camera distance and the surface is far
- Error goes away when camera comes close to the surface.
- When switched to orbit camera, visibility of the error reduces even when it’s far (distance-wise)
Increased the width of the error surface by pushing/extruding it by 1feet.
Result - Problem got solved
Increased the distance between error surface and the surface on which it was placed.
Result - Problem reduced.
Re-uploaded the entire model by changing material name of the error surface
Result - Problem solved
So, I strongly believe that this error is caused with something related to Shapespark and not Sketchup.