I am having problems taking screenshots of high-accuracy model of "thin sheets". They are just not presented properly in Creo 2.0:
The pictures pretty much say it all. AFAIK, I have all graphics settings maxed out (shade quality 30, smoothed edges, shade small surfaces on, antialiasing at 16X, ...) - but still these visual artifacts persist. I wonder if this is the best I can do with Creo 2.0, and did things get better in Creo 4.0 / 5.0 ?
Can you either share the model or provide the dimensions so I can recreate and test?
yeah, try this one please and see if you see what I see:
I can see that if I get rid of the holes, these "facet" lines disappear, but I am wondering if such a hack is my only option. I was hoping for an option I can toggle to force creo to "render all surfaces"
Yes, I'm seeing the same thing. Interestingly it only happens on the front side. The back side doesn't do it.
The root cause seems to be the small gaps between the layers. If A_, B_, and C_ are set to zero, the graphics anomalies disappear.
This would be interesting to send to PTC technical support. Do you have maintenance? If not, I'm more than willing to file a case and see what they say.
Thank you for looking into this. Are you using newer version of Creo? (we will be upgrading soon)
I don't mind if you send the model to PTC to see if they can use it as a test model, but I don't have the time to to deal with PTC support cases. Opening the model in Creo View and viewing it in "Shaded" mode gives me acceptable results. Curiously, viewing it in Creo View's "Shaded with Edges" mode gives me the same faceting problems.
As a workaround you could try these:
Good work-around. By the way, I can open the Creo .prt file directly in Creo View.
Your absolute accuracy needs to be smaller than the smallest dimension. Yours is currently set at .0005. The smallest accuracy value I get for your model is about .000827. Setting your accuracy to .0009 you should be able to set your smallest distance to .0009 or .001 and the issue goes away.
His model currently has the absolute accuracy set to 0.0003. Even if I lower the absolute accuracy to 0.00000001, the problem still occurs. I don't think this is an accuracy issue...
Are you saying you got the issue to go away? If so, please post the modified model.