Circles issues in Creality Print v5.1.4.10249 mac

Hi,
I had some issues with circles/rounded surfaces when I upgraded from Creality Print v5.1.1.9490 to Creality Print v5.1.4.10249. It seems that Creality Print is trying to overemphasize the edges of rounded prints. It may occur due to many stl files are being generated using not exactly perfect circles/rounded surfaces (such as tinkercad that generates a circle that is not truelly a circle). So, Creality Print may be trying to focus on squaring things instead of rounding them. I downgraded it back to Creality Print v5.1.1.9490 and it started printing rounded as before.

Please, see some pictures from the same stl sliced/printed with the old and new versions of the Creality Print.


My problem is very similar to this. Some circles show these ridges at each intersection of segments in the STL. I just got this K1 Max and have never used Creality Print before, so my experience here is limited, but I used an i3 design for 10 years and never had a problem like this.

The effect shown seems to get larger with the size of the circle. I don’t know if it’s just circles (I’ve only done two prints - one of a design from Printables and another of my own making).

A few other observations:

  • The circles ARE circular, so I don’t think it’s a belt tension issue. (So this is not like the other circle posts in this forum)
  • The slicer preview shows a normal circle, not the bumps
  • The attached image is a 96-sided circle that’s 79mm in diameter. I expect to see the sides a little bit, but not to have large bumps at each intersection.
  • I’m also on a Mac.

I guess I’ll try to find an older version of Creality Print and see if the problem goes away? If anyone knows of a change in the latest version that would cause this, or a setting that can be adjusted, I’d sure appreciate it.

Thanks!

For what it’s worth, I just use Orca Slicer now and it’s fine.

Just an update about the issue. I installed the latest version (Creality_Print-v5.1.6.10470) for Mac, and it’s working better than v5.1.4.10249. It looks very similar to v5.1.1.9490. It seems that the problem happened only with v5.1.4.10249 and it was solved with v5.1.6.10470.
Cheers.