Also remember that on occasion the result of an error can sometimes be a better result than the original intention 
1 Like
I agree. Keeping the SHX fonts in their own folder, just makes the most sense to me, as well. I liked the suggestion another user supplied (not in the posting, and sorry I can’t recall their name), and added “1-“ to the front end of each SHX font’s name, allowing me to readily see those fonts as a group, and as the first fonts in the font list, in Lightburn.
The SHX fonts I loaded certainly seem ideal for very small size usage. I didn’t try anything as small as 2mm, but I was working on some leather pieces, and I wanted them to be a bit more prominent. Look forward to hearing how tiny texts with the SHX worked out for you.
Lee
1 Like
Chris
Wow, 2mm is tiny! What type of material did you use?
I’ve only had the opportunity to try them on our xTool P2 so far, and on leather, but I’ll also need to test additional materials, as well as on our D1 Pro.
Cheers
Lee
Chris, you are so right! I always enjoy working through an issue, and finding a good resolution!
Cheers
Lee
I have a more technical reason for keeping them separate. Windows is a resource gathering machine. The more resources it gathers, the slower it goes. If you want to see a difference, especially at boot-up time, add 50 or so new fonts to the Fonts folder.
The impact is not so obvious with the newer machines having Solid State H.D.'s, but when you have 20-secont boots, 25 seconds is irritating. 
1 Like
That might have been one of my posts on SHX Font support.
1 Like
I can’t remember which projects used the smallest, but I’ve done 2-3mm on basswood, slate, stainless, and coated aluminum.
Sorry about the blur, but this was for a customer… 2mm th’k basswood. Makes that bottom line text maybe 2.5mm.
1 Like
Rick
You are right on point! Your post was my source document! So sorry I wasn’t able to connect the dots earlier, and provide proper acknowledgement. That was a very useful and helpful naming suggestion.
Cheers
Lee
1 Like
I totally understand. I haven’t worked in the Windows environment in almost 15 years, but still recall they could be resource sensitive. Definitely must stay vigilant.
Our windows machines I had at my govt job, in the early days of our LAN/WAN, were more of a turn on and go get a coffee, and maybe they’d be ready for login credentials when I got back. Glad you aren’t in that sort of waiting pattern!
Cheers
Lee
Reducing the applied power of a 60-ish W CO₂ laser using Dot Mode makes perfectly readable 1.5 mm characters on scrap CDs. These digits are in a different font generated by a different program, but the size-on-target is the same as the SHX fonts I’ve used:
Trying to draw them in ordinary vector mode doesn’t work as well, because the power can’t go low enough to compensate for the low speed on those tiny curves.
No worries, all good. Just wanting folks to be able to find your reference. 
1 Like
Remember downloading text at 300 baud and reading it as it arrived?
Yeah, those numbers look like they have goose bumps!
Here is my test (first try!): 2500mm/m, 35% pwr, 10w, 3mm Baltic ply, ISO9 font. I was actually surprised at the result. Should have put a space after the “1”, no?
1 Like
Dang, that 1.5 mm font is tiny. Cool seeing it used like that on an old CD. I haven’t yet found a setting that allows me to limit the power on my 55-watt Co2 laser, on leather. I was using 1% power and 250mm/s which was the max speed offered. I still have lots to learn.
Lee
Mike,
The fonts look nice. Since I’m mostly using XCS with my xTool P2, it limits the speed to 250 mm/s. Their proprietary software allows access to all of the features in my laser. I wish Lightburn allowed me to access the built in cameras, in my P2. Maybe someday.
Lee
That is almost 3x the top speed of my Sculpfun. If you are burning tiny, I doubt you can reach that speed. Your machine can do stuff mine can’t, so there is always a trade-off. It explains why some guys have one of each!
Petition xTool to play well with others. If they do not share technical details, the Lightburn team has no idea how to code for it.
1 Like
Thanks for your input. I’ll definitely communicate my needs to xTool, regarding sharing both of the camera’s datastream, as well as the internal material thickness measurement data. I totally understand there is no way to write code to handle unknown data.
Lee
The link below illustrates my interaction with xTool. Skip to the second posting. I was told killing 3rd party use of the RA2 was an “engineering decision”. Good luck!
1 Like
you can also mark a font as a favorite to keep it at top of font list (select font - Right Click)
2 Likes
Hey Mike
Thanks for the info, which I read as a solid “heads up”.
won’t be completely surprised if my request is either summarily rejected or I’m told to go pound sand. I’d say I probably have an extremely low chance of succeeding. It might be an easier sell if they weren’t using the cameras tied into proprietary systems (autofocus, as well as the system to recognize and setup their new variably non-flat lasering function). Perhaps at some point there might be a basic call allowed, to gain basic camera functions, without fear the overall handling of their integrated cameras and the “smart functions” could be at risk of exposure. Fingers crossed!
Lee
Thanks for that Chris! Another good handling solution.
Cheers
Lee