I want to address the silence some of you mentioned a couple weeks ago. Yea, sorry about that…
Lightburn 2.0 and then the entire company traveling for our LightBurn experience conference put a lot of conversations on hold for a minute. Or basically all of July… We did have some banners on our home forum addressing that, but I understand wanting to having communication and frustration with the lack of it.
@Jonathjon and @jeyeager Your post didn’t get ignored as much as you nerd sniped a couple devs to dig into custom g-code more. There’s a bunch of changes coming in the next RC for it, but we are all just getting a chance to land back in our workshops to make sure they actually work before putting them out.
One of the big things we are doing is making the “Start G-code” header that was effectively hardcoded user editable now. I don’t think that will disable that first tool probe yet, but I will be playing with it in the next couple of days.
I wanted to point out how valuable this mega-thread has been for the team and how much I appreciate all the feedback. You have both validated and disproven some key assumptions we had going in and it’s been a major help for me and the rest of us.
I hope you’ll find this tight nit community of V1 machine builders is a really good resource to help development cycles. We’re not just machine users (and we are that!), we’re also a crazy mix of disciplines who help design and build the very machines we operate.
A better focus / beta group I’m not sure there is- and I’ve seen a bunch in my career.
The big ugly problem is computing the “medial axis” of the input shapes. Once you have that, you can use it to produce V-carving paths, fast internal offsets, as well as a center-line path for the geometry.
We have an in-house medial-axis solution in progress, and it’s about 90% complete, possibly more, but the number of weird edge cases and geometries that fail is very large and we’re working through those now. It’s complicated, ugly math, and making it fast and robust is very hard.
Once it’s ready, we’ll start implementing V-carving paths, including V-carved inlays, faster offset pockets, centerline tracing, and larger than 50% stepover needs it too.
Short answer: it’s coming, not sure when it’ll be ready and usable.
That sounds great. As I said: I can do it in Estlcam but it’s hard, V-Carve Pro is 700€… If you want someone to test the carve funtcion with deep inlays, just tell me.
I sure believe that, but you got to believe me that I am pretty good at inlays and know what people need who do deep inlays in cutting boards… You should check out my makes here in the forum, for instance the Coffin Board so you know I’m not talking shit.
This would be a killer feature - even for lightburn. Trace image is good but if you’re working with line drawings, especially ones with small details making a fine line not a loop would be very cool.
We’re excited for it to be ready for public too! Centerline trace (and the other features that benefit from the math behind the scenes) will be a huge win once it’s available.
what is the status of millmage? Does it have vcarve? I have not heard anything about Millmage at all lately.
I had HUGE hopes for it as lightburn was soooo ahead of everything else for lasers. (There was something else it was missing for woodworking but I cannot remember what it was.)
They’ve been making a lot of progress. It’s not going to have everything at release and that’s fine. It’s a tremendous amount of work to get a product of this size to a release version. It’s just going to take time.
It looks like they added trochoidal in RC8 but I haven’t tried it.
Man I just updated to RC8 last time I was home (2 weeks ago) and they are already on 11 now!?!? I have loved it so far. But 99.9% of what I do is flat sheet work and it’s just so much easier to lay out different parts than it is in Estlcam
I’ve spent some time down that rabbit hole.
You should check out my makes here in the forum, for instance the 
