I have 5 images being cut in 5 cubes that are aligned in a jig. When 1 face is done, I rotate the cubes, turn off the current layer, and enable the next layer. When I hit send, every single time Lightburn crashes.
Low storage will make Ruida controllers behave strangely. You need to manage files. Or avoid this by using Start instead of Send. Did you confirm that the issue goes away after clearing files?
Potential issue with crashing when storage gets low. I’d suggest sending a crash report to support@lightburnsoftware.com in that case.
If you can demonstrate specific conditions where this occurs in 1.4 vs not happening in previous version even better. It may be that you hadn’t run into this scenario previously.
I am using 2 stacks of images in a jig, and the crash happens every time when I try to communicate with the laser after finishing a job.
It seems that Lightburn is not releasing the laser properly and then is trying to reconnect with it but Windows thinks it never disconnected (correction, rather than the laser).
But also wasn’t able to follow all the steps. Something is odd with the file so Print & Cut wasn’t behaving properly. Didn’t explore it very far.
I ran 2 images, then attempted to run a 3rd. Did not experience a crash. Note that I used Start rather than Send, however.
Other than the oddity with the Print and Cut, I noticed that the faces show up in an Image layer but don’t otherwise behave like an image. For example, Adjust Image doesn’t seem to be an option on these images. How were these images brought into LightBurn?
Other thing I noticed is that the images themselves seem unnecessarily large. Look to be about 4 MB each. Any reason for this?
Can you attempt to run these without Print and Cut and using Start button to see if the crash can be reproduced that way?
I think tomorrow I can find some time to figure out an acceptable place to cut with manual alignment.
The images were drag and dropped into Lightburn on a mac. They are grouped together, that is probably why they are not acting like images (when only one shows it’s easy not to notice).
They are sized to the cut size @ the desired DPI (3.9" x 3.9" @ 283dpi).
Indeed that’s the case. Didn’t realize just how many photos there were. I’m curious if some of the hidden layers were responsible for the oddity in Print and Cut.
I can see that now after ungrouping. Surprised this results in such a large output It was sending about 4MB of data. If my math checks out this should be around 660KB.
The idea is that each stack has 6 layers, one per cube face. Only one cube face can be cut at a time, then the cube has to be rotated. Using 6 layers and turning each off/on in succession has been the best solution I have found so far to managing all the cube faces.
