LightBurn 0.9.19 problems

LightBurn Software Questions
1

Environment:
LightBurn 0.9.19, built Sat 2020-11-21 @ 14:19
Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic
Fresh install of both OS, and Lightburn
Emblaser Core laser cutter

1: “Fire Button (‘Move’ tab)”
When the Fire Button is pressed, I only get ONE MOVE before the laser locks up. I have found that right-clicking on Devices allows me another one move before it locks up again. The one move can be in any direction, and with or without the ctl or shift modifiers.

Previous version allowed me to Fire the laser, then move it around while showing. Now I have to Fire, un-Fire, estimate move, Fire, check laser position, un-Fire, guess move again - repeat.

2: Push to Front and Push to Back do not seem to do anything.

Previous version clearly showed different overlappings as the ordering was changed.

3: Create Grid Array- X Column and Y Rows only allow typed entry of 2 digits (i.e. maximum of 99), whereas using the up arrow control allows far greater values.
To enter, say, 200, requires typing 99, then over 100 clicks of the little up arrow.

4: Infrequently, deleting the initial node of a curve makes Lightburn crash

5: Infrequently, resizing rectangles seems to cause the (0,0) origin to be included in the shape somehow, as the bounding rectangle becomes much larger than the shape, and extends to the origin.

2

  1. I suspect this is related to a change made to help Ortur lasers, but seems to have broken others. I’m likely going to change it back.

  2. You’re in ‘Filled Rendering’ mode and the drawing order is dictated by the layers.

  3. I am not able to reproduce this here on Ubuntu 16.04. It’s possible it’s related to Mint.

  4. If you see this, and are able to reproduce it with any regularity on a file, I would love to see that file so I can try to figure out what’s causing it.

  5. Are you saying the rectangle you are drawing is getting resized to include 0,0? Can you give a little more detail on this, as I’m not sure I understand.

3

  1. OK, thanks

  2. Changing the ordering of the layers gives the behaviour I expected from reading the documentation - that is, being able to see a hidden shape by moving it ‘in front of’ the shape which was hiding it - thanks.
    I re-read the online documentation, and I can’t understand what the Push forward/backward functionality is supposed to do.

  3. Ok, will watch for reoccurence, and try to capture a file for reproducing the issue(s)

  4. When I select a rectangular shape, the 9 control points are normally all closely spaced around the outside of the shape, and one in the middle.

What I’ve had happen is that the control points spread out to include 0,0 so that the shape behaves like a grouping of (the shape + and invisible point at the origin).

If I try to, say, centre this weird shape with another shape, they end up wildly misaligned because the extents of the shape somehow include 0,0

It happened in the previous version, too. Not frequently enough to be a major issue, and it seems to happen ‘early’ in the development of the rectangular shape, so I now just delete it and try again, rather than trying to ungroup, or look for hidden nodes, or something.

4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.