For those that don't have menu text in the latest BETA 2.1 build

[Frumple]

I'll note that I have the block-text issue as well, on a vista machine.  Looking for a solution (It should probably be noted that the 2.0.1 build works just fine.) I noticed that a common theme between the folks having the same problem seems to be an Nvidia graphics card... which I have as well. Perhaps the issue lies there?

Oh, and the testbuild thingy at the top of the thread doesn't fix the problem, it in fact makes the blocks, menu, etc, completely disappear.

[Buginator]

I'll note that I have the block-text issue as well, on a vista machine.  Looking for a solution (It should probably be noted that the 2.0.1 build works just fine.) I noticed that a common theme between the folks having the same problem seems to be an Nvidia graphics card... which I have as well. Perhaps the issue lies there?

Oh, and the testbuild thingy at the top of the thread doesn't fix the problem, it in fact makes the blocks, menu, etc, completely disappear.

2.0.x used bitmap fonts.
2.1.x uses a different font system, so international character sets can be used.

It isn't Nvidia or ATI issue, it is a quesoGLC or fontconfig issue. 

For the testbuild, did you un7zip all folders  to where ever the original beta version installed, and then did you run the warzone2100ms.exe ?

[The Commander]

What is the differance between these two files?

"warzone2100-2.1_beta1.exe"
and
"warzone2100-2.1_beta1-r1.exe"

I noticed if you use the 2nd one that all the writing on the main menu is all block letters. The only way I can use normal writing is with the first 2.1 beta. This may help others I hope.

[Buginator]

It isn't Nvidia or ATI issue, it is a quesoGLC or fontconfig issue. 

It could be something else, so here is another test to find out more. DON'T put these in your warzone install!

This just displays font tests.

un7zip to whatever directory. [like d:\tempkill]
Run these from console (ie, start->run->cmd.exe)
type cd d:\whatever directory (that you un7ziped to) in this case, it is cd d:\tempkill
then type d:
then you can type dir, and it will show all the files that were in the archive.
then start doing the tests.

When done, feel free to delete the d:\tempkill directory & the archive.

I just need to know which one(s) fail.
Thanks!

[DevUrandom]

What is the differance between these two files?

"warzone2100-2.1_beta1.exe"
and
"warzone2100-2.1_beta1-r1.exe"

I noticed if you use the 2nd one that all the writing on the main menu is all block letters. The only way I can use normal writing is with the first 2.1 beta. This may help others I hope.

The first build uses QuesoGLC 0.6.5 and the latter uses 0.7.0.
Most people so far claimed that fonts were broken on Windows with both 0.6.5 and 0.7.0, so I didn't bother anymore about it. But if 0.6.5 works for you, then it is a general issue (also present on Linux) with 0.7.0.
I'll build the next beta with 0.6.5 till 0.7.1 is released and fixes the issue.

[Verminus]

yea i can confirm that on my Ubuntu install at least Quesoglc-0.6.5 works fine. but if I try to use 0.7.0 then I get blocks instead of text. so i guess this is  a Queso problem and not a WZ2100 one...

[Mezoth]

I just need to know which one(s) fail.

Test7: Failed to get the bounding box of the space character

All other tests showed successful, test 10 displayed ABCD in red font on a black background.

[Zythran]

I just need to know which one(s) fail.

Alright, here's the rundown for me:
demo.exe - pass
glcdemo.exe - pass
glclogo.exe - FAIL with message: GLC ERROR - glcFontFace() returned GLC_RESOURCE_ERROR
test1.exe - printed "Tests successful"
test10.exe - printed "ABCD"
test4.exe - printed "Tests successful !"
test5.exe - printed "Tests successful"
test6.exe - printed "Tests successful"
test7.exe - FAIL with message: Failed to get the bounding box of the space character
test8.exe - printed "Tests successful"
testcontex.exe - printed "Tests successful!"
testfont.exe - appears to pass, synopsys: "Current font count : 1" ... "- Family : DejaVu Sans Light"
testmaster.exe - appears to pass, prints information on masters up to "Master #124"
testrender.exe - passed, printed Bitmap, Line, Triangle, Texture
tutorial.exe - passed, printed "Hello World!"
tutorial2.exe - Likewise passed
unicode.exe - passed, with Danish text

This was all on my girlfriend's ATi-based laptop, on which neither of the beta builds have worked.

As an aside, I seem to no longer be able to start network games on my Gentoo box (the beta worked once, now neither beta nor original build work - freezing) but this may be my own fault, and I haven't tried rebuilding yet.

[estefaz]

Hiho

As above.

test7.exe results in the message "Failed to get the bounding box of the space charachter"

rest seems to work.

Greets, faz

[Buginator]

As an aside, I seem to no longer be able to start network games on my Gentoo box (the beta worked once, now neither beta nor original build work - freezing) but this may be my own fault, and I haven't tried rebuilding yet.

I believe the ports are a bit different.  Also, it may freeze while it is polling, trying to find the master server.  If that is down, then you have to wait for the timeout period before you can do anything.

Also note that you can't mix 2.0.x & 2.1.x versions, it will crash.

Thanks for the info on the tests!

[Laserlight]

Just tried the beta and i do not not get the correct font either..
Its does not matter what card you got.. tried it on my pc (FX5500) and my laptop (G965) and makes no difference.
But the new beta looks like it will improve the game allot i hope..
Good work and cya..

P.s I am back, got broadband now so i can be online..

[doom3r]

Same here. Just a cube where a letter should be in every screen, looks like everyone here has the same bug. Are you developers having this bug too?

[DevUrandom]

We have found a likely cause for that bug, and will release another beta soon. We hope it fixes all font issues and you are free to test the netcode then.

[Arbraz]

OK guys, but this topic don't explain to me how to do ! Sorry i'm french  ::)

I can(t eliminate that blocks.

Thanks a lot

[Kamaze]

We have found a likely cause for that bug, and will release another beta soon.