I am using a NVIDIA card (Quadro 600) but only get that bleed thru effect when I have some of my parts set to transparency, such as expanded metal. My settings are set for performance, and even so the jaggies aint that bad.
new graphics system...I'm sure of it. Didn't have any of these problems in 2011, 12, or 13.
Multi-core graphics... When I opened these files they barely bled into another core (4 core i7) ran as much as 30percent (1 core plus 1/5 of a second core). When zooming in and out there was a threshold that would cause this effect, but that threshold was not absolute, it would change a little (one middle button roll click in or out would cause the shadows to appear or disappear). During scroll wheel zooming, the CPU level would stay down around 15% never using second core when turning on shadows.
intelligent drawing order... likely the biggest culprit. The order is placing shadows before surface occlusion, during certain levels of zoom detail. Not too intelligent, shadows are expensive processing, unless all shadows are processed only once (old ACAD 3D engine process where ray tracing is calculated once and reused regardless of angle, and stored as a data file). If shadows are processed that way, then they could be reused faster, accept they forgot to call down the occlusion feature to weed out which shadows are shown at certain zoomed in detail levels. I'm assuming shadows were calculated at several sizes. Zoomed way out (little shadow calcs), zoom way in (detailed shadow calcs), are the obvious levels. This would explain why the issue is predominant when zoomed in. It is possible that the second level is the only one with the error.
This is causing all shadows to be displayed at the close detail levels making it difficult to understand the outer surfaces. Since I am accustomed to working in old 3D wireframe, I can survive, but I'm sure I'm the only one of my staff that can.
With Ambient Shadows.
Actually when i zoom in everything displays correctly.
Unfortunately update 1 does not address this issue. Nor did it address the issue of the scrambling display. I'd think that the graphics performance of the program is way more important than the small bugs they fixed.
Fair warning, if you get this type display, first thing you should do is save any unsaved work in Inventor. Just pressing the windows restore down button can potentially crash Inventor at this point.
For the scrambled screen issue, remove these registry keys:
Thou has slain the Jabberwocky... Well at least one of them.
Access a broad range of knowledge to help get the most out of your products and services.