LightBurn v2.0.02 Release Candidate

Announcements Release Candidates
, , ,
1

The first release candidate for LightBurn v2.0.02 is now available to download here:

LightBurn-v2.0.02-RC-1 - Change Log

Changes Since LightBurn-v2.0.01-RC-1

Bug Fixes

  • Fixed Windows DPI scaling bug that could increase the size of UI elements to a degree that made application unusable.
  • Fixes a few laser-specific jog issues.
  • Rotary enable icon was not showing correctly in some cases (#1085)
  • 3DSlice resampler crash caused by temp variable going out of scope (#1088)
  • 3DSlice resampler crash caused by temp variable going out of scope early
  • Fix file ‘Start’ corruption after using Send (#1086)

Existing Feature Updates

  • Certain zoom levels were slow because of transparent grid (#1090)
  • Add ‘Flash Layer Shapes’ action so it can have a hotkey (#1087)
  • Minor Tweaks to Cut Settings height (#1101)
2 Likes
2

A problem with importing an Inkscape SVG with text that’s common to all the V 2.0 versions. I haven’t tried it with the 1.7 series.

The (simplest failing) Inkscape layout:

LightBurn 2.0.01 - Inskcape layout
LightBurn 2.0.01 - Inskcape layout617×677 40.5 KB

The result looks identical to that image in all the usual browsers, image editors, and image viewers. The problem occurs when it’s saved as either a standard SVG or an Inkscape SVG, so I think the hole isn’t in the Inkscape end of the boat.

Importing either of those files into LightBurn, however, causes the text field to float off toward the upper left:

LightBurn 2.0.01 - SVG text offset
LightBurn 2.0.01 - SVG text offset810×883 144 KB

The file in standard SVG:

LightBurn 2.0.01 - Inkscape text layout

And Inkscape SVG:

LightBurn 2.0.01 - Inkscape text layout - Inkscape SVG

The LightBurn file after the import:

LightBurn 2.0.01 - SVG text offset.lbrn2 (14.4 KB)

This problem popped up in a set of programmatically generated SVGs, each sporting a label identifying which one of 16 Inkscape layers it was. The text field must be within the bounding box set by the rest of the image to let me snap it into position in a template, but it refuses to stay inside the box. The SVGs get stacked in LightBurn, but must go in a specific order that’s impossible (for me, anyhow) to get right without their labels.

1 Like
3

I can verify I see the same on Windows 11. Will try on Mac later this afternoon.

1 Like
4

Thank you, @ednisley and @CarlFisher. I have added this to another, existing report currently being investigated. :slight_smile:

5

Works correctly in 1.7.06

6

Just because I said I would, I verified this is also the case on Mac. Works in 1.7.08, not in 2.x

1 Like
7

image
image1685×399 94.5 KB

2.0 vs 2.0.0.2 RC (in front).
The iconsize is set to smallest(max left) on 2.0 and to -5 (max left) on 2.002 RC.
an error/bug? or is no longer possible to go with small icons like in 2.0 and previosu releases?

8

With this version I’m noticing the power output is being sent at a much higher value than specified in the settings.

For example, 300 mm/s and 50% power is what I use for scoring on acrylic. In 2.0.1 this works as expected. In 2.0.2 RC it’s burning nearly all the way through the acrylic. This is using the exact same .lbrn2 file.

I haven’t done a lot of testing with this (for obvious reasons hopefully!) but if there’s anything I can do to help debug or if it’s a misconfiguration on my end please let me know.

Thunder Bolt 30 Watt, MacOS 15.5. 1/8" Clear Acrylic.

9

Hi Rick, I’m still experiencing issues with print and cut. I’m still getting the same message about insufficient space between targets. Additionally, the jog function overshoots the second target and only stops when it reaches the bottom of the axis. Test file uploaded, can you help? So its back to 1.7 again!
Print and Cut Test.lbrn2 (9.7 KB)

10

Hey @Steve765, thanks for the reach-out. We will look into this deeper. As a friendly ‘heads-up’, this may take a bit more time as most of the team is out, off to LBX 2025 for the weekend. Thank you for your patience. :slight_smile:

1 Like