ToME WikiStrange problems in the current 234 version of TOME.
In ascii mode there are no visible floor tiles at all.
Here are some screen shots to demonstrate.
It wouldn't matter normally to me one way or the other but, you can't see important things like... oh lava as I found out by dying (heh). I've tinkered with my brightness and contrast too and it makes no difference, the floor tiles just don't show up. Here's the different tile sets and how each looks, old and new would be usable but I loathe the graphical tile sets, the last time I had tome installed it didn't have this problem. Not sure what's causing it, but I did verify that it wasn't just an issue in this particular version, I downloaded 227 and it was having the same problem.
I (for the first time) ever have had to have Bizarre display turned on also because without it a lot of tiles are missing in general and i get the lagging @ sign.
This is the downloaded windows .zip version that I'm using.
Any ideas?
ShadUs: and yes, I do have a torch/lantern equiped with fuel remaining - and the town pic is during the day. I also downloaded vanilla angband and it doesn't seem to be having this problem, not sure if thats a help or not. This bug also does NOT seem to affect tome 3a12 (which may be explained by what i found out below, since tome 3a12 is using standard chars # . etc... rather than the highascii like tome 234.)
ShadUs: I went to the tome screen % then hit 8, then n till I get to number 88 (dirt-- one of the many items that isn't showing up at all) quite literally what I get is:
Terrain = 88, Name = dirt
Default attr/char = 15 / 46 << . >> Current attr/char = 15 / 31 << >>
As far as my system is concerned whatever char 31 is... doesn't exist. I noted that sorting through the list there are no ANSI solid blocks except the completely solid one (Current attr/char = 1 / 127 which is 0x7F in the pref file) In fact there are no character at all starting at 28 all the way to 32 (including it). Then there are standard alphanumerics from 33 to 126 and 127 is the solid square ansi block, then 128-255 is nothing at all. Odd.
Knowing this let me swap the contents of the dos/win font files nad the game is playable, but this is kinda weird still. Any suggestions on a fix or possible cause?
NeilStevens: AerdanRunestar suggested on IRC that your problem is your font is missing a character. Oh, and the character at issue is NOT ASCII. ASCII ends at 127.
ShadUs: I know, technically my problem would be with the ibm-pc extended ascii character set (everything 128-255 is missing)... although it bothers me that this problem seems to occur even with older versions of tome also. I know this problem didn't use to occur. I'm also missing characters from 28-32 inclusive. Does tome use any system fonts or strictly the fonts in the lib/xtra/font directory? hmm i may see the problem actually. I have a veramono.ttf font already installed, gonna yank it from the system reboot and see if that corrects my issues. The thought occurs that it's using my system version rather than the one in the tome lib/xtra/font, is it possible to force tome to use a different font?
Pulled my copy of veramono.ttf and replaced it with the version in the lib/xtra/font directory from tome and rebooted, still same issue. So back to my previous question, does tome use any system fonts or just fonts in lib/xtra/font?
ShadUs: After becoming highly annoyed at not being able to play my tome the way I wanted, I blew my entire system off and reinstalled from scratch. Things are working presently and after each app I'm going to check and see if the graphics glitch comes back. I had two years of cruft built up since my last reformat so it was about impossible to pin point the problem... and since this is primarily my gaming box its entirely possible that it was some copy protection rootkit or something similar. If i can figure out the app i'll let you know.
AustinMcDonald: I have the same bug on a reasonably fresh install of Vista. Has anybody found a workaround that doesn't involve a reformat?
DanielFishman: (copied across from BugReport830, which I assume is the same bug as you (Austin) are suffering from). I have managed to find a (sort of) solution to this problem. NPPAngband 0.5 has some custom fonts which a solid block character (char 1), and also the smaller '.' character used for floor spaces in ToME. http://members.cox.net/nppangband/download.htm Then you just need to change the lines in font-win.prf from 0x7F to 0x01 and from 0x1F to 0x07.