Forums » Linux
Dual Screen Resolution Choices
I know this is in part Xorg causing issues. But When I have both monitors plugged in I get Resolution choices like
"3840x1080" "1920x1080" and others that are non-native resolutions.
With just my primary monitor I get
"1920x1200" "1920x1080" and others that are non-native
I would like to see, with both monitors plugged in, "1920x1200" that allows me to "blank" or turn off my external monitor and play VO in full screen on my primary monitor.
Like I said I'm sure it's xorg in part or Nvidia twin view in part, but there has got to be a fix somewhere.
Xrandr is putting out the correct blarbs
Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 8192 x 8192
LVDS-0 connected 1920x1200+1920+0 (normal left inverted right x axis y axis) 367mm x 230mm
1920x1200 60.0*+
DP-0 connected 1920x1080+0+44 (normal left inverted right x axis y axis) 509mm x 286mm
1920x1080 60.0*+ 59.9 50.0 30.0 30.0 25.0
1280x1024 75.0 60.0
1280x720 60.0 59.9 50.0
1152x864 75.0
1024x768 75.0 60.0
800x600 75.0 60.3
720x576 50.0 25.0
720x480 59.9 30.0
640x480 75.0 59.9 59.9
DP-1 disconnected (normal left inverted right x axis y axis)
"3840x1080" "1920x1080" and others that are non-native resolutions.
With just my primary monitor I get
"1920x1200" "1920x1080" and others that are non-native
I would like to see, with both monitors plugged in, "1920x1200" that allows me to "blank" or turn off my external monitor and play VO in full screen on my primary monitor.
Like I said I'm sure it's xorg in part or Nvidia twin view in part, but there has got to be a fix somewhere.
Xrandr is putting out the correct blarbs
Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 8192 x 8192
LVDS-0 connected 1920x1200+1920+0 (normal left inverted right x axis y axis) 367mm x 230mm
1920x1200 60.0*+
DP-0 connected 1920x1080+0+44 (normal left inverted right x axis y axis) 509mm x 286mm
1920x1080 60.0*+ 59.9 50.0 30.0 30.0 25.0
1280x1024 75.0 60.0
1280x720 60.0 59.9 50.0
1152x864 75.0
1024x768 75.0 60.0
800x600 75.0 60.3
720x576 50.0 25.0
720x480 59.9 30.0
640x480 75.0 59.9 59.9
DP-1 disconnected (normal left inverted right x axis y axis)
That's TwinView doing that. Though I have noticed Vendetta doesn't list all of the modes for all of your monitors when you have a two-headed XRandR setup.
You probably want this. Another option is to add custom modelines using xrandr or your xorg.conf.
The game is going to look pretty silly sliced down the middle with dual screens. I'd connect a third one. :)
You probably want this. Another option is to add custom modelines using xrandr or your xorg.conf.
The game is going to look pretty silly sliced down the middle with dual screens. I'd connect a third one. :)
Good try, but it didn't work.
VO seems to list all the modes for DP-0 but not the one mode from LVDS-0 Though it works quite well with the second monitor disconnected. I think it's a polling issue (only looking at the last monitor). Rather is VO, xrandr, twinview, or space elephants I can not say.
VO seems to list all the modes for DP-0 but not the one mode from LVDS-0 Though it works quite well with the second monitor disconnected. I think it's a polling issue (only looking at the last monitor). Rather is VO, xrandr, twinview, or space elephants I can not say.
If it didn't work, you did it wrong. I use the xf86vidmode=0 and xsize/ysize every time I play on my desktop at home to get the weird 1400x1024 "fullscreen plus statusbar" window size.
Make sure to check the whole config file for extra xf86vidmode=1. I've noticed the darn game likes to put it in there multiple times...
Make sure to check the whole config file for extra xf86vidmode=1. I've noticed the darn game likes to put it in there multiple times...
"If it didn't work, you did it wrong. I use the xf86vidmode=0 and xsize/ysize every time I play on my desktop at home to get the weird 1400x1024 "fullscreen plus statusbar" window size."
It stuck it in a window instead of full screen. The window was the correct size, but it was still a window. Borderless, annoying, and with reduced performance (though that's likely the compositor cause it's not actually full screen). It also did not disable the other monitor. And because it's an annoying borderless window, the window manager gets all finicky
Yes I noticed about 4 of the "extra xf86vidmode=1"
It stuck it in a window instead of full screen. The window was the correct size, but it was still a window. Borderless, annoying, and with reduced performance (though that's likely the compositor cause it's not actually full screen). It also did not disable the other monitor. And because it's an annoying borderless window, the window manager gets all finicky
Yes I noticed about 4 of the "extra xf86vidmode=1"
The borderless window is likely the cause of "fullscreen plus statusbar"
Wait, you *want* it to turn off your 2nd monitor? Mac users have been complaining about that for ages...
Why not just put a wrapper script around vendetta and disable that output with xrandr when you start the game?
Also, fullscreen in X11 isn't really "fullscreen" everything is still a window and your compositor is still going to cause problems. There's a reason the guys who worked on Xorg have been building Wayland...
Why not just put a wrapper script around vendetta and disable that output with xrandr when you start the game?
Also, fullscreen in X11 isn't really "fullscreen" everything is still a window and your compositor is still going to cause problems. There's a reason the guys who worked on Xorg have been building Wayland...
Personally, I just run VO in windowed mode set to the size of my screen, and then have my windowmanager itself fullscreen it (Alt-F11 in IceWM).
That does leave my other monitor active, but I want it active. Otherwise why have it? I could just turn it off if I wanted it black. I usually leave IRC up in that window, since the game eats chat messages while warping, and sometimes it's just easier to read things in the IRC window, since it doesn't get cluttered up with other information, and can be sized to display a longer history. Sometimes I have my browser running over there too, if I'm looking stuff up on the wiki or whatever.
The only reason I can think of to not have the monitor running is if I'm in a dark room and don't want it glaring at me. Or, I guess, if I mistook a Dorito for a graphics card. But I'm a Sun Chip man myself, so I never have that particular problem.
Anyway. Another option besides using xrandr to turn off your other screen would be to make a wrapper script that actually runs Vendetta in a completely separate instance of Xorg with its own settings. For example, I believe you could set up an extra xorg.conf file named /etc/X11/xorg.conf.vendetta which doesn't enable TwinView, and then run the following script:
#!/bin/sh
export DISPLAY=:1.0
export XORGCONFIG=xorg.conf.vendetta
xinit $HOME/bin/vendetta -- :1
I haven't tested that specifically, but I have used something similar (minus the custom xorg.conf) to launch certain games. You'll end up with the new session of X running in a different virtual terminal, so you can switch back and forth with the normal Ctrl-Alt-F# combo (or Alt-F#, if you miss and reach a commandline).
That does leave my other monitor active, but I want it active. Otherwise why have it? I could just turn it off if I wanted it black. I usually leave IRC up in that window, since the game eats chat messages while warping, and sometimes it's just easier to read things in the IRC window, since it doesn't get cluttered up with other information, and can be sized to display a longer history. Sometimes I have my browser running over there too, if I'm looking stuff up on the wiki or whatever.
The only reason I can think of to not have the monitor running is if I'm in a dark room and don't want it glaring at me. Or, I guess, if I mistook a Dorito for a graphics card. But I'm a Sun Chip man myself, so I never have that particular problem.
Anyway. Another option besides using xrandr to turn off your other screen would be to make a wrapper script that actually runs Vendetta in a completely separate instance of Xorg with its own settings. For example, I believe you could set up an extra xorg.conf file named /etc/X11/xorg.conf.vendetta which doesn't enable TwinView, and then run the following script:
#!/bin/sh
export DISPLAY=:1.0
export XORGCONFIG=xorg.conf.vendetta
xinit $HOME/bin/vendetta -- :1
I haven't tested that specifically, but I have used something similar (minus the custom xorg.conf) to launch certain games. You'll end up with the new session of X running in a different virtual terminal, so you can switch back and forth with the normal Ctrl-Alt-F# combo (or Alt-F#, if you miss and reach a commandline).
It might be a bug that the game doesn't check XRandR for resolutions of the monitor that it's being displayed on, and not offering them in the list, ok. This may be more the fault of XRandR and the API than the game, since it was originally designed with a rather short-sighted set of goals. (laptop/tablet rotate and *simple* dualscreen configurations)
I don't think it's Vendetta's responsibility to turn off your other monitors when it goes into fullscreen mode though. That's the window manager's job and I'm kind of *glad* it doesn't do this for the same reasons Pizzasgood just mentioned. My other two displays have IRC and a music player up most of the time.
I don't think it's Vendetta's responsibility to turn off your other monitors when it goes into fullscreen mode though. That's the window manager's job and I'm kind of *glad* it doesn't do this for the same reasons Pizzasgood just mentioned. My other two displays have IRC and a music player up most of the time.
@turning off second monitor stuffs.
It's more of a long term bug report. Like I said it could totally be (and likely is) something totally out side VO at this point. Specially if their using the "older" methods of detecting screen resolutions.
You are correct on both accounts a xrandr wrapper script would be quite simple, however VO still detects the wrong resolutions and just turns the other monitor back on.
As for window v.s. full screen, your right that a window app shouldn't touch full screen apps, and neither should the full screen app. But when xrandr gets a call to "set resolution to size of display 0.0 then it turns off 0.1. VO never sends the right resolutions to let that happen.
Finally, also in the land of Full screen and windows (and take with a grain of salt cause I refuse to use it), if a window is not truly full screen with the proper flags then the compositor doesn't know to un-redirect it. Meaning those that use compiz (again not me, so ...) get a completely horrid frame rate among other problems.
For now, I am perfectly happy unplugging my second monitor. Playing, and plugging it back in when done. It's not that hard for me, but I'm on a laptop.
Also I totally realize that second monitor is something that people use very differently. For me it's only purpose is to run compile tasks in the background while I am writing code so I can see test results etc. Other then that I never use it. But that's not a normal use.
It's more of a long term bug report. Like I said it could totally be (and likely is) something totally out side VO at this point. Specially if their using the "older" methods of detecting screen resolutions.
You are correct on both accounts a xrandr wrapper script would be quite simple, however VO still detects the wrong resolutions and just turns the other monitor back on.
As for window v.s. full screen, your right that a window app shouldn't touch full screen apps, and neither should the full screen app. But when xrandr gets a call to "set resolution to size of display 0.0 then it turns off 0.1. VO never sends the right resolutions to let that happen.
Finally, also in the land of Full screen and windows (and take with a grain of salt cause I refuse to use it), if a window is not truly full screen with the proper flags then the compositor doesn't know to un-redirect it. Meaning those that use compiz (again not me, so ...) get a completely horrid frame rate among other problems.
For now, I am perfectly happy unplugging my second monitor. Playing, and plugging it back in when done. It's not that hard for me, but I'm on a laptop.
Also I totally realize that second monitor is something that people use very differently. For me it's only purpose is to run compile tasks in the background while I am writing code so I can see test results etc. Other then that I never use it. But that's not a normal use.
The video mode problem becomes a bigger issue if you want to play the game ON the external monitor but it only shows the modes for your laptop display. Just unplugging it isn't an option in that case.
I'm running openSUSE 12.3 right now, as per ARF above and don't have a issue. (see below). Specs on laptop are a Intel I-5, HD3000.
Via the video settings I just turned off the laptop display and put it on my external monitor, which has a native display of 1920x1080. (vs the native res of 1366x780). VO is set to run in windowed mode at 1024x900 or something... he is correct though on that if the laptop display is enabled VO insists on using that display. (so, just a option for some).
Via the video settings I just turned off the laptop display and put it on my external monitor, which has a native display of 1920x1080. (vs the native res of 1366x780). VO is set to run in windowed mode at 1024x900 or something... he is correct though on that if the laptop display is enabled VO insists on using that display. (so, just a option for some).
@abortretryfail - yes that is the larger issue of the bug report. If your not going to show all the resolutions then you can't go the other way (displaying on an external while not using an internal)
@vskye - disabling your internal display is not having a dual screen. You only have one screen. Thus are not effected by the problem. You are also plaing in a window and are not effected by the problem. Try Having both monitors on, and in use then starting VO with only one of them fullscreen. Issues ensue.
@vskye - disabling your internal display is not having a dual screen. You only have one screen. Thus are not effected by the problem. You are also plaing in a window and are not effected by the problem. Try Having both monitors on, and in use then starting VO with only one of them fullscreen. Issues ensue.
Playing in a window is affected by this too.
The resolution choices you're given for windowed play are the same as the ones for fullscreen unless you use the override hack linked earlier. Why? I have no idea. Some other games just let you resize the window and play in whatever size view you want.
The resolution choices you're given for windowed play are the same as the ones for fullscreen unless you use the override hack linked earlier. Why? I have no idea. Some other games just let you resize the window and play in whatever size view you want.