Think of it as slicing the model at the defined height.
3 Likes
It turned out that the contour path didn’t recognize the error and used a 10mm depth of cut for the calculation. It should be fixed in 804.
2 Likes
804 is up at Carbide Create Beta Downloads
- (FIX) Bug in contour toolpath if start and end depths were equal.
- (FIX) Try to fix rare crash in V-carve toolpaths.
- (FIX) Try to fix rare crash in toolpath simulation.
The bottom two are shots-in-the-dark to fix BugSplat reports where we see a crash, but didn’t get good debug information.
4 Likes
Couple of notes about CC v804 Beta:
- Still seeing some weird issues with the 3D modeling list. Will have 4 components created including 1 which is an STL import. Then try to add another vector component & upon hitting Apply & the program re-calculates the model, the STL component will just vanish! Hitting Undo does not bring it back. It just seems to lose it.
- The calculation of the 3D model seems to cause the program to sort of Hang & become unresponsive until the model is done
- The 3D Modeling always reverts back to Cherry colour after a component change & re-calculation. While not the biggest issue, it certainly does become annoying to have to always go back to the Toolpaths tab & Simulate to change the colour back to one I want to see the model in.
- STL import components seem to always get their position reset upon making a change to the STL import. After setting up an STL, I adjust the position inside my other vectors, then decide to edit the STL settings, re-calculate & the STL position reverts to the initial setup position I’m guessing? So then I have to re-position the STL back into the position I had it in.
- On the plus side, I haven’t encountered any hard crashes!
2 Likes
Are you able to come up with a series of steps to make this happen repeatedly?
2 Likes
FYI- Joel sent us a file with the error and we got it fixed for the next release.
6 Likes
Glad a fix was readily achieved!
Can’t wait to try the next beta version. As great as it is to be able to edit the 3D modeling components now(which is superb!), having components weirdly/inexplicably duplicated/lost is a pretty tragic set back.
We just posted 805 with the fix. Carbide Create Beta Downloads
4 Likes
That certainly seems to be working more reliably in the Components list now.
With all the recent changes, I was curious how CC handles utilizing a V-bit with 3D finishing - so I tried it. Guess it’s not really supported, but it makes for an interesting simulation result.
Seems to place the point of the bit somewhere below the model - using the non-cone shaped part as the end of the bit? Would this then generate G-code which would cut way below the intended surface? I may have to try just to see what it does. Bug or just unintentional consequences of not supporting V-bits in the 3D Toolpath generator?
Send over the file and we’ll take a look.
Looking at your file (sent privately) I suspect it has to do with the way the tool was defined and there’s probably a bug too. We’ll dig into it.
EDIT- We found the problem- it’s definitely the V bit not being handled correctly in 3D. We should be able to get the working relatively quickly.
2 Likes
That would be really awesome… Cause then a Taper Ball Mill could be setup as a pseudo-Vbit & the simulation could give quite close representation!
Another thing I had noticed while watching the tool simulator in that project file was the behavior of the 3D Roughing toolpaths - and is something I’ve noticed before while running other projects.
When the roughing gets down to just the outer ring, it’ll make in/out edge paths which clear out all the material between. But then it makes a raster path within the ring as if it somehow could have missed some material. Some layers it reverses the order of the rim/raster paths.
Anyway, I just wondered if you guys had ever looked at refining how the algorithm works cause it can add significant time to the roughing operation. Is there any way it could refine itself by checking if a path function is actually removing any material?
Constructing new models is hugely improved. However, when opening in V8 Beta 5 a file created with V7 and not altered, the rough & finish toolpaths work improperly (at least according to the simulation). These toolpaths appear to get the Z height wrong. Is this a known problem or should I send the c2d file?
If it’s got 3D components in that file, it probably won’t load correctly going from V7->V8. We made some big changes to the file format and internals, so we decided to not load the older 3D components because they don’t directly map to the new code.
2 Likes
In that case, shouldn’t V8 pop-up an impossible-to-miss warning?
It sounds like right now it’s silently failing, the worst kind of failing.
(I haven’t tried V8 myself, so if there is a warning, don’t ignore it people!).
It’s currently in beta testing. So hopefully notifications like that are on the to-do list.
With or without a pop-up window the inability to import V7 files using STL is reflected in the Model window (mine was empty, including even the non-STL entries).
I’m now attempting to establish a workflow for transitioning V7 models containing STL to V8. (Someone please jump in if my conclusions are wrong or if there is a simpler method.) I’m referring solely to the 3D import window.
It appears that 3D Orientation, Angle and XY Scale, along with Name and Merge Type, work the same in V7 and V8. The V7 Height setting can now be entered via the Scale to Height button in V8, that in turn establishes the associated Z Scale. I’m guessing that the V7 Invert setting can be accomplished in V8 using a separate 3D import with an opposing Add/Subtract merge type? The Remove Z Height setting from V7 is slightly more challenging. (As an aside, I have found this useful for constructing 2-part pieces in which one piece is 50% of the front of the STL and the second piece is 50% of the rear.) I was able to accomplish this by virtue of the V8 Base Height setting that now accepts negative numbers (Yea). In V8 the Z height removal can be accomplished (for merge type of Add) by setting the Base Height to a negative value (The V7 removal percent of the V8 Scale to Height value.)
I just discovered the File/New Window menu entry. Thanks. Cut and paste of design elements (not toolpaths) works. Given this change I’d suggest that the File/Open command be altered to work in the more standard way. i.e., opening a new file should create another project in a new window, and not quit and replace the currently active project.
See: