Hi-Res Patch 3.06 - allows for playing the game at resolutions above the original 640 x 480, including widescreen resolutions. A warning - bumping the color resolution to 16/32-bit resulted in massive slowdowns for me.

Hi-Res Patch 3.06 - allows for playing the game at resolutions above the original 640 x 480, including widescreen resolutions. A warning - bumping the color resolution to 16/32-bit resulted in massive slowdowns for me.

How do you install the hi-res patch? I'm using CG 10.1.2 and Fallout from GOG was easy to install and runs flawlessly but it's in a tiny 640x480 window. I'd like it to run in a larger window, which I'm assuming the hi-res patch would allow, but I can't seem to do anything with the hi-res executable in CG 10.1.2 or WINE. Any suggestions?

How do you install the hi-res patch? I'm using CG 10.1.2 and Fallout from GOG was easy to install and runs flawlessly but it's in a tiny 640x480 window. I'd like it to run in a larger window, which I'm assuming the hi-res patch would allow, but I can't seem to do anything with the hi-res executable in CG 10.1.2 or WINE. Any suggestions?

-PN

P.S In fullscreen mode in CG 10.1.2 Fallout runs like a dog.

The hi-res patch I linked to comes in a .zip file which you have to expand in your Fallout install folder (whether it be in CrossOver or Wineskin). There are some detailed instructions in the included readme file too - the only other thing is that the patch needs the Visual C++ 6.0 runtime, which you can install either in Winetricks within Wineskin or via the Software Installer in CrossOver. Remember to install it in the same bottle as Fallout or else the patch won't work.

Oh yes, and you shouldn't try to run either Fallout or Fallout 2 in any version of CrossOver earlier than CrossOver 11. In every other previous release I tried, they were unplayable due to slow performance.

Bump. It pains me to say this, but (after some more testing) performance appears to still be almost unplayably sluggish in CrossOver 11.1 (the latest released version) for both Fallout and Fallout 2. While the relevant bug in WINE appears to have been fixed, a lot of people over on the WineHQ database also seem to be experience speed problems too. Because of this, I can't recommend that anyone get this game to run in WINE or CrossOver anymore.

Bump. It pains me to say this, but (after some more testing) performance appears to still be almost unplayably sluggish in CrossOver 11.1 (the latest released version) for both Fallout and Fallout 2. While the relevant bug in WINE appears to have been fixed, a lot of people over on the WineHQ database also seem to be experience speed problems too. Because of this, I can't recommend that anyone get this game to run in WINE or CrossOver anymore.

I have Fallout 1 running almost perfectly well in a WineSkin wrapper with Wine 1.4 (without XInput2). No performance problems at all.

"We do what we must, because we can."
"Gaming on a Mac is like women on the internet." — "Highly common and totally awesome?"

I have Fallout 1 running almost perfectly well in a WineSkin wrapper with Wine 1.4 (without XInput2). No performance problems at all.

The odd thing is that I actually tried Fallout 2 on Wineskin with the CX10.3 engine, the CX11 engine, WS8Wine1.4, W9Wine1.5.6, and WS8Wine1.5. Nothing worked, and they all showed the same speed issue I'd noticed with Fallout and Fallout 2 way back in CrossOver Games 9.x

Just now though, I then checked the option to use the user's system installed Xquartz instead of Wineskin's own X11 and voila - both Fallout and Fallout 2 work perfectly (this was with the WS8Wine1.4 engine). You mentioned that you used an engine without XInput2; I've seen these engines in the Wineskin Winery, but I'm a little unclear as to why they're there.

The odd thing is that I actually tried Fallout 2 on Wineskin with the CX10.3 engine, the CX11 engine, WS8Wine1.4, W9Wine1.5.6, and WS8Wine1.5. Nothing worked, and they all showed the same speed issue I'd noticed with Fallout and Fallout 2 way back in CrossOver Games 9.x

Just now though, I then checked the option to use the user's system installed Xquartz instead of Wineskin's own X11 and voila - both Fallout and Fallout 2 work perfectly (this was with the WS8Wine1.4 engine). You mentioned that you used an engine without XInput2; I've seen these engines in the Wineskin Winery, but I'm a little unclear as to why they're there.

Wine switched over to using Xinput2 in X11. This is great for linux, but very problematic on OSX. If your mouse goes haywire crazy, then trying a NoXInput2 version can often fix the issue.

Crossover's X server is quite old (its even dated 2003 if you watch the logs). XQuartz 2.7.2 runs very well, and I haven't had a chance to make a new version of Wineskin based with it. Wineskin 2.5.5 wrappers WineskinX11 is based of something near around 2.7.0 without some of the nice fixes in 2.7.2.