I have a big model, it starts near the origin but it stretch to 80+ meters.
I’m working with millimeters, but converting the document to centimeters didn’t help.
visual glitch.3dm (134.5 KB) (i have hundreds of geometries, here only some…)
(see the coordinates)
Objects near the origin are fine, object “far” away have this glitch.
Do I have to live with this or there are solutions?
(I watch the details here and there but geometries are built dynamically, moving the document origin (aka moving every geometry) is not possible because it would trigger mass recompute… )
Edit:
camera direction seems to matter, sort of that. If behind the camera frustum there is an object (or the origin), the glitch occurs. With other camera directions it look ok. … maybe…
I do not see the problem in the video of the orange showing through the green, other than occasionally a few very brief, small flashes of orange if I zoom in closely and pan and rotate quickly. Perhaps it has to do with how fast the hardware can process and display the image. DC System Info.txt (3.0 KB)
Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 32Gb)
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: AMD Radeon RX 6700 XT (AMD) Memory: 12GB, Driver date: 5-23-2023 (M-D-Y). OpenGL Ver: 4.6.0 Compatibility Profile Context 23.5.2.230523
> Accelerated graphics device with 7 adapter port(s)
- Windows Main Display attached to adapter port #0
- Secondary monitor attached to adapter port #1
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)
Anti-alias mode: 8x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: ATI Technologies Inc.
Render version: 4.6
Shading Language: 4.60
Driver Date: 5-23-2023
Driver Version: 31.0.14057.5006
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24 bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 28351 MB