The designer of this FontStruction has chosen not to make it available for download from this website by choosing an “All Rights Reserved" license.
Please respect their decision and desist from requesting license changes in the comments.
If you would like to use the FontStruction for a specific project, you may be able to contact the designer directly about obtaining a license.
Discopatentiously Obstructivenating font Copyright 2016-2019 Doug Peters.
This is my own clone of the original version. It may look a little like my Kindegraf or Sketchy fonts, as it's my handwriting with a mouse, and I bet there isn't a lot of deviation there (with the handwriting) but it IS different. More characters would require more work. Happy to do it, but not for free.
Categories: Pixel font.
Types: Hand printed lettering.
Weight: Regular, Curly.
Web font: I don't think that would be a good idea, NO.
Commercial use: When Purchased.
Derivatives: NO.
Redistribution: NO.
https://www.Doug-Peters.com
https://Dougs.Work
https://SymbioticDesign.com
https://Worthful.com
https://Font-Journal.com
My best Domain Name registration service:
https://www.DomainHostmaster.com
My best cloud web hosting solution:
https://HDWebHosting.com
PayPal donations (to encourage my continued design efforts):
https://paypal.me/sitedesigner
26 Comments
Trying to get the line height right (as it's all wrong).
I fixed it for Fontstruct with some tall characters (I think the unknown character, vertical bar and some floating accents did the trick in here) and for Photoshop I had to take off the .5 x .5 grid. Then, it worked. The leading in the sample text (not the font name, though) below is all auto leading...
space
WHAAAAAAAAAAAAATTTTTTTT IS OF PIXELS!!!!!!!!!!!
At pixel view, I see anti-aliasing... When working with pixel fonts, make sure to set spacing in intervals of 1 unit (1 unit = 1 grid square)...
So... you are all saying that a pixel font should be treated as a monospaced font with the same sized working character area for each and every character?
Jeepers.
@DP It doesn't have to be Monospaced... Just that the spacing of a Pixel font should be snapped to the pixel grid...
I'd only suggest widening the space. 10/10
It is. Every filter is set to 1. The left line and the base are starting points and characters snap to them, though there are overshoots of 2 pixels on characters with curves and maybe pointy ends. It is a 37 pixel high font, otherwise.
@DP Did you check the width of the letters and the Global Spacing?
Nice! It certainly creates interesting effects whether it's rendering smooth or pixelated.
You'd be surprised what kinds of fonts people will buy. I think this one could succeed commercially on the right websites. It's really expressive and versatile, two things which I cannot say about the majority of generic script designs which people buy every day.
You know, @77, there are optical illusions in there. I know a little bit about anti-alaising and used it at times, from a human perception perspective. But hey, I started out as a pixel artist. At 640x480 you learn how to take advantage of pixels to faux in a look. There should be lots of gray spots when rendered at the correct size because of how we perceive stuff. And the font will look widely different at different (non-optimal) sizes. At multiples of 37 it will just look pixelated, though, unless you throw in a little magic and upset the math. Which can have good or bad consequences, depending on how it is used.
Wait. I responded once before this last one above, and then I edited it twice. Where is it?
Comments vanish when edited too much. Or it's when edited too often in too short a time window, I don't know which.
Fine. I'll stop correcting my typos and just let everything fly from now on. The only reason I do it is because of spelling naggers. I am happy to do it so that I can communicate better with everyone, and seem more intelligent, but if my posts are going to be blasted away into oblivion, I could care less.
I was telling 77 that the letters all snap to the left line and the baseline. That there are overshoots under the baseline for curves and pointy things. The letters and characters are the width they are, not some specific width. Aside from overshoots and high hanging accents and marks (or the low line, the cedilia and descender tailed letters), the letters are all 37 pixels talls. The exception being the vertical bar and the unknown character glyphs (3 of them), which were created (along with the accents) specifically to correct the issue where Fonstruct would overlap the letters in preview (quite dramatically).
The skinniest glyph may be the vertical bar which is extraordinarily tall and deep for increasing line height, but is only 10 pixels wide. 11 if you count the extra pixel of cushion. The gap between letters is 2.75 globally (I think I remember that right -- I hope so, but I will check and if not I will make another post instead of correcting this one).
Or just draft your comments in a text editor. I've been known to do that!
Maybe the 2.75 global spacing gap is the issue that @77 wants resolved? Is that a measure of pixels?
@DP Yes, you can round it up to 3... It is also a measure of bricks too...
Tip: Decimal Values on a pixel font at pixel resolution can cause Anti-aliasing (at pixel size)...
Hmp, whatever... this looks wonderfully handwritten (at whatever size it's printed), using a pen that doesn' ink on evenly: so clever! So natural! Spacings are natural under that angle of thinking, too. BTW, I simply love the name! Hyperrifically well done!
OK, Global Spacing Gap set to 3. I guess that makes sense.
Hi, @Aeolien! ;) Lately, I have been trying to come up with font names that no one else would want. This was probably one of the first of those. I was going to change it, no one will ever be able to remember it, or much less spell it. But, who would really want it? I guess the name grew on me, too. Anyways, I never did change it, so I guess I thought it fits. I'm glad you like it.
Now to decide where to take it from here. Hah!
Lol, the Space is finally been addressed (18 pixels wide, now). Not used to moving around that width bar on space. Thanks, @JingYo & @Cookielord. Photoshop must've over-wrote the few pixels it was at, because in my sample text images it was fine. That's crazy.
@DP You can also round the right bearing of the lc j up to the nearest pixel...
@77... The right bearing of the lowercase j? What is the right bearing? The width? I looked at it. There was an extra pixel of space between the left border line and the j, so I moved it over 1 pixel. The width bar didn't move, so maybe that's what you are talking about, but I hit the x on that line so that it would snap to it's default. I also thought the bottom of the j was a bit flat so added a single row of pixels at the bottom to round it out. Thanks for the catch on the strangeness of that character, I hope I addressed what you were talking about. I think I might have nudged the width line somehow by accident, the whole font was supposed to use the default character width.
Hmmm... It seems the i and 4 are also 1 pixel off... I am going through all the characters now. The 4 width snapped correctly, but I had to make the i width snap to the default setting. You sure are thorough in your critiques, thanks! ;)
It looks like the Q is an exception to the default width scenario because of the under baseline tail.
I moved the t over a couple of pixels, too. Added a small pixel line to help round out the top of the f and s.
Please sign in to comment.