ok, thank you
I can reproduce the freeze, but only if I have multiple instances open and hit Frame before plugging in the laser.
Or Frame in one window, change to the other and unplug the laser.
Please try if it still happens if you only run one instance of LightBurn.
If you still see the spinning beach ball, please explain the exact steps you are taking.
Does the window unfreeze if you restart the laser?
1 Like
Exporting gcode to LinuxCNC has lcnc complaining about missing â%â at the end.
There is also no M2 or M30.
I am unable to get the New 2.0.0 RC7 to run.
Installed and started, the splash screen appeared then disappeared then nothing.
Task Manager does not show it in memory at all.
Uninstalled, deleted the directory then reinstalled and same issue.
My 1.7.08 is still installed and runs fine.
More Info from Windows Event Logs after trying today:
Summary
Faulting application name: LightBurn.exe, version: 0.0.0.0, time stamp: 0x683e0d69
Faulting module name: LightBurn.exe, version: 0.0.0.0, time stamp: 0x683e0d69
Exception code: 0xc0000005
Fault offset: 0x0000000000174be3
Faulting process id: 0x22AC
Faulting application start time: 0x1DBD975CBB60336
And more info from yesterdays crash:
Log Name: Application
Source: Windows Error Reporting
Date: 6/8/2025 4:25:01 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: HP800-G4
Description:
Fault bucket 2190723773039335497, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: LightBurn.exe
P2: 0.0.0.0
P3: 683e0d69
P4: LightBurn.exe
P5: 0.0.0.0
P6: 683e0d69
P7: c0000005
P8: 0000000000174be3
P9:
P10:
Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f547b97c-af17-43fe-94a8-0b918013071b.tmp.WERInternalMetadata.xml
These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LightBurn.exe_d6eafecceda29b465e1478e433463a88c783ce5_14068908_144dc3ac-deec-4950-967e-717fe88281b8
Analysis symbol:
Rechecking for solution: 0
Report Id: 5f3e3593-95c7-4604-8c72-f4edafd4e060
Report Status: 268435456
Hashed bucket: 75922056e8ea9758ee6703aa25035849
Cab Guid: 0
Event Xml:
1001
0
4
0
0
0x8000000000000000
41961
Application
HP800-G4
2190723773039335497
4
APPCRASH
Not available
0
LightBurn.exe
0.0.0.0
683e0d69
LightBurn.exe
0.0.0.0
683e0d69
c0000005
0000000000174be3
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f547b97c-af17-43fe-94a8-0b918013071b.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LightBurn.exe_d6eafecceda29b465e1478e433463a88c783ce5_14068908_144dc3ac-deec-4950-967e-717fe88281b8
0
5f3e3593-95c7-4604-8c72-f4edafd4e060
268435456
75922056e8ea9758ee6703aa25035849
0
Started using 2.0 and really like many of the new features. I did find a small bug with the laser position tool. Cannot turn on âShow Last Positionâ. Another bug may be the speed at which it positions. So far many of my settings i use from V1.7 transferred to 2.0 but position speed is very fast.
Centering 2 shapes (align vertically and horizontally) doesnât do what I expect. I draw two stars, one a single and one a double star, to make some sort of Christmas decoration. Here Iâve aligned them manually, then selcted both and clicked on the align V and H button (top line of icons). The centers do not coincide. Same happens with circle and star.
.
.
Thatâs because LightBurn defines the center of an object to be at the midpoint of its bounding box, which may not be at the geometric center of symmetry.
Both the circle and the star have their geometric centers at the middle of the workspace, so the points of the star are equidistant from the circle:
However, the starâs selection handles and bounding-box center point are offset upward, because the top point of the star âsticks upâ farther from its geometric center than the bottom points.
I usually draw a big circle on a tool layer from the geometric center of an odd-vertex polygon, group the circle and the polygon together, and then snap the circle + polygon to wherever it should go. Because the circle defines the (grouped) bounding box, its center snaps to the right place and the group carries the polygon along for the ride.
4 Likes
Legendary response as usual Ed, thank you!
2 Likes
I realised this - which was why I was careful to say âNot what I expectâ. and it probably isnât what most people would expect to happen either.
1 Like
True, most people would expect what you did, but we are both schooled now. Looks like a detail to add to the documentation.
Currently, when you want to resize an element and try to do it by dragging from the center (not from the corner) you always get an element that will be distorted. In PhotoShop this is solved differently - the user has the ability to lock the aspect ratio so that the scaled element is always consistent with the original proportions. I really miss this solution when arranging elements on canvas.
Video:
corner grab will expand/shrink proportionally. no need for a lock
Resizing by dragging a corner aligns the element to the opposite corner by default, or to the center when holding the Ctrl key. However, if we want to align it to the opposite edge (not the corner) and maintain proportions at the same time, there is currently no way to do that (at least none that I know of). Yes, itâs possible to achieve this via the âDockingâ menu or by manually entering the dimensionsâthis allows alignment to one of nine possible anchor pointsâbut these methods are not always time-efficient for us. Adding a keyboard shortcut, even just one that enables proportional scaling from the center while dragging, would significantly improve our workflow efficiency.
Check if there is already a request for this in Feature Suggestions, If not you can add it.
I know itâs on the roadmap but any chance you could add a MacOS/AArch64 âApple Silicon M1/M2/M3/M4â build to the RC channel.
Itâs been years since the last intel Macs were sold and full support for the Rosetta2 translation layer will start to sunset with MacOS 26 due out this fall.
We canât add it to the RC channel as we havenât gotten it working yet.
And Rosetta 2 will be sunset with OS 27, but still work on 26. Weâve got a year.
Once 2.0 and MillMage are out, ARM builds move to the top of the priority list.
1 Like
Iâve had an issue happen a couple of times now with RC7 on my computer that I use for my Fiber and UV Lasers. My default device profile is set to my 200mm lens on my Fiber laser. If I open a project that was last used on my UV Laser, I will get the prompt telling me what device profile that project was created with, and ask if I want to switch to that device profile. I select Yes, and LightBurn will Crash. Reopen LightBurn and do the same thing, and it works. Has just happened a couple of random times with different project files, so havenât been able to recreate on demand.
When you say it crashes, do you get a crash log? (you should) If you have that and can include it here or in an email, itâll be easier for us to track down whatâs happening.
There is no crash log on the machine. Just upgraded to RC8 last night, and have been unable to get it to crash under those circumstances now. If it happens again, will look for a crash log again, but havenât been able to get one yet.
3 Likes