If you let me know which ones, I’ll take a look - send me a PM if you prefer. Also, what would be the minimum gap between lines that you could resolve with the laser?
I think that you can use “! _SelBadObjects” to find the lines that create bad objects. I will write all letters and will make a screen-shot with the ones that this particular command recognizes as bad.
As for the spacing, I was using 2 millimeters between characters, even though some of them needed to be 1 mm closer in certain combinations, such like:
“-7”, where the number 7 was too far away from the “-”)
“LT” (1 or 2 mm closer due to the large space in-between)
PS: This is the alphabet, both in capital and small version. The selected (yellow) curves are bad objects according to Rhino. I also noticed couple of missing lines in the small letters.
Great, thanks for the info - I’ll check them out.
I managed to get the “MecSoft_Font-1.ttf” font to show up in the font list, but not the “BulgarLineA-Laser.ttf”.
It’s a work in progress - except I haven’t had much time to progress it of late. I need a better understanding of how Rhino interprets it to iron out the wrinkles.
Anyway, were you trying to install it on Winows or Mac?
AH ! It works, but it required to close and re-open Rhino.
It works in V6 and V7, but all the numerals don’t pan out…
I’ll try and find some time to take another look at it sometime soon. Unfortunately my font editor is on my desktop pc and I’m away from the office at present.
Thanks Jeremy, I found a viable workflow here, with the Mecsoft font.
I find it amazing the McNeel lets us struggle with this while they claim to provide the perfect tool for CNC hobbyists…
@jeremy5 I noticed there are a lot of duplicate lines in your font, I think this makes it fail
As Windows doesn’t support single line fonts, they are fudged by superimposing the two sides of each stroke, rather than placing them a stroke width apart. (It’s actually rather more complicated than that.) That may be resulting in what you see. The problem, in a nutshell, is getting the balance between ‘duplicate’ lines - which are needed for the font to render as a font in the textbox - and single lines - which are all the tool needs.
@jeremy5 but for laser engraving this is not nice I think, because that means the laser will have to make some double strokes too, which is a bit of a waste. The mecsoft font doesn’t render well, but is a true single line font. In Rhino 7 btw, I can get the font to output correctly when checking the engraving checkbox, but with double strokes. When not checking the engraving checkbox I see what @osuire posted, on the Mac it is even worse (lower one with ‘engraving font’ checkbox)
would be nice if you could fix this, because it is a clear geometric font. The mecsoft is also usable but has some ugly curves in it. It’s been long time ago that I touched a font editor. I tried to open the font in font forge but on windows this program is unusable, I might give it a try otherwise on the Mac.
@gijs, That’s interesting - I guess that the ‘engraving’ checkbox causes Rhino to remove overlapping curves before rendering. I have asked @stevebaer in another thread if there is any documentation on what Rhino expects from a single line font, so hopefully I will have something to inform my implementation when I get back to my office. I hope to complete the font in due course.
An update to my font editor has removed the loophole that allowed me to create an unclosed contour in a font, which was fundamental to my approach. In compensation it has made closing contours either by overlapping paths or creating a closing line a trivial task. I now have a choice: I can create a font that previews in in the Rhino 6 TextObject window as black blobs but renders as single lines (like mecsoft), or one that previews legibly but renders with duplicate curves (which could be selected and deleted). Next session I’ll see what happens in Rhino 7.
I don’t see that in WIP 7.0.20042.9575, 11/02/2020 - is it the one from this thread? Wish List item: SINGLE STROKE FONT - the link is no longer available.
Hi Jonathan - I was mistakenly assuming that we shipped that font with Rhino on the Windows platform.
You can still download that font from this post:
I’ve started to get this each time I open rhino or new doc after a few uninstalls and reinstalls:
Read 1 annotation style that references 1 font that is not installed on this device. Annotation style referencing a missing font: Engrave / SLF-RHN Architect Regular Missing font: SLF-RHN Architect Regular
That’s a known issue in the Service Release Candidate - trying to fix a superscript issue with that font broke things. Hopefully, a fix will be in next week’s build.