You are not logged in.
I'm building Angband from sources with the following two configure options:
#1. X disabled (curses enabled)
./configure --with-setgid=games --disable-x11 --without-x --with-libpath=/usr/local/games/lib/angband --bindir=/usr/local/games
#2. Normal (X enabled, curses enabled)
./configure --with-setgid=games --with-libpath=/usr/local/games/lib/angband --bindir=/usr/local/gamesThere's two problems displayed by Angband:
- When running the game version with X11 enabled, the game takes 100% of one of my cores.
- When running the game with the X disabled version, or with -ngcu, the game runs normally. However, on exit the game overwrites my .Xdefault color settings and I'm forced to close the terminal and start a new one.
Anyone else experiencing these problems? How can I solve them? Please advise if you need any more information.
Last edited by marfig (2010-09-06 11:53:25)
I probably made this post longer than it should only because I lack the time to make it shorter.
- Paraphrased from Blaise Pascal
Offline
are you running angband in X11 in maximized mode?i experienced this behaviour in angband and other variants only in maximized mode... always seemed like a bug for me.
Offline
Sorry for the OT - but Angband is one good old classic game!
################
....@......D....M..^#
##########$#####
Last edited by sultanoswing (2010-09-06 11:50:37)
Arch on: ASUS Pro-PRIME x470, AMD 5800X3D, AMD 6800XT, 32GB, | ThinkPad X1 | ASUS ux303ua | Surface Laptop 2 | Minisforum UM780
Offline
Thank you danvari.
The high CPU usage happens -- on this system at least -- only during the game welcoming screen. I noticed by chance that when I leave that screen (by starting a new character for instance), cpu usage returns to normal. Your post prompted me to experiment a little and its when I noticed it's just on that screen. Before, I would just quit the game and try something else with the configuration or how I would launch it, and would never see past the welcoming screen.
The curses issue is afterall a known bug (#678) on the stable version. It's been fixed in 3.1.1. For some reason I kept on failing to see it on the issue tracker. My bad.
I probably made this post longer than it should only because I lack the time to make it shorter.
- Paraphrased from Blaise Pascal
Offline