http://bugs.winehq.org/show_bug.cgi?id=22948
Jörg Höhle hoehle@users.sourceforge.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hoehle@users.sourceforge.ne | |t
--- Comment #7 from Jörg Höhle hoehle@users.sourceforge.net 2010-06-06 01:17:39 --- Can you please elaborate on the specific effects of this commit, in light of the background information given in bug #15881, comment #14 ?
Here's how I managed to use Casear 3 with wine-1.2rc2. 1. wine explorer /desktop=Caesar,640x480 Watch the still images and intro video, everything seems perfect. Start a game, select 1024x768 resolution. Black borders at the bottom and right, mouse displacement. Hit Esc to exit the game 2. wine explorer /desktop=Caesar,1024x768 Now the videos manages to display in this virtual desktop (even though it's a small 500x300 animation surrounded by huge black borders, but it's rendered correctly). Play, the screen now displays correctly at 1024x768. Everything works well except from the "button visual feedback lag when hovering" effect.
As I explained in bug #15881, the key is the correspondence between Wine's initial resolution and the default or previous setting from the game.
Alas, depending on your monitor's resolution, this means you cannot play Caesar3 in full screen (i.e. without virtual desktop) like you could with older versions of Wine. Fullscreen now works only if you use xrandr -s <N> to switch resolutions to Caesar's last used one before you start it.
Once you've got this working setup, don't switch resolutions in the game, or you'll again get a black screen. F6 does not help to recover from it as it used to do. Curiously, the "exit Imperium?" requester that appears if you press Esc is rendered normally.
Wine-1.1.16 behaves a little better than wine-1.2rc2: + It manages to work with fullscreen mode even though the monitor's resolution is >1024x768 . When started using wine explorer /desktop=640x480 c3.exe /cd=D:\ it will resize its window to its last saved (or default) value. + No mouse lag (at 102x768). - Unability to switch resolutions correctly afffects both, and - mouse vs. a button's visual feedback displacement.