The forum

Great job so far... the two games I play most run very well on my Mac now!

I have a question, however: Is there a way to configure the wine engine to only do full-screen on ONE of my dual monitors? Currently, when I launch Fallout: New Vegas, Black Ops, or any Steam games, I get full-screen, but it's spread across both monitors... it's difficult, because my aiming reticle is centered between the two monitors so it makes targeting difficult.

Any suggestions?

Cheers!

Try this :

Right click on your software -> configure this application -> Display

And let the window manager to control wine windows.

The Apple X11 Windows manager (quartz-vm) is quite buggy, so it might cause problems ... Let me know if it works

Thanks for the suggestion, however, it didn't help. Steam based games still show up on both monitors and in-game settings only give me the option to select the resolution for the entire desktop (both monitors).

In Fallout: New Vegas (installed directly from DVD), it used to play on both monitors, but after changing the wine config to your suggestion, I get this error now: "Failed to initialize renderer. Your display doesn't support the selected resolution in Fallout: New Vegas's Launcher under 'Display Settings'." However, in-game settings now don't have ANY resolutions in the drop-down list of available resolutions (i.e., the combo is completely empty). I'm going to remove the entire config and try re-installing FNV from DVD again, selecting the resolution of my primary monitor, then trying your suggestion again. I'll report back when I have results.

Sorry I didn't get the chance to post back quicker, kids happen. ;)

I'm not sure what I've borked, but I did a full "remove" of FNV (even ensured the prefix folder was removed from hard disk) but when re-installing FNV from disk, I once again get a completely empty screen resolution combo box on the in-game video settings page (regardless of if 4:5, 16:9, or 16:10 is selected). Video card is detected correctly.

My next step is to disable (or unplug) one of the monitors, restart OS-X so it only sees a single monitor, then play that way. It'll be a minor inconvenience compared to buying a new windows machine just to play a few games... at least until a dual-monitor workaround is realized.

ok, I've made two steps forward and a huge step back: I was playing around and installed the "XQuartz patches - prevent fullscreen" fix and in conjunction with the "allow Windows manager to control wine windows" FNV now runs in a window on my primary monitor. That is the "two steps forward"... the "huge step back" is now I get to the main FNV menu and start a new game/character, watch the initial cut-scene movie, then the entire machine's GUI locks up (when you would normally wake up in the doctor's house in the game)... the mouse is still responsive, but you can't do anything but move the mouse around. I have to ssh to the machine from another machine and sudo-reboot it to get ANY GUI to work again.

Looks like I may be running into the issue described in this post on POL: http://www.playonmac.com/en/topic-4017-Digital_Version_Executable.html (only I'm installing from DVD). Going to try an install some of the other fixes (.net 3.5, etc.) and see if any resolve it.

The problem you described is very strange.

You can edit $HOME/Library/PlayOnMac/configurations/installed/Your game

remove the line export WINEDEBUG="-all"

and add "> $HOME/Desktop/log.txt" at the end of the line starting by wine

You'll have a logfile of the crash. Maybe it could help

I think you don't need to reboot. Just try these commands :

killall wine -KILL
killall wineserver -KILL
killall x -KILL
killall x11.bin -KILL
killall xquartz -KILL

I've already tried the killall route... it doesn't free-up the GUI at all; I believe it's something in Xquartz that's messing up the "real" Mac OS GUI; as I mentioned, the mouse moves around but absolutely NOTHING responds to any events that only a full reboot resolves; I've even tried forcefully logging off the user from a remote desktop/screen sharing session... nothing seems to "unlock" the frozen screen but a reboot.

I've also tried what you suggested about editing the game script and I get a zero byte log.txt in my $HOME/Desktop folder. I assume simply commenting out the "export WINEDEBUG='-all'" line should suffice? As in: #export WINEDEBUG="-all"

Cheers!

Weird... It must be a bug coming from XQuartz

And yep, it's sufficient :-)