Prior to v1.7 I was able to save LightBurn.exe as LightBurn2.exe, create a separate shortcut for it, and have one labeled for my CO2 laser and the other for my Fiber laser - and I could set the default device in each instance. Since upgrading to 1.7 and now 1.7.01, I can’t do this. I set a default device in one instance and it affects both. I know I can change devices, but it was SOO nice having the previous ability as I tend to work in 2 sessions all the time.
LightBurn has never worked this way. It’s possible you were using a pre-release version, which would save its preferences in a different.
@adammhaile - can you tell him how to set up a shortcut with a different prefs location? I can’t recall.
You can call LightBurn with --prefsdir <prefs_location>
If you create a new Windows shortcut you can just add that in the properties and point it wherever you want. It will create the directory if it doesn’t exist already.
@LightBurn in previous versions there were code paths that did base the prefs directory location purely off of the .exe name. This was never intended to be used and it was fixed (since it really was just a bug) when I created the option for tagged builds and pre-release prefs.
Never used a pre-release version and always stayed current. Never had to call Lightburn.exe with the --prefdir before, but if that works I’m a happy camper again!!
Hrmmm, now I am only able to open 1 session of LB at a time. When I try to launch a 2nd it tells me that is cannot find the prefs location I put in the shortcut properties.
Not sure if my reply to your email was received or not, I included a screenshot of the error. In any event, I run simultaneous jobs on my two different lasers, but with the --prefsdir solution I can only run a single LB session…
Interesting… I’ll see if I can reproduce it. Could be a newly introduced bug.
Ah, ok, I see the issue.
Again, this is unfortunately all in parts of the code that were really only ever meant for testing. I need to formalize all of this at some point.
In your shortcuts add --forcenew
So: LightBurn.exe --forcenew --prefsdir <prefs_location>
Otherwise it tries to find existing open instances and use that instead.
That worked! Thanks Adam. I’ve passed this information on to a few folks in my “circle” here in Colorado who’ve been dealing with the same challenge since 1.7.0. We all thank you!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.