Currently it seems that's just a stupid dual-monitor twinview
problem.
http://forum.winehq.org/viewtopic.php?p=40647&sid=358e192a75c3b8b076aeb496c5a90dac
The same problem applied to a user with Halflife:
http://www.codeweavers.com/compatibility/browse/name/?app_id=3;tips=1
I'm trying to find the correct "working" NVidia Twinview Xinerama
settings tipp within the next days.
Do you know if there is such "global" tipps area where it can be
posted to? Is there a global FAQ?
Right - when I saw your previous post and saw the resolution quoted, I figured you
either had a very interesting monitor, or you had a dual-head setup -- it wasn't
immediately obvious =) The issues with Wine and dual monitors has been known for some
time, and as I understand it, this is more mooted in the way the xserver/video drivers
present the situation (to the app), compared to how the win32 counterparts do the same
thing. Even putting wine/crossover aside for a moment, dual-head setups in linux can
be fickle even with native apps.....
....what {ahem} 'should' work, would be a scenario of say two, 1650x1080 displays, which would appear
as the composite $display area of 3300x1080 and would be addressed as localhost:0 , the left display
as localhost:0.0 and the right display as localhost:0.1 ...but it doesn't work that way. It might not
even be what you want to do, it's just an example. If one wanted to span -both- displays with the app's
video output, then you're still limited to whatever maximum resolution the win32 app is going to support.
If, say, that resolution was 1920x1080 maximum, the 'proper' way to display that on the composite desktop,
would be with the 1920x1080 viewport centered on the two display areas, with a 690pixel wide black bar
to the left/right of that. If you did that, then you have to calculate mouse coordinates and so forth,
from a 0,0 position that appears at 690 of the overall display size, and things get uglier from here on in...
Like I say though, it depends on exactly what you're trying to do. What one would -like- to have happen,
is if the app's max resolution was 1920x1080, being able to present that as 2 viewports each of 960x1080
in size might work (supposing the display handled whatever modeline that calculates out to)..ie; you change
the maximum $display size presented by the 2 monitors. This has problems as well...
From what I've read about the place, the maximum resolution Greed Corp supports (I have it as well), is
1920x1080 with all 16:9/10 & 4:3 aspect resolutions under that catered for. I suspect if you enable the
'emulate a virtual desktop' feature and set desktop size to 1920x1080, it might pop to fullscreen then.
It might not be what you want, but, it would example the behavior. (if that didn't work, it might be due
to the refresh-rate set in registry for the emulated desktop window). I used to have twinview setup here,
emulated virtual desktop was the only way out most times - I don't use it anymore =)
It really depends on the app tho' ...ie; if Greed Corp supported 3300x1080 in the example above, it'd likely
all work fine, but as that isn't the case, one wishes you could command the GPU on the video card to just
retarget the graphics steams for you <grin>...
Cheers!
ps: there is a General forum area, but, this is as good a place as any for twinview stuffs ...