Some kind of graphical/model rendering accuracy error?

[Max_Marz]

Working on a model that was produced with creo then exported as a step/iges I noticed some wonkiness' with this groove that is supposed to be straight for the 'lead-in' portion of the part after opening it in fusion to start CAM. I assumed it had something to do with the source model or how it was exported until I went back into creo with a colleague and did some investigation. Opening the exported mesh file back into creo showed no such anomalies so I tried to investigate further with fusion. I created a plane where the groove looked the widest to split the model so I could measure the width of the groove at the intersection.

In doing this I noticed that as soon as I split the model, the initial area of the groove 'became' straight?!?!
After seeing that I assume the issue is not with the source file but some kind of rendering tolerance and so I ask you, beloved forums, in hopes of some kind of explanation. ❤️
I would prefer not to post the .F3d file if at all possible, thanks for your help.

Overall view:

<Model before being split, Model after being split>

[johnsonshiue]

Hi! I could be wrong but I don't think this is a graphical error. More than likely there is something wrong with the geometry. A simple test is to create a sketch on the split plane and project the edges.

If possible, please share the file here. Forum experts can help take a closer look to understand the issue better.

Many thanks!

[TrippyLighting · Accepted solution]

Select the body in the browser, right-click and select “display detail control” from the menu.

Change it from “adaptive” to “fixed/high”. Provided feedback if that helped.

if it doesn’t then we definitely need to see the model, or at least the timeline of the design.

[Max_Marz]

Bingo, Thank you so much Trip.

Also, Johnson, thank you for that suggested test of projecting the edges into a sketch. I tried that and it confirms it was simply a display fidelity situation solved with "display detail control"

However, I still see some anomalies and this test confirmed that the (separate) issue is present with the source file.