- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
So the last few days I've been starting at a MacOS beach ball more often than not.
It seems part of my issue was my sketch had too many points which caused the solver to become overloaded.
In this case, the sketch was a single polygon with 160 edges. I've noticed in other cases, for example, some .svg files where there are hundreds of points. The solver again will struggle.
Another example. When trying to Fillet many edges. If I select say 50 edges to fillet and change to a fillet size that is not acceptable for one of the edges everything comes to a grinding halt.
Now in my eyes, I feel like these requests are not that "intense" in the grand scheme of computing power but really what do I know. And I feel like my designs are only gonna get more complicated as my skill progress. Obviously learning to work efficient and smart in both a time and computer solver based approach is part of this progress.
But clearly beyond my poor design approach. I've overestimated the computer's ability.
My questions after that long winded opener are:
-When it comes to sketches, what are some maximum amount of lines and points you would use before splitting up the sketch?
-What are some bad design intents that would cause solver slowdowns?
-Does upgrading the CPU allow you to work with bigger and more point dense sketches?
Solved! Go to Solution.
