LarryG on 17/3/2013 at 00:29
Boy that's out of my league. Let's hope that someone who knows more about this stops by.
Nameless Voice on 23/3/2013 at 21:19
Quote Posted by kdau
I'm not sure if you noticed, given how buried it is, but there's actually a (source) patch to your font tool in the NewDark distro (it's in fonttools_aa256_patch.zip inside contrib_editor_demos.zip). The patched thieffon.exe seems to work fine, but the patched wfon.exe hangs for me when it tries to actually generate the bitmap, so that code probably needs some scrutiny.
I thought I'd give this a try since I have the appropriate build environment set up to build this code (as I use GCC for NVScript.)
In any case, it seems to work fine? I built wfon.exe and ran it; it asks me to select a font and options, and then saves it out to a bitmap, ready for conversion into Dark.
That's what it's supposed to do, isn't it? I'll admit I've never used this tool before, I only ever created fonts from manually-created font images (as all I ever did to fonts was edit existing ones.)
The only issue I had was that the program seemed to disappear for about 5 seconds when I pressed the "ok" button, but after that it came back and asked me where to save the image.
kdau on 23/3/2013 at 21:33
Quote Posted by Nameless Voice
I thought I'd give this a try since I have the appropriate build environment set up to build this code (as I use GCC for NVScript.)
In any case, it seems to work fine? I built wfon.exe and ran it; it asks me to select a font and options, and then saves it out to a bitmap, ready for conversion into Dark.
That's what it's supposed to do, isn't it? I'll admit I've never used this tool before, I only ever created fonts from manually-created font images (as all I ever did to fonts was edit existing ones.)
The only issue I had was that the program seemed to disappear for about 5 seconds when I pressed the "ok" button, but after that it came back and asked me where to save the image.
Yes, that's the intended behavior. For me, it just sits at 100% CPU indefinitely after clicking OK. I built the patched version with MinGW from Linux, but had the same problem in both Linux and Windows 7, and the original code compiles and runs fine for me on both.
One other note for anyone working on wfon.exe is that the new HQ AA mode seems to have even more overlap of glyphs over their bounding boxes than the basic AA mode. It would be great if the BBs were accurate without manual adjustment, but I wouldn't wish anyone the requisite journey through the Windows drawing API. :eww:
Nameless Voice on 23/3/2013 at 23:42
That's strange.
I suppose you could try the version that I built and see if that does anything different.
Telliamed on 26/3/2013 at 06:58
If you've got Gimp, I made a plug-in to do the same thing. Still doesn't get the boxes quite right, but they're drawn on a layer so you can tweak it before saving to BMP.
(
http://whoopdedo.org/font-pinkbox.py)
Copy that to /.gimp-2.8/plug-ins/ then restart Gimp. Open the Font window and in that window's menu will be "Draw Pink Boxes" using the selected font.
(whoah, what the hell happened to this post? I swear, this BBS really hates Chrome.)Squadarofl on 26/3/2013 at 19:29
Quote Posted by Daraan
[...]
That might increases my chance that this will be fixed in version 1.21:cheeky:
Weeelll... I guess you were right; Le Corbeau just posted this a little while ago
Thief 2 v1.21 : (
http://ge.tt/3HKfoDc) | md5 : e4a6edf0f29915517b4ce11d21f1b8e9
System Shock 2 v2.42 : (
http://ge.tt/3HKfoDc) | md5 : c8af4c0d5ca6673e81712e70530bb141
ARIANNE THREAD : (
http://ariane4ever.free.fr/ariane4ever/viewtopic.php?f=2&t=4287&sid=10066c1a27f5a77e5fc50f6cf9aec00a&p=29235#p29235)
EDIT : Here's the changelog
Changes and fixes for v1.21
---------------------------
General:
- fixed handling for multiple displays and GPUs
- fixed a small non-critical glitch in FMSel
DromEd:
- fixed issue that caused wireframe drawing in 2D viewports to go nuts on some video cards/drivers, when running DromEd with hardware rendering
- fixed bug when saving Rendering Parameters in T1 mode (would cause ambient light to lose color info and all other parameters not originally in T1 to get reset)
Sources:
- added missing file to FMSel source package (fltk patch)
- updated sources to build referencing the latest CRT DLLs (VS08 SP1 9.0.30729.1) so the private assembly fallback works
voodoo47 on 26/3/2013 at 20:04
well, here we go again - guess I will have to test a bit and roll out TFix 1.15 in a couple of days (that means full relights and reprocesses will be released in 1.16).
no rest for the wicked.
Vae on 26/3/2013 at 20:09
Thanks for all your good work , Voodoo...:thumb:
kdau on 27/3/2013 at 03:41
Quote Posted by Nameless Voice
I suppose you could try the version that I built and see if that does anything different.
Per our PMs, yes, the last one you attached here works great. Thanks!
Quote Posted by Telliamed
If you've got Gimp, I made a plug-in to do the same thing. Still doesn't get the boxes quite right, but they're drawn on a layer so you can tweak it before saving to BMP. (...)
Why yes, I do use GIMP, thanks! :D The separate layer is most convenient.
Quote Posted by Squadarofl
Weeelll... I guess you were right; Le Corbeau just posted this a little while ago (...)
Again already? The poor raven's beak must be tired from all the typing... :cheeky:
R Soul on 29/3/2013 at 17:14
Now we get a big red box showing us the +-1000 limit.
