Chaosforge Forum
DoomRL => Bug Reports => Topic started by: Cheater on September 14, 2010, 16:39
-
This started happening recently, DoomRL worked
perfectly pretty well before.
Basically, I have no line wrap for the output (and it also isn't put in place by dvtm, but I think these issues are correlated). The game just outputs ASCII as far as the screen allows, so I get 2 lines of game text per terminal line. It doesn't work in a plain terminal either (without fbterm and dvtm).
However, it does work inside a terminal emulator in X. Any Idea of what the problem could be?
(http://img163.imageshack.us/img163/3303/doomy.png)
ETA: This also happens with Berserker!
-
If i understand correctly, DoomRL is specifically built for an 80x25 geometry terminal, and looks like there aren't any routines in it to validate its environment (and that would be too platform-specific anyway). Configuring the terminal to provide an 80x25 geometry before launching the game seems like a reasonable workaround (and all the shell scripts provided with the game do this too).
-
Checking log.txt (I can't believe I didn't see it before), gives me this revealing, yet still compellingly obtuse error:
<TTextModeOutput/0/0> Initialized.
<TTextModeOutput/0/0> Setting ASCII video to 80x25 color.
<TTextModeOutput/0/0> Failed to set ASCII 80x25 color textmode.
ETA: Also, after reboot, it no longer works in X.
-
1. how are you starting the game? what terminal emulator inside x, or what shell if without x/
2. I don'nt have such problems with a recent build of Berserk even if I maximize the Konsole (KDE terminal emulator) window - the game keeps just to 80x25.
3. the same goes for doomrl 0.9.9.1 (using the download from the website) + 32bit lua libs
I guess it's a problem on your end, so let's get back to point no 1 - how exactly are you trying to run the game?
-
1) Inside X, I tried with urxvt-unicode and xterm (Both ./doomrl, ./doomrl_xterm starts an xterm session that immediately closes). Without X, in bash.
2) When DoomRL works in X (which it does occasionally) it does keep to 80x25 in a maximized urxvt.
ETA: My word! Installing fpc from the AUR seems to have solved the problem. I probably shouldn't say anything out of fear of jinxing myself until I test it further. Thanks for the help!
-
that's strange... how installing the compiler could have fixed anything? ;-)
Anyway what you are sayin in point 1 and 2 doesn't seem to be comprehendable to me - first you say that it doesn't work in urxvt, and then you say that it works in urxvt... :-)