I know when i posted this before you folks said. “we dont get it” “that doesnt happen in Our software dude”
when node editing in Lightburn. lightburn randomly throws a node to Zero, Zero coordinate. when user tries to select and delete rouge coordinate the software crashes and destroys the work.
I have seen similar behavior where deleting something causes the odd line out of the work area. Not sure if it went to 0,0, but definitely not right. I have never had it cause a crash though. When it has done this I hit undo and attack the problem a different way.
Did you design this in lightburn, or is it an import job?
Please post the offending file for the dev team to look at.
On a related note, there is no need to be adversarial. The forum exists to solve user problems..In other words… please don’t poke the bear if you want to be answered. It’s just good manners.
Hi Anthony, any chance you can email us this exact LBRN to support@lightburnsoftware.com?
Or Post it as @JimNM said
Yeah, but when it closes out the software and deletes the file its kinda difficult to hit “undo” and do it a different way. For real though, my goal was to give awareness to the issue, a hey, something to look into folks .
Are you using “snap to grid”?
The idiosyncrasies of the file are what the devs need to see. If your file is the only one in the history of LB to cause such an error, how can that be addressed without having the source file?
It looks like you snipped a screen shot off the internet and it needs some cleaning up for engraving. Those watermarks can be tricky to work around.
We are happy to help you learn.
We want to know about issues that happen with the program.
Don’t play games with free and expert help.
James has a point here - if you can send us the LBRN before edit - we can try to force the issue to happen.
Knowing a file that is prone to trigger the issue is a very good tool for replication.
But then I get your nastiness. Whom ever you are…
nowhere in the post did i say “please help” or “how do i fix this”
I clearly was not playing any game with anything it was clearly just a hey look what happened. as the software said “hey notify lightburn folks this happened.”
“the only file in lightburn history to Cause such an error” where another user has stated they had the issue as well but lets not notice that because we are gunning this user…
“watermarks can be tricky to work around” it wasn’t a water mark but,whatever works for you.
“We are happy to help you learn” bub, you have been gunning me from the gate, over the opening of the thread. which was merely a fact. i didnt need help learning, i was following the diction of the software to notify Lightburn of an issue
as clearly seen another user clearly said it happened to them they hit “undo”
but i guess you were so ready to “teach me a lesson” you were not interested in reading that maybe.
As the file no longer exists. there would be nothing to send
It appears to me that there are deeper problems present that are outside of my influence.
Good day, sir. 
You are calling other people nasty, but they only try to help.
Then we can close this thread and don’t have to discuss this further. As long as the bug can’t be reproduced, there is nothing to do except wait for it to happen to some user again and check the issue then to reproduce it.
