thought maybe the blank field #1 might be causing the issue, so separated to 2x different input csv files, still no luck. I get maybe 3-4 and then it just hangs.
These files used to work fine in version 1 of LB. Now I can’t complete the job.
Is there a crash dump file or something I can upload that will highlight what’s causing LB to hang on these simple jobs?
Can you send us a screenshot of the entire LightBurn window when it “just hangs”?
There won’t be a crash log if the program didn’t crash (close), but you can try capturing a Debug Log
Turn on the debugging log by clicking on “Help > Enable Debug Log”. This logs all actions taken, so it’s important to try and capture as brief a log as possible to make finding the issue easier.
The log file will be written to your “My Documents” folder on Windows, and is cumulative - each time you enable the debug log it will append to any existing log, so it’s a good idea to delete it after you’re finished.
After enabling the debug log, perform the action that caused the hang, then disable the logging from ‘Help > Enable Debug Log’ once again. Then, retrieve that file from the above location and attach here.
We are having a similar problem LightBurn 2.1.02, Hangs when we send a job to our JCZ Fiber Laser, works ok with Ruida 664XS CO2 Laser. We have reverted to 2.0.05 while a fix is found
I am having a similar problem where Lightburn v2.1.02 crashes when using variable text. If there are only 3-4 variable text elements, the Frame and Start work fine and the file is burned. However, if there are more than 4 variable text elements, 11 in this case, when I press Start to burn the file the screen does the Windows opaque look, and I get the “Not Responding” at the top of the screen. Everything hangs up and eventually I get the “Program not responding” window and Lightburn closes.
Yes, same here. My fiber has a JCZ control board, and I’m pretty sure the UV does as well.
I cannot use any variable text with this version. I have also downgraded to 2.0.05 and that seems to work fine with variable text.
Any update from developers re this issue? Have we provided enough information for you to replicate the issues I demonstrated in the videos I attached above?
I’d love to upgrade to the latest version but variable text is a must-have for my jobs so it would be good to get an update as to whether or not the devs can replicate this issue and what plans there are to rectify it.
@ihockings Thank you for taking the time to upload your video. I’m only now getting around to properly looking at it.
So far, I have been unable to reproduce any hangs or crashes while using Variable Text in version 2.1.02.
“Crashing” to us means, LightBurn closed, and you need to reopen it. Is this what happened?
If so, you should get a LightBurn_Crash_Log.txt saved to your desktop. If that’s the case, please send us this file, along with a detailed explanation of the steps you took. Attach the project file (.LBRN2) and .CSV files used in the process.
Since you all say that you’re experiencing the same issue, can you send us a screenshot of what you see when it freezes?
The default “End” value in the Variable Text window is 999.
If you load a .CSV file with say, 5 lines, this End value adjusts down to the maximum available value, which is 4, because it starts counting at 0. (Computers…)
If you then load a .CVS file with more than 5 lines, LightBurn will not increase the End value on its own.
It’s debatable whether we want the End value to automatically jump to the highest value of available lines.
