In order to improve the quality and stability of public releases, we offer a “Public Beta” period for new releases.
We’ll test to the point we normally would before a release, then make the new version available here for anyone who wants to try it. We’ll gather feedback from those users to address any issues we missed before doing a general release.
Reporting Bugs
If you encounter a bug in a public beta, please let us know by sending an email to betasupport@lightburnsoftware.com. Please provide us with as much information as you can recall - ideally, provide the steps required to produce the issue, and attach any screenshots, crash logs, or images as needed. Please put ‘Public Beta’ in the subject line of your email., so we can set out to reproduce it and fix it.
The standard licensing rules apply - you’ll need to have a current license key to run these (or be in an active trial period). If you encounter any issues while using a beta, you can just install whatever version you were using before, or grab the current released version from the Trial/Download page.
Request from Oz: “…please download and hammer on this.”
Hi folks! Been a bit since I’ve been very active here, as we’ve all been working like mad on the upcoming 1.5 release and the CNC version. We have a 1.4.02 patch release ready to go, and it’s got some very welcome fixes in it.
-[Oz] Art Library search function
-[Oz] Added thumbnails for Thunder 1Gb controller
-[Oz] Bugfix: groups with LOTS of objects took too long to load
-[AH] Bugfix: Snapmaker rotary output now correctly maps to B axis
-[JL] Bugfix: Lead in/out now allowed when tabs enabled
-[JL] Bugfix: Adjust Image tool now keeps images in sync, even with odd orientations
-[JL] Bugfix: Fire Button setting didn’t work when the Move window was hidden
-[JL] Bugfix: DXF MTEXT vertical alignment was sometimes incorrect
-[JL] Bugfix: fiber out-of-bounds images masked by ‘unframed’ tool layers were being output
-[Oz] Bugfix: Deleting a node that connected to itself could crash node edit
-[Oz] Bugfix: Dragging a node that connected to itself could crash node edit
-[Oz] Increased precision of Boolean operations (was 1/125th of a mm, now 1/4096th of a mm)
-[Oz] Bugfix: Ctrl+Shift didn’t de-select shapes
-[Oz] Bugfix: Ruida Z-step per pass could fail to set scanning speed if not filling whole layer at once
-[Oz] Bugfix: Convert Move Window target location for ‘Go’ button to new units when switching
-[Oz] Bugfix: Rotary setup screen would reset “run whole shapes” settings back to default
-[Oz] Allow galvo frequency setting as low as 10hz
-[Oz] Added ‘Test’ button for Repeat Marking axis setup
-[Oz] Faster screen refresh when drawing lots of very small shapes
-[Oz] Shape Optimizer will now remove Beziers that are basically linear
-[Oz] Bugfix: weird error in PDF decompression code caused some files to not import properly or even crash
-[JN] Bugfix: IP address selection would not show in new device setup
-[Oz] Bugfix: Door Protect on galvo could not be un-paused when triggered
-[Oz] Bugfix: UV pulse now allowed as low as 0.05ns (controller limit)
-[Oz] Bugfix: ‘Increment by’ for variable text in radial array wasn’t being picked up when changed
-[Oz] Bugfix: Nasty crash in break / break apart / convert to path interaction, often triggered when node editing
The biggest one for me is the last one - We’ve had reports of node editing being unstable when working for a long time and have never been able to track it down. Last night someone sent us a crash report with a very short set of steps to trigger it, and from that I was finally able to track it down and fix it. This was an interaction between ‘Break’ in node editing and then using ‘Convert to Path’ on something else. It’s quite likely that this was causing some other instability as well, so I’m extremely happy it’s now fixed.
We’re going to try to target next Monday as the release date for 1.4.02, so please download and hammer on this. I think at this point it’ll be more stable than our current public release.
Thank you all for helping us get to this milestone. 