I will try out with Diablo 2 ASAP and report back. one plays with onboard sound via speakers and one via usb sound card plus headset) Using a second soundcard dedicated for the second gamer (e.g. IMO this would mean less issues with fullscreen and so on. This way every "gamer session" would be limited to a certain screen. I think a good starting point for a guide would be a new entry in the wiki (for example referenced by the Xorg entry). Thanks for posting those instructions and the reference in the other thread. Maybe a wiki page would be a good idea? I think it would also be easier to join efforts there. Now I'm looking for suggestions where I could place them. Xinput reattach "$KEYBOARD" "$MASTER_NAME keyboard"ĭon't ask me for more detailed instructions - I'll provide them when I have time. Xinput reattach "$POINTER" "$MASTER_NAME pointer" KEYBOARD="$( IFS=$'\t' zenity -title="Select device" -list -text="Choose a keyboard" -column="Id" -column="Name" )" POINTER="$( IFS=$'\t' zenity -title="Select device" -list -text="Choose a pointer" -column="Id" -column="Name" )" IFS=$'\n' DEVICE_LIST=( $(xinput list -short) ) Here's one that lets you choose a mouse and keyobard and assign a second pointer to them (uses zenity, but can be adapted to use CLI only): As you can see, it requires some tedious typing each time, so right now I'm writing scripts that automate the setup. You'll have to repeat all steps (except the first one) each time you want to play in this configuration. Use xinput with "set-cp" option to assign a second pointer to the window that will be operated by it Launch two instances of some game, one on each screen Set up a secondary pointer with xinput utility Start another X server with "xinit /usr/bin/xterm - :1 vt8 -config " (so that when something goes bad, your main desktop won't suffer) Prepare an alternative xorg configuration file for both displays (if you don't use both already) Also, sometimes keyboard focus is not automatically assigned for the second pointer, and you have to explicitly assign it via command-line for the keyobard input to work. Thankfully, it doesn't have to be explicitly supported by a WM in order to be used with it, but most WMs tend to get confused by it. The multi-pointer feature of Xorg is still fairly new, and is not supported by any window manager that I know. Besides, it's much less painful to set up. Mutli-pointer approach lets you use both screens with hardware acceleration with just one dual-head graphics card (like most laptops have). Often it won't let you use hardware acceleration on both displays unless they're connected to two separate video cards. What makes this approach better than a "true" multiseat:Ĭonfiguring a proper multiseat system (where each "seat" get's it's own login screen) is not easy, to start with. Now, run some game on first screen, then another instance on another, and you can play it multiplayer with your friend Now, if you connect a second physical display and configure it to be a separate X screen belonging to the same X server, you can send your second pointer to that screen, virtually allowing both sets to be used independently. Plug another keyboard, assign it to this pointer, and you can independently work with two windows at a time (each pointer getting it's own focus). In recent versions of Xorg (>= 1.7), there's a nice feature - it lets you plug another mouse and make it control a second pointer on the screen. It really works - I use it to play Myth II: Soulblighter (on Wine) with my brother Recently I've discovered a decent way to play multiplayer games in multiseat (or pseudo split-screen) manner.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |