LightBurn v2.0.01 Release Candidate

Announcements Release Candidates
, , ,
1

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

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

Changes Since LightBurn-v2.0.00-RC-9

Bug Fixes

  • Prevent extreme fisheye projection infinities in head-mounted camera wizard (#1049)
  • Prevent extreme fisheye projection infinities from crashing the diagram in the head mounted camera wizard
  • Handle cancel of Offset Fill (#1057)
  • Invalid custom gcode blocks were getting hidden (#1054)
  • When framing first, job was continuing if canceled after out of bounds warning
  • Large images might not load with Qt6 build
  • Increase epsilon distance on Trim checks
  • Better handle device units for people upgrading from older versions
  • Enable relative arrow-jogs with ruida (#1076)
  • If an image fails to import, show an error message about file size (if greater than 100MB) or possible corruption. (#1069)
  • If a very large image fails to import, show an error message about file size or corruption.
  • Adding origin type to Go to Origin (#1075)
  • Node editing was not undoing properly because the selected node got removed from the undo. (#1073)
  • Fixing the fire power setting when the Fire button is already enabled. (#1077)
  • 3D slice masked / transparent pixels shouldn’t be negated (#1079)
  • Proper handling of click-drag of multiple nodes (#1080)

User Interface Updates

  • Fixed vertical spacing and minimum height for tabs for the galvo cutsettings dialog

Note: Work continues to address and resolve the ‘Windows Scaling’ issues reported.

7 Likes
Warning - Upgrade from 1.7 to 2.0 Has critical defects for some - I reverted to 1.7
Cut tool issue not cutting
Move tab, arrows not working
Lightburn 2.0.00 Software Crashes on opening
Offset Fill Generating Bizarre Paths
Verson 2.0 and setting User Origin
2

You must have worked hard for this 2.0.01… :+1:

NB. The missing display of the red target cross at “Set Laserposition” has not been included in this RC, is it an oversight or a priority issue?

1 Like
3

I think we may not have observed the bug directly. Can you share a screenshot of this happening?
What I have noticed is in case the gcode or origin is incorrectly set, the crosshairs are showing wayyy off grid.

4

SkĂŚrmbillede 2025-07-10 kl. 12.59.07
Skærmbillede 2025-07-10 kl. 12.59.072076×812 123 KB

5

Just a quick test and couldn’t get the Boolean Assistant to work?

6

Works fine here on MacOS

7

Please explain the exact steps taken, what you expected to happen, and what did or did not happen. Difficult to work from what you provided; need a bit more detail. :slight_smile:

8

2.0 Noticed that when I use saved MOVE positions the cursor does not update.
Windows 11 Machine. Reverted back to 1.7.08 and functioning again.

1 Like
Warning - Upgrade from 1.7 to 2.0 Has critical defects for some - I reverted to 1.7
10

This may have already been addressed but I missed it. In the new 2.0 version, even the most recent addressed in this topic, the “saved positition” red dot indicator (shown in the attached screen shot circled in red) doesn’t remain. It does pop on the screen but only for about 0.5 seconds but then disappears. I have reverted back to 1.7.08 so I could continue to work with Lightburn till a fix is provided or I find a work around. I am using Windows 11, with a Omtech MF2028 machine. I just re-read posts and it seems this is a known issue so this may be a redundant question.

Lightburn 1_7_08 Vs Lightburn 2
Lightburn 1_7_08 Vs Lightburn 2604×552 78.3 KB

1 Like
Saved Positions still not showing
11

Yes, known, but thank you for offering your report of this behavior. :slight_smile: @goeland86 for visibility.

12

virgin install of v2.0.01 RC1 and so far so good, absent testing the laser position indicator (not hooked up to machine in the shop yet). Drawing a few simple shapes seems fine, nice new features I see. Inherited prefs from v1.7.08 just fine. All sw text and icon scaling seem normal.

2 Likes
13

Thanks for this positive report, @bLouChip. Much appreciated. :slight_smile:

14

Well, after updating to version 2.0.0.0, I noticed that on my OMTech with Ruida controller, the arrow keys to move the laser head didn’t work unless I enabled Continuous Jog. I saw that some other people also reported this issue.
Then RC 2.0.0.1 was released — I updated it, and now the arrow keys work, but the Red Dot on the screen doesn’t respond when toggling Show Last Position.
The Red Dot only works now when I click Get Position.

15

Correct.

16

I created several multiple star images and put them on top of each other then tried to activate the Boolean assistant after highlighting all. The assistant would not activate.

17

Does “several” mean more than two shapes/objects? :slight_smile:

From the documentation: Boolean Tools - LightBurn Documentation

There are a few important things to keep in mind when using the Boolean tools

…

  • To use any of the Boolean tools, you must have exactly two shapes, two Groups of shapes, or one shape and one Group selected. If you have more than two shapes or Groups selected, the Boolean tools will be grayed out and unavailable.
18

The 2.0.01 RC1 version should fix Ruida arrow jogging. And last night we fixed the cross hair update on Ruida, it will be in 2.0.01

Thank you all for your patience.

19

…you probably mean 2.0.0.2… (we are on 0.1 :wink: )

20

No no, this is 01 RC1, and it didn’t make it in, but it will be in 01 :grin: (unless @adammhaile overrules me)

1 Like
21

…forgot RC :+1:

1 Like