Starting in 2.0, LightBurn supports only Windows 10 (and higher) or macOS 11 (and higher) operating systems. Linux operating systems are no longer supported.
2.0 will be the final release that supports macOS 11 — subsequent releases will require macOS 12 (and higher).
You will always be able to use the most recent version of LightBurn that is compatible with your operating system and was released within your license’s valid update period. To download an earlier version of LightBurn that is compatible with an outdated operating system, visit our release repository.
This build includes the following updates
Change Log for LightBurn-v2.0.00-RC-8
Changes Since LightBurn-v2.0.00-RC-7
Bug Fixes
Don’t allow any barcode create / drag / select if a dialog is up (#963)
Suppress kerf warning on filled shapes (#970)
Three Bugs
gcode settings were not being shown for LinuxCNC and Custom GCode
Show save gcode button even in beginner mode for LinuxCNC
Head-mounted Cameras would crash after Trace (#984)
don’t use infinite timeout for Ruida serial send
Ruida auto-home flags were wrong
fixed a bug in the Ruida setting for limits enable
Existing Feature Updates
Added info to invalid proxy warning
warning fix
Update “position laser” tool to change cursor to indicate snapping
Allow un-modified media buttons as hotkeys
DEV-1531 Default LB to GoTo in OT_WORKPIECE. (#987)
Initial support for RD8445
Miscellaneous
Cleaned up some runtime debug warnings (#971)
Language Updates
Updated translations
User Interface Updates
Changed dark red text on “Additional” tab of Device Settings window to an appropriate theme color to improve readability on dark themes.
Improved margins, spacing and text styling for Custom GCode Options in Device Settings.
Fixed bug causing partial theme change if Windows theme is changed while app is running.
Read the full change log with all updates since 1.7.08 here:
To access the complete Changelog, click the link below:
I realize this is somewhat a dead-horse topic, but … have you considered at all a “Light” version of LightBurn that would continue to support Linux – but WITHOUT any of the more burdensome feature support (cameras, serial, device control, etc.) that has raised compatibility issues?
I know for me, I use an old windows laptop to do the “at the laser” work, but it’s still really nice to be able to use the UI for editing from my desktop linux machine.
Understand completely about the difficulties you’ve had with the support overall given narrower audience, just wondering if “stripping out the pieces that are higher burden” would allow for doing a “limited” functionality build without significant operational cost.
We’re not saying no to Linux in the future, at some point, but for now, LightBurn 1.7.08 is your best bet for the forseeable future.
Removing features from 2.0 would likely still make for a piece of software that is subpar to the current version AND still a developer and support load. So for now, 1.7.x will be the final release for Linux devices.
On previous versions, the oject size was changing live while you are scrolling over numeric edits. Now its not. You only see the size change after hitting enter or clicking anywhere
What do you experience when selecting? Do you get anything returned, or does the menu just go away and nothing appears to happen? What steps do you take?
I’m using LightBurn v2.0.00-RC8 and running into a problem with camera calibration using AprilTags.
Due to the distance between my PC and the laser, I’m using VirtualHere on a Raspberry Pi 4 to connect the camera over USB remotely. The connection itself works flawlessly — the camera is detected and works fine in LightBurn.
However, after switching to a UC60 camera, I noticed that AprilTags are no longer detected, even though they worked perfectly with my previous cameras. I’ve tried moving the tags closer, farther, changing lighting conditions — no improvement. The software just doesn’t recognize them.
Even the alternative camera calibration method fails to detect the tags on this camera.
UC60 Camera Specs:
Sensor model: IMX179 (CMOS)
Sensor size: 1/3.2"
Pixel size: 1.4 µm x 1.4 µm
Interface: USB 2.0
Cable: 1 meter USB
Typical resolutions / frame rates (MJPG):
3264×2448 @ 15 FPS
2592×1944 @ 15 FPS
1920×1080 @ 30 FPS
1600×1200 @ 30 FPS
1280×720 @ 30 FPS
960×540 @ 30 FPS
800×600 @ 30 FPS
640×480 @ 30 FPS
Operating voltage/current: 5V, 110–190 mA
Has anyone encountered this issue before? Could it be related to how the UC60 handles image processing or streaming over VirtualHere? Any advice or suggestions would be greatly appreciated!
Thank you, @reki1 for drawing our attention. I have moved this post to the RC8 thread to help with managing the feedback we are getting for the release candidate.
If you create a custom device with a network connection, choose the device and then Laser Tools → Device Settings you will always get a “invalid IP / hostname” error upon exiting. But there is no field to change that.
Going through the Devices → Edit let’s you enter an IP without error.
That also stops you from using the focus test since you need to activate the z-axis.
I have just installed and tested RC8. We seem to have the issue back again that was in RC5. The arrow keys do not move the laser head anywhere. But the home and origin button seem to work just fine. Also the get position button displays on the screen correctly. I am not sure what changed from RC 7 to 8 but this function is huge for me to get the proper laser head location on the bed to start jobs on the material.
