Lightburn is giving me this output in the the print preview and it’s actually skipping the areas under all of the letters. I’m quite sure this is a software issue as the laser is outputting what it was told to do.
What I can’t figure out is why it’s doing this as I’ve done fill layers in the past with no issues. Not sure if any recent software updates did something or it’s a setting I have to update?
I’m quite stuck for time as well and need to get this project completed.
If anyone can assist, I’ll try anything at this point. I still will be up quite late to figure this out as the forums don’t have exactly what I’m looking for.
I should clarify that crosshatching was only turned on as part of my troubleshooting. It is actually off at the moment.
I’ve disabled everything except for the red layer which is the graphic itself. I have also disabled that to check the other layers to see if they render correctly. They all render as expected.
I’ve spent just under 2 hours. Trying to troubleshoot this. Many different permutations and combinations.
It’s not clear to me that there’s actually a problem with the preview.
The areas beneath the letters appear to be very lightly engraved. The preview shows as those areas getting engraved although the final outcome isn’t so apparent.
I’ve just re-traced the layer. It seemed to have worked, but I did notice the properties for this layer set to “multi”. It didn’t make too much sense at the time but I didn’t ungroup everything to readjust the power scale. The redone trace just had 100% power scale.
I did have to decrease this layer as this banner image was supposed to be a lighter colour within a crest design.
I don’t know why it would drop off the bottom as when I ungrouped everything the banner just came out black. It was only happening once I grouped all the letters with the banner.
I will keep an eye out on this going forward. I appreciate the extra eyes on this topic.
It’s my first time posting and my expectations are exceeded so far.
This is because of the power scaling applied on a per shape basis. The specific behavior was actually odd and I suspect either not working as intended or not intended to be used that way.
In any case, glad you seem to have a working solution.