URL:
<http://gna.org/bugs/?11121>
Summary: Briefings not displayed at high resolutions
Project: Warzone Resurrection Project
Submitted by: pabs
Submitted on: Friday 02/22/2008 at 05:14
Category: Engine: Graphics
Severity: 3 - Normal
Priority: 5 - Normal
Status: None
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 2.1_beta1
Operating System: GNU/Linux
Planned Release: None
_______________________________________________________
Details:
Forwarding a bug from the Debian BTS from Roland Mas:
http://bugs.debian.org/466897
Warzone 2100 ceased displaying the mission objectives to me,
apparently with the latest upload. I get the background briefings (displayed
on a black background, since I presume the original videos haven't been
liberated), but the actual orders do not appear, and I get an empty box with
only "Briefing commences" at the top.
I thought it was related to the fact that I progressed through
missions, and maybe the objectives were only displayed for the first handful
of missions, but that doesn't seem to be the case, since the Tutorial/Fast
play mission suffers from the same behaviour (and I distinctly remember
having played it and having seen objectives). I tried renaming my
.warzone2100-2.1/ directory, to no avail.
Further poking led me to a surprise: the default resolution for the game
(800x600, or maybe 640x480) does display the briefings. But when I go back
up to my usual 1680x1050, not touching other graphics option, they disappear
again. All resolutions starting from 1280x960 exhibit the bug; 1152x864 and
under work fine.
I don't see how resolution could have an impact on displaying one
particular piece of text (the others are okay, including the other pieces of
"Intelligence reports"), but there you have it.
Confirmed. I had a look at the diff. diffstat said "201 files
changed, 3945 insertions(+), 5322 deletions(-)", but I sort-of-guessed that
the problem would come from src/intelmap.c, where the diff is much smaller
(+20, -18). I didn't isolate the precise change that triggered the bug, but
replacing the file with the version from 2.1.0~0.svn3595.dfsg.1-1 fixes the
problem for me.
I would therefore suggest reverting that particular file to its
previous version, unless of course the actual fix is found and
applied.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?11121>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Warzone-dev mailing list
[email protected]
https://mail.gna.org/listinfo/warzone-dev
