Better use version 1.2 of wineskin then the newer version 2.0 is a bit buggy still, but Doh123 is working hard on it. Waiting is on Xquartz 2.6.0
waiting is partially on RandR getting finished in Xquartz 2.6.0. If I get to it, I'll finish it up myself and get a working version, wether my patches are accepted into Xquartz main or not.... but I don't think I can get to it anytime soon. I've been busy and haven't worked on it in awhile, but I have been learning ObjC/Cocoa and trying to recode all of 2.0 using that. The latest Wineskin Winery beta is in ObjC, but the Wineskin.app in the wrapper is still Java.... I have an ObjC/cocoa version I'm still working on to replace that, but its only about 75% done.
I gave up on it already.
In Fallout the mouse movement is extremely sporadic and irritating. Can't stand to play it. It is a known bug with this game and Wine dating at least 4 years back and still hasn't been fixed (
http://bugs.winehq.org/show_bug.cgi?id=6033)
on top of that whenever I exit a game I have to cmd+Q or else it gets stuck in a black screen with a cross for a pointer. And even after that if I want to relaunch the game I have to quit all Wine related processes. Just too buggy and incompatible for someone like me who only games in 5-15 minute sessions. Guess I have to go with Virtualbox or Boot Camp
Edit: Seems to also be an issue in Windows! Just installed Windows 7 x64 (in VMWare Fusion 3), mouse is still choppy. Not AS bad as with Wineskin here, a little more accurate, but still choppy.
I'll try PlayOnMac tonight and update this post
its a game by game basis, and I've designed Wineskin to be more of a porting tool to be used by people who port a lot, not just a casual user. This is mainly because its very hard to get games working right in Wine. You may want to look at the forums at portingteam.com and see if someone already has working wrappers using Wineskin or Cider or CXZ/S, which you can use. Once someone get it working they should be able to share wrappers around pretty easy.
I have had a few people complain about programs not quitting right in Wineskin using Wine versions 1.3+ but I haven't been able to reproduce it yet so I haven't narrowed down why this is happening for some people. As a minor work around, in case i do not find it anytime soon, I have stuck on my list to add in that if the X server is killed (CMD+Q or however) that it should kill off its wineserver on its own and do a normal shut down... which would at least let people hit CMD+Q and have it exit properly if its stuck on a black screen.
There are some ways to fix mouse issues on certain games, but they take Wine patches, which means you have to custom compile your own WineskinEngine.bundle ... thats one major point to Wineskin over WineBottler (and one of the major reasons I started Wineskin) is that anyone should be able to take and modify some Wine source code and use it easily with a Wineskin wrapper. Another thing i wanted was a built in X11, not just using X11.app on the system... so thats its cutting edge in support and performance, and the same exact version built in across 10.5 and 10.6.
2.0 beta is still buggy, and 1.2 less buggy overall... 1.2 still has some limitations that 2.0 beta doesn't have.
Other than that I don't know a lot about current WineBottler, as I stopped using it any about a year ago when i started Wineskin... but I used to use Mike's Darwine builds a lot before he started WineBottler back before I got into how the heck to do any of this stuff myself... and have been making it up as I went along ever sense.
I also love input and suggestions on Wineskin if anyone thinks things need to be changed or added.
I'm hoping to have all beta stuff updated with everything currently on my "working on" list within 2 weeks... besides RandR in Xquartz being totally done.
current Wineskin 2.0 Beta thread at portingteam.com
