http://bugs.winehq.org/show_bug.cgi?id=15881
Summary: Pharaoh - can't play on fullscreen Product: Wine Version: 1.1.7 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: nobange@poczta.onet.pl
Pharaoh game 1.0 is unplayable when set to fullscreen in winecfg. After loading screen and intro movie, you see black screen only, while music is still playing. It's a regression bug. With wine version 1.0rc3 this bug doesn't exist - the game is fully playable in fullscreen mode. After this I tested versions 1.1.3 - 1.1.7 and they all have this bug. Tested with clean .wine directory. Console output from running Pharaoh.exe is the same for all versions above, including 1.0rc3. Monitor resolution in fullscreen mode: 1280x1024.
http://bugs.winehq.org/show_bug.cgi?id=15881
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
--- Comment #1 from Austin English austinenglish@gmail.com 2008-11-02 16:52:00 --- Please run a regression test: http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=15881
FJA nobange@poczta.onet.pl changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |stefan@codeweavers.com
--- Comment #2 from FJA nobange@poczta.onet.pl 2008-11-04 15:06:06 --- (In reply to comment #1)
Please run a regression test: http://wiki.winehq.org/RegressionTesting
I did, it ends like this:
git bisect bad Bisecting: 0 revisions left to test after this [34b37fe2411d83f1a6f3e11a7a1e4d28bd9b36ba] d3d: Remove IWineD3DDevice::SetHwnd.
I'm not really sure if I did it right - is the output OK for identifying the bad patch? It's my first regression test. Added author of the patch to CC.
http://bugs.winehq.org/show_bug.cgi?id=15881
--- Comment #3 from James Hawkins truiken@gmail.com 2008-11-04 15:35:45 --- Please read the directions carefully:
"If you see:
Bisecting: 0 revisions left to test after this
THEN YOU ARE NOT DONE YET!"
http://bugs.winehq.org/show_bug.cgi?id=15881
--- Comment #4 from FJA nobange@poczta.onet.pl 2008-11-04 16:57:11 --- So, regarding to the directions, I posted it here and added the author of the patch to CC. What else should I do?
http://bugs.winehq.org/show_bug.cgi?id=15881
--- Comment #5 from Austin English austinenglish@gmail.com 2008-11-04 20:04:12 --- (In reply to comment #4)
So, regarding to the directions, I posted it here and added the author of the patch to CC. What else should I do?
You've got one more bisect to do. Rebuild, test, and input git bisect good/bad again to see the final result. See the Wiki.
http://bugs.winehq.org/show_bug.cgi?id=15881
--- Comment #6 from FJA nobange@poczta.onet.pl 2008-11-05 12:33:13 --- Oh now I see. This "0 revisions left" made me think it's the end of compiling. This is the result of last bisect:
34b37fe2411d83f1a6f3e11a7a1e4d28bd9b36ba is first bad commit commit 34b37fe2411d83f1a6f3e11a7a1e4d28bd9b36ba Author: Stefan Dösinger stefan@codeweavers.com Date: Tue Aug 5 14:24:10 2008 -0500
d3d: Remove IWineD3DDevice::SetHwnd.
:040000 040000 70726cbb30d4e915779d7f0897cd44227f549e3e afda0b9ddba310280afcbe82a78ae4e2212f1801 M dlls :040000 040000 405e4687c093ec5c082507ce0195a7958799b4bf fc8ba10a277dc8b364967673fb81eb08f0844897 M include
http://bugs.winehq.org/show_bug.cgi?id=15881
Marco Túlio monolitonegro@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |monolitonegro@gmail.com
--- Comment #7 from Marco Túlio monolitonegro@gmail.com 2009-04-17 14:23:55 --- It seems that as of wine version 1.1.19 this bug has been fixed. I tried to play in fullscreen and had no problem doing it. Could someone confirm it?
http://bugs.winehq.org/show_bug.cgi?id=15881
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #8 from Austin English austinenglish@gmail.com 2009-04-17 14:39:00 --- Reported fixed.
http://bugs.winehq.org/show_bug.cgi?id=15881
Marco Túlio monolitonegro@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|monolitonegro@gmail.com |
http://bugs.winehq.org/show_bug.cgi?id=15881
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #9 from Alexandre Julliard julliard@winehq.org 2009-04-24 12:18:41 --- Closing bugs fixed in 1.1.20.
http://bugs.winehq.org/show_bug.cgi?id=15881
Jörg Höhle hoehle@users.sourceforge.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hoehle@users.sourceforge.net
--- Comment #10 from Jörg Höhle hoehle@users.sourceforge.net 2009-04-27 07:42:30 --- I believe this issue was closed too early. The behaviour depends on several factors: - OS, - X screen size, - winecfg desktop window size, - Pharaoh's (or Cleopatra's) in-game resolution settings. Here are my findings.
Ubuntu Hardy generally works well. Trouble is with Ubuntu Intrepid. One may be tempted to dismiss this issue as invalid "Not Our Bug" on the basis that the apps work well with Ubuntu Hardy. But why do plenty of other wine apps manage to switch resolutions well with Intrepid? What does Pharaoh order wine to do to X differently?
The manual documents keys F5-F8 to switch resolutions. Works in Hardy, causes a black screen in Intrepid. IIRC cannot even switch back afterwards.
The following was observed recently with wine-1.1.19 on Intrepid:
With desktop 1024x768, Kleopatra's window remains black after the intro video, when the Kleopatra add-on image should display (assuming Pharaoh's own setting is 800x600).
When the virtual desktop's size matches Cleopatra's in-game settings (default is 800x600), there's no black screen after the intro video (Tested with both 800x600 and 1024x768 on Intrepid). The app works well then.
Similarly, when using $ xrandr -s <mode-number> prior to starting the app to match X and the game's resolutions in full screen mode, there's no black screen either.
Somewhere somebody mentioned a displacement between buttons and mouse position. I also observed this is desktop window mode, when the resolutions do not match, or I changed resolutions on the fly in wine-1.1.19 on Intrepid. The effect is that a) the picture is cut to a rectangular region smaller than the window size -- the right hand side control area may be entirely missing -- and b) the buttons and menus do highlight, but do so when the mouse is not above them, rather one inch away in the upper left direction -- as if using a shifted set of coordinates. Also, with Intrepid I once remember seeing Pharaoh's screen centered in the upper left corner.
I cannot yet comment on the regression the OP mentions. What OS was used anyway?
http://bugs.winehq.org/show_bug.cgi?id=15881
--- Comment #11 from Jörg Höhle hoehle@users.sourceforge.net 2009-04-30 04:20:25 --- I can now confirm that the regression identified by the OP in wine-1.1.3 d3d: Remove IWineD3DDevice::SetHwnd indeed breaks Pharaoh's (and Cleopatra's) full-screen behaviour in Ubuntu Intrepid.
The manual documents keys F5-F8 to switch resolutions.
Actually, F6-F10 cause changes.
http://www.sierrahelp.com/Misc/Demos.html lists http://www.sierrahelp.com/Files/Extras/Demos/PharaohDemo.zip (53MB) but I've not verified whether the demo is also affected.
Somebody please reopen this issue and add download link.
http://bugs.winehq.org/show_bug.cgi?id=15881
Marco Túlio monolitonegro@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |monolitonegro@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=15881
--- Comment #12 from Marco Túlio monolitonegro@gmail.com 2009-05-01 19:15:56 --- I've confirmed from Jörg Höhle instructions that the Pharaoh fullscreen bug is present at wine version 1.1.20. Although I managed to play Pharaoh in fullscreen with wine 1.1.19 without problems, i did it only at the in-game resolution of 800x600. Since when i've changed the in-game resolution to 1024x768, the game is no longer playable at fullscreen. My OS is GNU/Linux Ubuntu Hardy 8.04.
http://bugs.winehq.org/show_bug.cgi?id=15881
--- Comment #13 from Jörg Höhle hoehle@users.sourceforge.net 2009-05-19 06:13:37 --- I found a work-around: Press F6 when the screen is black. This works with both Pharaoh and Cleopatra in 1.1.21.
F6 is not documented in Pharaoh's manual, but it corresponds to the in-game menu -> options -> graphics -> "Fenster-Modus" (in German) / window mode. F7: 640x480 F8: 800x600 F9: 1024x768 F10: undocumented, causes a mini-icon to appear in the top left corner in desktop mode and the game pauses. Is this iconification?
Pressing F6 during game play produces a notice that switching to "Fenster-Modus" failed. The visual effect looks like F6 restores a sane screen after some failure to switch to another mode, that's why this trick works.
The F6 trick cures black screens in both full-screen and desktop mode in Kubuntu and Ubuntu Hardy for Pharaoh and Cleopatra. I wrote in comment #10 that Hardy worked fine for me, but todays testing with 1.1.21 showed some black screens when trying and switching among the 3 resolutions. The main difference was that Pharaoh typically starts with a correct screen, while Cleopatra typically starts black.
Black screens show up in both winecfg's full screen and desktop window mode.
http://bugs.winehq.org/show_bug.cgi?id=15881
--- Comment #14 from Jörg Höhle hoehle@users.sourceforge.net 2009-05-26 09:40:15 --- The downloadable PharaoDemo (URL in comment #11) also suffers from this bug. Somebody please reopen this issue and add the download link.
With wine-1.1.22 in Ubuntu Hardy, I installed the demo using an 800x600 virtual desktop, which got remembered in c:\windows\SIERRA.INI: [Config] ScreenWidth=800 ScreenHeight=600 Colors=16777216 WinVer=Windows NT Language=German
PharaohDemo starts fine in desktop window mode. - F6 says "Cannot set Windows mode", as in comment #13 - F7 (640x480) resizes but produces a black screen. - F8 returns to 800x600. - F9 resizes to 1024x768, opens a requester "confirm within 10 seconds or I'll restore". You seemingly cannot click the ok button, because you must click approx. 2 cm left above it. Once confirmed, Pharaohdemo will switch resolutions, but with black borders to the bottom and right, where all buttons are missing. Actually, Pharaoh "senses" the invisible buttons in the visible area (exactly where they were at 800x600), as that's where mouse tooltips appear.
So the symptoms are similar, albeit not identical to the full games (Pharao v1.2 and Cleopatra v2.1). Unlike the full versions, the demo cannot recover from a broken screen by pressing F6 in desktop window mode; yet this works in full-screen mode, where I can switch among the 3 resolutions.
Exiting the game (via the main menu, don't forget to click left above the actual buttons mid-screen) while at 1024x768 will allow you to restart in 1024x768 next time, this time without weird button offsets. From there, don't press F8+F9 or the borders reappear. Marco, could you please try this out?
Oddly, the demo produces no sound, although the archive contains sound files.
http://bugs.winehq.org/show_bug.cgi?id=15881
--- Comment #15 from Marco Túlio monolitonegro@gmail.com 2009-05-30 00:02:32 --- I've tested the game again with wine-1.1.22, and i've found similar problems. Playing the game outside virtual desktop leads to the following effects:
Pressing F7, F8, F9 switch to 640x480, 800x600, 1024x768 modes respective, but the screen goes black. Pressing F6 does not switch to windowed mode, but removes the black screen from switching modes. Thus, it's a workaround.
In virtual desktop 1024x768: Pressing F9 switch right into 1024x768 resolution, but pressing F7 and F8 turn the screen black, with no workaround.
In virtual desktop 800x600: Pressing F8 switch right into 800x600 resolution, pressing F7 turn the screen black with no workaround. Pressing F9 turn into 1024x768 resolution, but the button boxes collision are offseted from the real buttons.
In virtual desktop 640x480: Pressing F7 switch right into 640x480 resolution. Pressing F8 and F9 switch into 800x600 and 1024x768 respective, but the button's collision boxes are offseted from the real buttons.
In any size virtual desktop pressing F6 does nothing, but blink the screen.
http://bugs.winehq.org/show_bug.cgi?id=15881
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|FIXED |
--- Comment #16 from Austin English austinenglish@gmail.com 2009-06-23 11:34:02 --- Wasn't fixed, reopening.
http://bugs.winehq.org/show_bug.cgi?id=15881
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE
--- Comment #17 from Ken Sharp kennybobs@o2.co.uk 2009-10-05 09:44:43 --- Duplicate caused by commit 34b37fe2411d83f1a6f3e11a7a1e4d28bd9b36ba
*** This bug has been marked as a duplicate of bug 15000 ***
http://bugs.winehq.org/show_bug.cgi?id=15881
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #18 from Ken Sharp kennybobs@o2.co.uk 2009-10-05 09:44:58 --- Closing dup.
http://bugs.winehq.org/show_bug.cgi?id=15881
--- Comment #19 from Jörg Höhle hoehle@users.sourceforge.net 2010-06-04 04:11:19 --- Some admin please remove the "duplicate of bug #15000" marker. This was unfortunate because it removed attention from the present issue. We've seen the Fallout bug closed as fixed, reopened as bug #21426 and closed as fixed again. It doesn't seem any of the Fallout bug fixing has benefited Pharaoh or Cleopatra.
As of 1.2rc2, Pharaoh still exhibits the symptoms described in comment #13, comment #14 or comment #15, i.e. a black screen until pressing F6 once or twice.
In addition, Pharaoh now seems affected by bug #22948 like its predecessor, Caesar III. The symptoms are similar: during initialisation, a couple of background images used to be displayed, now the screen is black, except for the mid-screen rectangle with text. I've not tested whether the commit mentioned there causes that effect.
http://bugs.winehq.org/show_bug.cgi?id=15881
--- Comment #20 from Vitaliy Margolen vitaliy@kievinfo.com 2010-06-04 09:15:32 --- (In reply to comment #19) So why isn't it a duplicate of bug 22948?
http://bugs.winehq.org/show_bug.cgi?id=15881
--- Comment #21 from Jörg Höhle hoehle@users.sourceforge.net 2010-06-06 01:17:23 --- I claim that this is not a duplicate of bug #15000 because the commit that fixed Flatout for wine-1.1.35 and caused that other bug to be closed benefited neither Caesar 3, Pharaoh, Kleopatra nor Emperor.
I checked out that commit c24e48d937cfd0000a22af555a920ea7fab71d7b (cf. bug #21426, comment #7) but all symptoms mentioned in comment #10 etc. are still present.
- Black screen issues, depending on whether the app was started in a virtual desktop of 640x480, 800x600 or 1024x768 that matches what these apps last used.
- Mouse position displacement, present or not depending on resolution, as mentioned in comment #10 (I have sometimes observed this in PharaohDemo on a win95 machine as well).
- Mouse lag (seems to depend on resolution, but relation is unclear)
- Black bottom and right borders when switching to higher resolutions (using either the in-game menu or F8-F9).
Generally, it seems that wine explorer /desktop=Caesar3,640x480 c3.exe works best initially with Caesar 3 for the intro and menu, while 800x600 is the least problematic with Pharaoh.
Once the app is started correctly, switch to a higher resolution, exit and restart to use it, as mentioned in comment #14.
Starting Caesar3 in another resolution may lead to purple+green videos and screens, with videos shown shrinked to half their horizontal size, or no video shown at all. Please read bug #22948, comment #7 about how the 2 bugs differ (and what they have in common).
All in all, Caesar3, Pharaoh and Emperor behave very similarly, yet there are differences:
- Only Caesar 3: purple&greenish videos, main menu 1/2 or 1/4th their normal size (remembers me of Simcity 3000 trouble with 32bit bpp). Sometimes, using F6 after a black screen causes a window to be created, and the content appears twice, side by side, half its normal size in green and pink. - Only Emperor: borderless window amid the desktop instead of full screen.
They all worked much better in the past, e.g. 1.1.2.
-
wine-bugs＠winehq.org