| View previous topic :: View next topic |
| Author |
Message |
mr_clark
n00b
Joined: 13 Feb 2004
Posts: 14
|
 Posted: Fri Feb 13, 2004 11:41 pm Post subject: Full Screen Games with dual screen |
 |
|
I'm running an Nvidia Ti4200 video card with dual monitors. I've tried playing various games full screen and keep running into the same sort of problem. The latest one is the UT2004 demo.
If I run the game full screen then the game sits in the middle of the screen between the two monitors.
Its weird because some games (like Enemy Territory) automatically go full screen on my main screen without any problems.
I tried UT2004 in a window but the window doesn't seem to grab the mouse completely so if I go too far left, right, up or down then I can't turn anymore until I figure out where the mouse is off the screen and move it back to the game window.
Is there a way to get games to run full screen on one window instead of in the middle of the two? I'd like to at least get it working on UT2004 Demo.
Thanks in advance. |
|
| Back to top |
|
 |
trINItr0n_
n00b
Joined: 05 Feb 2004
Posts: 44
Location: Belgium::Leuven
|
| Posted: Tue Feb 17, 2004 10:42 am Post subject: |
|
|
I got exactely the same prob ... also my main screen on the left is an 19" lcd, while the other one is 21" crt, i'd prefer to game on the crt obviously ..
Right now i just switch between :
| Code: |
Option "TwinViewOrientation" "RightOf"
#Option "TwinViewOrientation" "Clone"
|
and restart X.
Any better solutions out there ?
Preferably with an option to full screen to the 2nd monitor ? |
|
| Back to top |
|
|
blueworm
l33t
Joined: 09 May 2003
Posts: 962
|
|
| Back to top |
|
|
Heewa
n00b
Joined: 28 Jan 2004
Posts: 8
Location: Rochester, NY, US
|
| Posted: Wed Feb 18, 2004 6:56 pm Post subject: |
|
|
| Use <ctrl>+g to have the window "grab" the mouse in windowed mode. The mouse will no longer go outside the window. This works in UT, also. |
|
| Back to top |
|
|
r00d00
n00b
Joined: 13 Feb 2004
Posts: 56
|
| Posted: Wed Feb 18, 2004 7:30 pm Post subject: |
|
|
| Cntrl g - doesn't seem to work for me? What window manger do you use or are there other settings to create this? |
|
| Back to top |
|
|
trINItr0n_
n00b
Joined: 05 Feb 2004
Posts: 44
Location: Belgium::Leuven
|
| Posted: Wed Feb 18, 2004 11:32 pm Post subject: |
|
|
works for me with kde ... tnx btw, blueworm  |
|
| Back to top |
|
|
Heewa
n00b
Joined: 28 Jan 2004
Posts: 8
Location: Rochester, NY, US
|
| Posted: Thu Feb 19, 2004 4:36 pm Post subject: |
|
|
| I use Gnome 2.4, not sure if that has anything to do with it, though. By the way, I have an NVidia card, and when I go fullscreen, it just chooses the first monitor. Are you using TwinView? What's your XF86Config look like? (/etc/X11/XF86Config) |
|
| Back to top |
|
|
tsigo
Tux's lil' helper
Joined: 09 Jul 2002
Posts: 122
|
| Posted: Thu Mar 04, 2004 10:19 pm Post subject: |
|
|
| Heewa wrote: | | Use <ctrl>+g to have the window "grab" the mouse in windowed mode. The mouse will no longer go outside the window. This works in UT, also. |
Exactly the answer I came looking for. Worked perfectly, thanks. |
|
| Back to top |
|
|
SpitBubbleBoy
n00b
Joined: 14 Feb 2004
Posts: 4
|
| Posted: Fri Mar 05, 2004 1:48 am Post subject: |
|
|
You need to set you metamodes in the XF86Config to something like
1600x1200,NULL. You basically are turning off the other head on the card when you enter a game.
In theory you could play at 3200x1200, but I have not tried anything like that.
Of course, you might want all the metamodes to be there for so you can switch resolutions.
Mine is this:
| Code: |
Option "TwinViewOrientation" "RightOf" # <str>
Option "SecondMonitorHorizSync" "30-86" # <str>
Option "SecondMonitorVertRefresh" "50-120" # <str>
Option "MetaModes" "1600x1200,1600x1200; 1600x1200,NULL; 1280x1024,1280x1024; 1280x1024,NULL; 1024x768,1024x768; 1024x768,NULL" # <str>
|
From nvidia's readme:
| Quote: |
Option "MetaModes" "string"
This option describes the combination of modes to use
on each monitor when using TwinView. Please see APPENDIX
I for details. Default: string is NULL.
|
| Quote: | MetaModes
A single MetaMode describes what mode should be used on each
display device at a given time. Multiple MetaModes list the
combinations of modes and the sequence in which they should be
used. When the NVIDIA driver tells X what modes are available,
it is really the minimal bounding box of the MetaMode that is
communicated to X, while the "per display device" mode is kept
internal to the NVIDIA driver. In MetaMode syntax, modes within
a MetaMode are comma separated, and multiple MetaModes are
separated by semicolons. For example:
"<mode name 0>, <mode name 1>; <mode name 2>, <mode name 3>"
Where <mode name 0> is the name of the mode to be used on display
device 0 concurrently with <mode name 1> used on display device 1.
A mode switch will then cause <mode name 2> to be used on display
device 0 and <mode name 3> to be used on display device 1. Here
is a real MetaMode entry from the XF86Config sample config file:
Option "MetaModes" "1280x1024,1280x1024; 1024x768,1024x768"
If you want a display device to not be active for a certain
MetaMode, you can use the mode name "NULL", or simply omit the
mode name entirely:
"1600x1200, NULL; NULL, 1024x768"
or
"1600x1200; , 1024x768"
Optionally, mode names can be followed by offset information
to control the positioning of the display devices within the
virtual screen space; e.g.:
"1600x1200 +0+0, 1024x768 +1600+0; ..."
Offset descriptions follow the conventions used in the X
"-geometry" command line option; i.e. both positive and negative
offsets are valid, though negative offsets are only allowed when
a virtual screen size is explicitly given in the XF86Config file.
When no offsets are given for a MetaMode, the offsets will be
computed following the value of the TwinViewOrientation option
(see below). Note that if offsets are given for any one of the
modes in a single MetaMode, then offsets will be expected for
all modes within that single MetaMode; in such a case offsets
will be assumed to be +0+0 when not given.
When not explicitly given, the virtual screen size will be
computed as the the bounding box of all MetaMode bounding boxes.
MetaModes with a bounding box larger than an explicitly given
virtual screen size will be discarded.
A MetaMode string can be further modified with a "Panning Domain"
specification; eg:
"1024x768 @1600x1200, 800x600 @1600x1200"
A panning domain is the area in which a display device's viewport
will be panned to follow the mouse. Panning actually happens on
two levels with TwinView: first, an individual display device's
viewport will be panned within its panning domain, as long as
the viewport is contained by the bounding box of the MetaMode.
Once the mouse leaves the bounding box of the MetaMode, the entire
MetaMode (ie all display devices) will be panned to follow the
mouse within the virtual screen. Note that individual display
devices' panning domains default to being clamped to the position
of the display devices' viewports, thus the default behavior is
just that viewports remain "locked" together and only perform
the second type of panning.
The most beneficial use of panning domains is probably to
eliminate dead areas -- regions of the virtual screen that are
inaccessible due to display devices with different resolutions.
For example:
"1600x1200, 1024x768"
produces an inaccessible region below the 1024x768
display. Specifying a panning domain for the second display
device:
"1600x1200, 1024x768 @1024x1200"
provides access to that dead area by allowing you to pan the
1024x768 viewport up and down in the 1024x1200 panning domain.
Offsets can be used in conjunction with panning domains to
position the panning domains in the virtual screen space (note
that the offset describes the panning domain, and only affects
the viewport in that the viewport must be contained within the
panning domain). For example, the following describes two modes,
each with a panning domain width of 1900 pixels, and the second
display is positioned below the first:
"1600x1200 @1900x1200 +0+0, 1024x768 @1900x768 +0+1200"
If no MetaMode string is specified, then the X driver uses the
modes listed in the relevant "Display" subsection, attempting
to place matching modes on each display device. |
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Gamers & Players
