I’m having an issue with variable text where when i press the “Test” button, the text from my CSV shows, however when i preview or send to the laser, the missing text does not output. The variable text is within an Array and I have created this issue in two different files, one with a standard array and one with a virtual array. In the image attached, you can see the text is being pulled in from the CSV using the test button, but the preview, the text gets cut off.
Thanks for reporting this, I can see what you mean. I can replicate the issue by creating my own boxes and arrays. After a certain amount, LightBurn appears to be recognizing the array numbers as open shapes, this is the warning message I receive:
Thank you for the response and this does get me partially working again. However, in my other use case, I have a standard array where every text needs to be different such as a serial number.
I created another example and played around with the cells in the CSV., see attached.
It appears that LightBurn is reading the cells in the CSV incorrectly. I’ve listed my findings below as well as a screen shot. For %0-%2, It seems to shift the next column down by the count of rows of the previous column until it reaches %3 and then they all stay on the same Row count.
If you click on any of the text items in the left-most column and look at their “Offset” value, the upper-left entry (%0) has an offset of zero. The next line down is an offset of 9, then 18, then 27 for the rest of them.
This means that most entries are pulling from line 27 in the CSV file or greater, and you have the “Auto-increment” toggle enabled, so as the variable text items are processed from left to right, that offset is incremented, meaning the 2nd item pulls from line 28 of the CSV file, then the next from line 29, and so on.
Since you only have 30 lines in the CSV, most of those entries end up blank, and that’s why the text disappears. If you turn off the ‘Auto increment’ I suspect it’ll be what you’re expecting.
I did find a bug in the code that we use for editing the virtual arrays after the fact, so that has been fixed.
The “open shapes” warning was being triggered because of the text evaluating to nothing - it was creating shapes that had no content, so I’ve removed those which will prevent that warning from popping up too.
