Not sure if anyone else has come across this issue before, but I just had LaserWeb3 do an “Aw Snap!” part way through a job.
I believe the reason why is because I was zooming in on the raster (2.84 million queued gcode) & it was lagging badly, then decided to “Aw Snap!”.
Anyway, point of the story is I just hit “Reload” from the little popup that appears & it seems the job is still going, albeit with no picture on the LW grid. So I guess the job is still in Chrome’s memory? Either way, don’t freak out (like I originally did) if it happens to you in the middle of an engrave job.
Anyway, I originally tried a 300dpi version of this image, it turned out to be 2.87 million gcode, so this 72dpi version is slightly less. Either way, I think I’ll be here a few hours.
Anyone have any tricks to speed up the engraving process? (as this is just my “test” image before I go engraving it onto leather, so I have to do it again, maybe even multiple times if I am not happy with the quality/light-dark balance).
