Crispy on 4/3/2006 at 04:13
Hmm. Well, I'll try using 0 as the first number and see what happens. Thanks for the Carleton font map, the more examples I have the better. :)
Anyway, I've just realised that the CEL file is listing Latin-1 encoded characters, numbered from 0 to 255! They just stuck the non-standard Xbox stuff into some of the lower-numbered control characters that normally aren't displayable. This is great because it means I don't have to make a tedious lookup table for converting font glyphs to their positions in the CEL file - I just pass the number of the character to my font library and it'll tell me which characters can't be rendered. Woot. :D
New Horizon on 4/3/2006 at 05:16
Quote Posted by Crispy
Hmm. Well, I'll try using 0 as the first number and see what happens. Thanks for the Carleton font map, the more examples I have the better. :)
Anyway, I've just realised that the CEL file is listing Latin-1 encoded characters, numbered from 0 to 255! They just stuck the non-standard Xbox stuff into some of the lower-numbered control characters that normally aren't displayable. This is great because it means I don't have to make a tedious lookup table for converting font glyphs to their positions in the CEL file - I just pass the number of the character to my font library and it'll tell me which characters can't be rendered. Woot. :D
Not sure I understand what that means...but SWEET! :thumb:
Crispy on 4/3/2006 at 06:32
lol.
Turns out that the font library seems to insist on generating those "no such glyph" boxes instead of actually returning an error code, but oh well. Doesn't make much different except for wasting a bit of texture space (which would probably get wasted anyway).
Enough talking... MORE SCREENSHOTS!
(
http://members.byond.com/Crispy/files/t3fonttest.jpg) Clicky.
Still a few glitches to iron out - the glyphs are appearing way too big and are resizing in ugly ways, for a start - but we have definite progress! This only works if I turn blockloading off though; if blockloading is on, I get mangled Papyrus, because it reads the Papyrus DDS file from the IBT, and the CEL file from disk. And turning blockloading off on my non-editor install gives me a nice crash when it tries to access the non-existent resources that aren't in IBTs.
Freakin' IBTs. :rolleyes:
I had to remove the background in Photoshop and save as DXT1 with 1-bit transparency to get this to work properly.
The font shown is Deja Vu Serif, simply because I had it laying around for use in another project.
New Horizon on 4/3/2006 at 06:37
That's looking great Crispy! :) Great work. This will be such a great tool for the community. Thanks for doing this. Can't wait to try this out and make some custom scrolls and books.
Crispy on 5/3/2006 at 03:07
Well, it's still a bit dodgy, but here's the program:
(Edit: Old version removed, read on for the current version.)
And another screenshot, this time with Carleton: (
http://members.byond.com/Crispy/files/t3fonttest_carleton.jpg)
Share and enjoy. This message was brought to you by the Sirius Cybernetics Corporation Complaints division.New Horizon on 5/3/2006 at 16:42
Crispy, this is absolutely wonderful. :) So easy to use, I love it. Just some minor feedback that will hopefully be a quick fix and not hurt the functionality.
Carleton works great, but the j.d.ttf texture is being cut off at the top. I should have given you more info on the placement requirements.
The easiest way to explain it is like this. On the carleton font, the top of the dollar sign symbol is currently sitting flush against the top of the bitmap texture. When I created my fonts by hand, the highest point of the dollar sign on a 512 x 512 carleton texture had 5 pixels above it. This would allow for any differences between fonts and will correct the problem with the j.d. font being cut off. :)
Example of the old hand made textures.
Inline Image:
http://newhorizon.veledan.com/fontspace.jpgAlso, would it be possible to shift the placement 1 pixel further to the right? There is some minor cut off there as well. Other than that, it's perfect.
Hope that's not a difficult fix. Thanks.
Crispy on 6/3/2006 at 10:21
Looks doable. I think I'll add the offset amounts as a command-line parameter though, since some fonts might want more offseting and some fonts might want less... in other words, I can't figure out the required offset reliably so I'm going to pass off the decision-making to someone else. :cheeky: :angel:
Glad you like it!
I'll edit this post or bump the thread when I've made the changes.
EDIT: Version 0.5.1 is up.
EDITx2: Version 0.5.1 has been superseded, see a later post.
New Horizon on 6/3/2006 at 16:27
Working perfectly now that the offset is in place. :) The final problem is that some of the glyphs used in the original T3 font textures, aren't being rendered onto the new texture by font taffer. I'm sure this has something to do with the way they're being displayed in fontlab. For example, the 1/4, 1/2, and 3/4 glyphs show up as being greyed out in font lab and this translates to a square box when fonttaffer tries to create it. I'll see if I can figure out how to make those symbols accessible to fonttaffer, just don't know how to ungrey them in font lab.
New Horizon on 6/3/2006 at 19:58
I can fix them in Font Lab, so no worries. I'll whip up a package of the most common classic Thief fonts for conversion and post the dds and .cel files.
I can't thank you enough crispy. :) This has taken something that once took me many painful hours to complete and now made it into a joy...and with fontlab, I can recreate any custom glyphs. :)
Crispy on 7/3/2006 at 05:36
Quote Posted by New Horizon
The final problem is that some of the glyphs used in the original T3 font textures, aren't being rendered onto the new texture by font taffer. [...] I can fix them in Font Lab, so no worries.
I didn't actually write any of the font functionality, so I have no idea how to fix that on my end! Glad you got it working though. (How did you fix it, out of interest?)
Quote:
I can't thank you enough crispy. :) This has taken something that once took me many painful hours to complete and now made it into a joy...and with fontlab, I can recreate any custom glyphs.
I'm just glad I actually managed to contribute something decent at last. :)
