hi, I am trying out doublesided carving for the first time using your software.
I seem to be missing something, but I cant solve the problem.
While the rough cut does not cut through the tabs, the contour cut appears to do so from what the preview shows me. It is likely something Im missing. What am I doing wrong here?
Thanks in advance for your help.
that would be a bug. investigating…
@bongo_matteo thanks for the workspace. I found the issue and it’s an easy fix. I will push an update in the next hour or two that resolves this. it was related to having tabs above the floor of the workspace.
Thanks for your help!
Is there a way to use the flip operation to also rotate only 90 degrees as well as 180?
I would like to try 4 sided carving using this method
glad you asked. this is something I plan to add as part of 4th axis work (discrete and progressive rotation control). it’s a little tricky to shoehorn into the existing flip operation.
@bongo_matteo this is fixed in production. please let me know if it is or isn’t working for you.
Hi and thanks for your help!
Im experiencing problems still, just different… The contour passes are exhibiting errors. I didnt notice them in KiriMoto, but IGS Platform showed them starkly once I opened the gcode there.
Also, for the 1st time I was unable to apply carve passes in isolation - in other words, if I set up a roughing pass, exported the file, then deleted the roughing pass & created a contour pass for the same side, in order to have seperate gcode files for each (due to my inexperience with gcode). Since the contour pass would not render properly alone, I noticed the contour pass appeared to work provided the roughing pass was still present in the operation chain; so I output both to gcode and seperated them manually in notepad++ to produce 2 gcode files. The contour files has errors around deep pocket areas displayed in yellow in UGS.
Here is the workspace file: https://file.io/juQfBfEJ73Hw
thanks for the workspace. I am able to replicate your problem. hopefully it’s a quick fix.
tip for separate exports. you can ctrl+click an operation to enable/disable it. red is disabled. that way you don’t have to delete them.
I have a workaround while work on a I fix this: enable true shadow under the expert menu. it’s computationally expensive, but does work around the issue.
I have a fix that I will push out later today
Thanks so much!
And for the cntrl click tip!
The more I use Kiri:Moto, the more I love it!
I’m replying to this 4-y.o. thread because this is where today I learned about the ctrl+click trick to disable an operation. Good stuff, and exactly what I needed in order to export my passes in separate G-code files. However: can I ask that this be made more discoverable? I hope I’m remembering correctly, but I believe there was a time when disabling the operation was available as a checkbox within the operation’s config “pop-out”. If mouse-over tool-tips worked on the operation, they could show the way, but mouse-over, of course, is already taken.
should be on the doc server
I guess you’ve made most of the interface so discoverable (once you get the hang of the workflow) that it would be nice if that was too. But I do take your point. 
I will be re-designing parts of the UI post 4.4 and can revisit this at that time.
there used to be a checkbox next to the trashcan in the op button. this felt really busy to me. I have some ideas for improving the op chain. in fact, I want to totally overhaul how operations are constructed and parameterized. this might be a 5.0 level redesign.
that kind of hints that I might skip from 4.5 to 5.0 because under the hood I want to do other major refactors like fully extracting the fdm, cam engines from the UI as standalone libraries. which would be painful and invasive, but worth it. for one, it would make unit testing possible.