Fallout 2 Forum

Worked fine under OS X 10.5.something, but now I'm running 10.6.4 and Crossover 8.1.4, and the game crashes immediately after the first "Please Wait" screen. Is there a workaround for this?

Which version of CX are you using? And what are your specs? Have you tried doing a reinstall into a clean bottle?

It does "run." I had to install the killap unofficial patch which apparently fixes some kind of problem because the game does get past the "Please Wait" initialization screen.

It suffers from unplayably slow mouse input and graphical output.

1. Install Fallout 2 from the disc. Exit. Takes an intolerably long time to install the full ~560 MBs, so I just use the 5.6 MBs "minimal" install.
2. Install the killap unofficial patch from the nma forum.
3. Now the game will run, but be too slow to enjoy, with or without the fix for CXG 7.1.0 here:
   http://www.codeweavers.com/compatibility/browse/name/?app_id=4118;forum=1;msg=44330

My Specs:
OS X 10.6.5
CXG 9.2.0
Mac Book Pro, C2D 2.16 GHz, 4 GB ram, ATI X1600 128 MB video ram.

Bug persists for people still:
http://bugs.winehq.org/show_bug.cgi?id=6033

I tried to use regedit but the 'fix' listed doesn't exist in my bottle:
"

For Fallout 1 this is much better solution:
[HKEY_CURRENT_USER\Software\Wine\DirectInput]
"MouseWarpOverride"="disable"
"
Specifically, Wine\DirectInput does not exist, nor could I locate any DirectInput software...

I tried virtual box, I tried dx9 mode in the FO2 'ddraw.ini' file. Mode=4, fullscreen dx9, and mode=5, windowed dx9. Neither worked, that is the screen was white, while I heard the music from the opening movies, but not from the UI in the main menu.

Going back in time on the posts by "Karol Lewandowski" on 2007-09-20. It appears some extra work was added and never fixed when this person worked on using WineD3D to do ddraw.
"I've narrowed this problem to one commit:

c8901d6f6253f6c97610eb1068ac4ff89758ed0a is first bad commit
commit c8901d6f6253f6c97610eb1068ac4ff89758ed0a
Author: Stefan DĂśsinger stefandoesinger@gmx.at
Date: Fri Jun 9 19:36:12 2006 +0200

ddraw: Rewrite most of ddraw using WineD3D.

Unfortunately this diff has 1.5MB and is really old (it's between wine 0.9.15
and 0.9.16.)

After applying this commit:

• loading screen is no longer shown at all, with 0.9.15 it nicely fades in/out,
• game is really slow, mouse pointer becomes useless (and it's only way to play
  this game.)

Hope this helps."

Andrew Trapani wrote:

I tried to use regedit but the 'fix' listed doesn't exist in my
bottle:
"

For Fallout 1 this is much better solution:
[HKEY_CURRENT_USER\Software\Wine\DirectInput]
"MouseWarpOverride"="disable"
"
Specifically, Wine\DirectInput does not exist, nor could I locate
any DirectInput software...

You can create keys in the registry editor, and you should create the DirectInput key. First, select the Wine key (at HKEY_CURRENT_USER\Software\Wine), then from the Edit menu, select New > Key. Name the new key DirectInput. Select it. From the Edit menu, select New > String Value. Name the new value MouseWarpOverride. Set its value to disable.

Hi thank you,
and while that did improve things, that is the mouse settings copy the settings on my OS X system, in both a virtual box window and in full screen, the GUI is still suffering from slow/poor response and poor frame rate on the graphics.

The best way to see is is to go full screen and move the mouse around a bit. I noticed latency in re-drawing the mouse position and poor graphical frame rate when I had my character run, attack, whatever.

Wine is still running at around 60% to 70% of one CPU. Not sure why 70% and not 99%, other than it must be blocking on something, a lot.

If there is a way to get it to run while in D3D mode, there might be some hope. Using the sfall patch included in the killap patch, edit the ddraw.ini in the fallout 2 directory.

[Graphics]
;Set to 0 for 8 bit fullscreen
;Set to 4 for dx9 fullscreen
;Set to 5 for dx9 windowed
;A dx9 mode is required for any graphics related script extender functions to work (i.e. fullscreen shaders)
;Modes 1, 2 and 3 are no longer supported
Mode=0

Set the Mode=4 or Mode=5. When I run this the screen is white, if there is a way to fix this. Sfall says it requires Aug 2009 DirectX 9.0c.

I've tried in Win2k and WinXp bottles to get this program working in D3D mode, but I cannot get it working in D3D and I cannot get it working full speed. :(

New Macbook pro update, it appears to work without this lag anymore.

My previous macbook pro had an ATIx1600 mobile card and I couldn't get this game working properly, given the graphical lag.

I purchased a new macbook pro with an AMD Radeon HD 6750M.

First the native OS X port will open a 640x480 fullscreen game, but the color mode is incorrect and looks like a psychedelic trip, since the ATI/AMD video drivers no longer support 256 color mode.

Now with cross over version 10.0 I cleanly installed the Humongous install of FO2 as required by the following un-official patch:
http://www.nma-fallout.com/forum/viewtopic.php?t=56087

Install the above unofficial patch.
Go into the C drive, find the ddraw.ini, and I edited it like this:

[Graphics]
;Set to 0 for 8 bit fullscreen
;Set to 4 for dx9 fullscreen
;Set to 5 for dx9 windowed
;A dx9 mode is required for any graphics related script extender functions to work (i.e. fullscreen shaders)
;Modes 1, 2 and 3 are no longer supported
Mode=4 ;Changed by Andrew to Mode 4

;If using a dx9 mode, this changes the resolution
;The graphics are simply stretched to fit the new window; this does _not_ let you see more of the map
;Changed by Andrew to a higher resolution
GraphicsWidth=1024
GraphicsHeight=768

I had WINE open up in a virtual desktop so I could watch the performance. It was using around 15% of one processing core and I couldn't get any graphical lag like before. I played through a little bit of the first dungeon.

This is also the same bottle as before with the regedit.exe settings I detailed above for the "DirectInput" to disable the "MouseWarpOverride."

So bottom line is, it works on my new computer...