Material Library no longer has ability to toggle Output after saved

I’ve discovered that after you “Create new from layer”, the Output function is no longer visible while/if editing the material cut parameters at a later time. More specifically, if the Output is enabled before saving the material and saved that way, then when assigning it to another object, all is well. However, if the material settings are saved with the layer’s Output turned off, then when you assign it to another layer at a later time, it set that layer’s Output to OFF with no means to turn it back on and save the new cut setting for that material. Yes, I can go back to Cut/Layers and turn it on, but that’s not what I’m talking about.

Of course, I can just delete that cut setting in the material library and recreate it from scratch but I’d rather have the ability to toggle its Output state and save as desired.

Am I missing the Output toggle in another location to enable/disable and save?

I can go to the “Edit Cut” and then see toggle for “Output sub-layer” if I add a sub-layer but no way to do so on the first tab; even the “Output sub-layer” grayed out in the Edit Cut Settings dialog.

interesting issue. If this is a bug we need some expert eyes on it

Lets call the big guns
@Rick @JohnJohn

What version are you using? Help → About Lightburn then you can copy and paste the version and build date…

LightBurn 1.6.00, built Sat 2024-02-03 @ 15:11

Is from mine…

I tried to follow you, but it seems to operate correctly on my beta version…

Would you mind posting screen shots of the problem?

:smile_cat:

I’ve logged this issue with our developers. The intended behavior is for all library entries to force enable output, which is why the switch is not available there. It looks like the force enable part is not working properly. Thanks for reporting this!

3 Likes

@jkwilborn
LightBurn 1.5.02, built Thu 2024-02-22 @ 04:21

Not sure how you’re seeing v1.6.00.
Either it’s a typo or you’ve got some super-whipper-dine version. :laughing:

Beta build :slight_smile:

Thanks for reporting! This has been fixed for the next release.
Either 1.5.03 if we do one and 1.6 if not (which will be soon anyways).

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