lilly.c2d (136 KB)
Is this an issue with M2 Macs by chance? This is a pretty simple model and should’t take much in the way of computational horsepower.
It opens and simulates instantaneously on my (Windows/x86) aging PC
2 Likes
Opens like any other file on my MAC/Mojave.
2 Likes
It almost has to be an issue with this being Apple silicon and therefore going to through an emulation layer (rosetta). I will try the file later on my PC.
I just tried on my M1 MacBook Pro and it was almost instantaneous. No delays in the simulation.
1 Like
Just tried on my Windows machine. Maybe an issue with the CC 757…the latest beta. I will try an earlier version.
Went back to 756 and still has the slowness. This is inexplicable.
If I enable either of the “VEE” toolpaths, it takes a long time.
If I replace the tool with the 60° tool from the library, it’s very quick. ??
1 Like
I feel kind of guilty as I am a software developer and I get frustrated when folks say “no workie” without doing any modicum of work to understand the problem…and that is exactly what I did here.
Good find. You have narrowed it down to the problem being rendering a simulation for a custom vee bit. This behavior is present on both my WIndows machine and Macbook. @Julien is that a known problem or just the reality for custom tools?
I suggest you send the file and pb description at support@carbide3d.com for advice, they’ll send it to the developers for a check
1 Like
For what it’s worth, the Rosetta system has been flawless with CC. In fact, we don’t test with Intel Macs any more because the M1 has been sold and is much faster.
I suspect you made that V cutter really big, which increases the simulation time a lot.
1 Like
It’s labeled: “1/8 60 Degree VEE Channel”. I suspect it’s too small, rather than too large??
There’s a problem with someone else’s file that has a custom tool. You can’t see the tool parameters.
More of a support issue, but also an issue for people wanting to share files.
I sent the file to support@carbide3d.com. Will was able to observe the slow behavior even on a Windows. So it is being investigated.
1 Like
I am still checking on this so as to make a proper bug report — need to determine the difference between the tool definitions which triggers this, then test on my wife’s M1 Mac just to be sure.
Decided it was better to not interpose my efforts at testing, so uploaded the files and observations as a bug report.
That’s his description, so it could actually be 8".
Yep, it’s a support problem at a minimum.
It’s very slow if I enable the chamfers toolpath, but it’s instant if I change that tool to a #302 (which creates an equivalent toolpath). I’m 99% sure the tool got entered incorrectly as being very big.
2 Likes
This topic was automatically closed after 30 days. New replies are no longer allowed.