Fallout 3 DVD and Steam version. Including all 5 DLCs or Game of the Year Edition.
When adding test results please specify video card and driver version you are using.
Follow the guide located below the bug list for installation instructions!
Application Details:
| Version: | 1.7 and GOTY |
| License: | Retail |
| URL: | http://fallout.bethsoft.com/ |
| Votes: | 140 |
| Latest Rating: | Platinum |
| Latest Wine Version Tested: | 5.0.3 |
Maintainers: About Maintainership
What works
The situation appears to be little different to when I submitted my previous report: The game generally runs great, however there are some issues and I recommend using Wine Staging for this game instead.
What does not
For the latter two issues, installing native quartz can stop the crashes with some radio stations and get music playback working to an extent, but playback then becomes very stuttery so it's not worth it. Music playback works with at least 3.10-staging without needing any tweaks/workarounds though, and the mouse slowdown issue with Intel graphics doesn't occur with 3.10-staging either. I haven't tested any newer staging releases yet.
These are quite long-standing issues; you can see my old reports of these issues for CrossOver (which includes screenshots) here: https://www.codeweavers.com/co...
I have uploaded some save games to demonstrate these issues: https://www.dropbox.com/s/ya8h...
Details:
Changing the Windows version to Windows 8 as suggested by another report made no difference.
Workarounds
I strongly recommend disabling winegstreamer as this can cause frequent random crashes on some systems (and aside from this issue it seems to make no difference whether it is enabled or not, so it's best to just disable it to be safe).
If you're using a system with Intel graphics a workaround is required to get the game to run. Two registry keys are required; just run these two commands to add them:
reg add "HKCU\Software\Wine\Direct3D" /v VideoPciDeviceID /t REG_DWORD /d 0x402 /f reg add "HKCU\Software\Wine\Direct3D" /v VideoPciVendorID /t REG_DWORD /d 0x10de /f
What was not tested
I have only briefly tested this version of Wine (and 3.13) to see if any of the previously discovered issues have been resolved, so most of the game was not tested.
Hardware tested
Graphics:
Additional Comments
This report is based on my notes and testing during the creation and maintenance of my wrapper for the GOG version of this game: https://www.gog.com/forum/fall...
Prefix configuration:
- CSMT was enabled
- Wine Gecko was not installed (Wine Mono was installed for the sake of any mods/mod tools that may depend on it, but doesn't seem to be required by the game itself)
If you're using an AMD GPU with the open drivers, this game benefits from enabling OpenGL threaded dispatch; set mesa_glthread=true for a small improvement to performance.
Tested systems:
AMD R7 1700 @ 3.7GHz, 16GB RAM, AMD RX 480 8GB (main system)
Intel i7-2600k @ 4.5GHz, 16GB RAM, Nvidia GTX 750 Ti
Intel i3-6100, 4GB RAM, Intel HD 530 graphics
The main system and i3-6100 system are running Linux Mint 19 64-bit with kernel 4.15.0-33 and stable Mesa 18.1.7 from Padoka's PPA; the Nvidia system is running Linux Mint 18 64-bit and using Nvidia's proprietary drivers (396.54).
| Operating system | Test date | Wine version | Installs? | Runs? | Used Workaround? | Rating | Submitter | ||
| Show | Linux Mint 20.1 | Feb 02 2021 | 5.0.3 | Yes | Yes | No | Platinum | Levon Mentz | |
| Show | Linux Mint 19.1 "Tessa" | Feb 17 2019 | 4.0-staging | Yes | Yes | Yes | Silver | adamhm | |
| Show | Ubuntu 18.10 "Cosmic" amd64 (+variants like Kubuntu) | Feb 01 2019 | 4.0-staging | Yes | Yes | Yes | Gold | Jacopo | |
| Current | Linux Mint 19.0 Tara | Aug 31 2018 | 3.14 | Yes | Yes | Yes | Silver | adamhm | |
| Show | Ubuntu 18.04 "Bionic" amd64 (+variants like Kubuntu) | Aug 04 2018 | 3.13 | Yes | Yes | No | Platinum | Andre Lima |
| Bug # | Description | Status | Resolution | Other apps affected |
| 21267 | Fallout 3 GOTY: Crashes Randomly | NEW | View | |
| 23532 | Provide offline implementation of Games For Windows Live (GFWL) 'xlive.dll' -> 'XLiveless' (Fallout 3, Batman, GTA IV) | REOPENED | View | |
| 30639 | Audio stuttering and performance drops in Star Wolves 3 | STAGED | View | |
| 37508 | Some Bethesda games sometimes freeze during gameplay | UNCONFIRMED | View | |
| 43075 | Fallout 3 crashes un Ultra settings at 1440p: err:d3d:resource_init Failed to allocate system memory | UNCONFIRMED | View | |
| 43105 | Fallout 3, Fallout: New Vegas, and Skyrim crash when the Steam overlay is opened on macOS | UNCONFIRMED | View | |
| 43477 | Fallout 3 crashes after a short time - possibly related to gstreamer | UNCONFIRMED | View |
Last updated 2014-07-21 by Jonas Jelten
Fallout 3 GOTY installation guide
This guide works with a completely fresh 64bit (x86_64) wineprefix.
DO NOT SET WINEARCH=win32
The guide was created using wine-1.5.17 on Funtoo GNU/Linux x86_64.
It should also work on other GNU/Linux distributions.
32bit x86 will probably not be supported.
This means: I assume you are under x86_64 (aka 64 bit system)
==> You have to install x86 libraries for Fallout, as it is a 32-bit game
And so on, you get the point. Refer to your distribution FAQ or forum for help and support installing x86 libraries on x86_64.
Look at the test results/bugs below for version changes affecting Fallout 3.
== DVD/Steam version
== Overview of installation steps
== About this guide
The following text block is a shell command. You have to execute them with your terminal (xterm, gnome-terminal, urxvt, ...).
Search on the web or ask in the forums if you need help.
echo "This is shell code, execute it in a terminal!"
== Create a fresh wineprefix
This guide assumes you create a fresh wineprefix.
export WINEPREFIX=~/.wine-fallout3
Make sure the wineprefix is set correctly all the time you execute wine and fallout-related commands!
echo $WINEPREFIX
== Configure this wineprefix
Now we create a new "Windows installation" and customize its behaviour.
winecfg
== Install fonts
DVD version: skip this step.
cd /tmp && wget http://cdn.steampowered.com/download/SteamInstall.msi && msiexec /i SteamInstall.msi
cd $WINEPREFIX/drive_c/Steam && wine Steam.exe -no-dwrite
wine /mountpoint/of/game/dvd/setup.exe
curl http://www.dllbank.com/zip/m/msasn1.dll.zip | funzip > $WINEPREFIX/drive_c/windows/syswow64/msasn1.dll
wget -O /tmp/gfw.exe http://download.microsoft.com/download/5/5/8/55846E20-4A46-4EF8-B272-7F988BC9090A/gfwlivesetupmin.exe && wine /tmp/gfw.exe /nodotnet
== Run the Gamewine "$WINEPREFIX/.drive_c/Program Files (x86)/Bethesda Softworks/Fallout 3/FalloutLauncher.exe
cd "~/My Games/Fallout3/" && curl "http://pastebin.com/download.php?i=SVqfWG0K" | patch
== (optional) Install uncut patch
This patch replaces four game files, removes censorshit (whoops, typo), and also fixes some launch problems.
cd "$WINEPREFIX/drive_c/Steam/steamapps/common/Fallout 3 goty/" &&
wget -O - "http://home.stusta.mhn.de/~006619/fallout3uncut/fallout3uncut.tar.xz" | xz -d | tar vx
== Run/play the game
export WINEPREFIX=~/.wine-fallout3 && cd $WINEPREFIX/drive_c/Steam && wine Steam.exe -no-dwrite
#!/bin/bash
# Fallout 3 Steam launch script
export WINEPREFIX="~/.wine-fallout3"
cd "$WINEPREFIX/drive_c/Steam"
wine Steam.exe -no-dwrite
#!/bin/bash
# Fallout 3 DVD launch script
export WINEPREFIX="~/.wine-fallout3"
cd "$WINEPREFIX/.drive_c/Program Files (x86)/Bethesda Softworks/Fallout 3"
wine FalloutLauncher.exe
That's it, you should be able to play Fallout 3 now. Report problems at the comment section below.
I'm happy about any feedback improving/correcting this guide, so please leave a comment down below :-)
You should also submit test results so the game's wine-compatibility-rating is up to date and known for most distributions. Thanks!
_
How to get Fallout 3 working (DEPRECATED GUIDE)
This section is out of date. Try the steps from the Steam installation guide above first, but install from your DVD instead of Steam.
This guide was created for wine 1.2, the above guide is for newer versions!
Install Wine-1.1.33 or newer. It is strongly recommended that you install the latest version of wine (wine 1.2). The official information on Wine HQ will always be written for the latest version of wine.
Steps & Requirements:
Winetricks extras:
Open a Terminal
Download winetricks by typing :-
wget http://www.kegel.com/wine/winetricks
Install DirectX libraries and native comctl32.dll by typing :-
sh winetricks d3dx9 cc580
Install Directx9 and vcrun2005 winetricks packages by typing :-
sh winetricks directx9 vcrun2005
Game for Windows Live client:
Now we need to install the Games For Windows LIVE client, follow the steps below :-
Download msasn1.dll from the link - HERE
Extract the DLL files and copy them into your C:/windows/system32 folder of wine
Override msasn1.dll in Wine Configuration - Set as native.
Now download the installer for Games For Windows LIVE from the link - HERE
Note : If you experience issues during that installation of Games For Windows LIVE try changing your windows version to Windows 7 in your winecfg.
Now we need to install the Games For Windows LIVE program but without installing the .NET framework, to do this run the code below in Terminal :-
cd /where/you/downloaded/the/file
wine gfwlivesetupmin.exe /nodotnet
Now in the Libraries tab of your winecfg add xlive.dll as native.
The Games For Windows LIVE client has now been installed.
NOW INSTALL THE GAME FROM STEAM OR THE DISK
(Note: DISK 1 IF YOU HAVE GAME OF THE YEAR EDITION)
Now if your CPU has 2 or more cores then follow the steps below, if not then skip over this section.
If you have 2 or more cores, do the following :-
1) Open ~/My Games/Fallout3/FALLOUT.INI
2) Find bUseThreadedAI=0 and change it to bUseThreadedAI=1
3) Add iNumHWThreads=2 after bUseThreadedAI=1
4) Save file
If you downloaded the game from STEAM then it will already be the newest version and you will not need to patch or install the DLCs (if you own game of the year edition from STEAM). If you own a retail version then you will now need to patch the game. Follow the steps below :-
Make sure your Fallout 3 disk is in the tray (Disk 1 if you own Game Of The Year Edition)
Fallout 3 1.7 patch:
Download the latest patch from the links below depending on your location
US Patch (North America Only) - HERE
UK / EU / Rest of world patch - HERE
Run the patch with wine and it will install.
Now the game will run, see below for how to install the DLCs.
IMPORTANT - To run the game, right click on the fallout3.exe in your C:/Program Files/Bestheda Softworks/Fallout 3 and select "Open with wine windows program loader". DO NOT run the game by using any desktop shortcut or wine menu entry or by the fallout launcher. Use the fallout launcher to set graphics and resolution etc. but don't use it to launch the game.
Install Fallout 3 DLCs
To install the DLCs, follow the steps below :-
If you have the Game Of The Year Edition from STEAM you will already have the DLCs and you are ready to go.
If you own a retail version insert your disk now (Disk 2 if you own the Game Of The Year Edition).
Run the disk's .exe with wine and the DLCs will install.
Note : Some people are finding that the DLCs don't activate when in game. This can be solved, see the DLC Fix section below.
This concludes the installation process for Fallout 3 with wine on Linux.
Troubleshooting/Fixes:
If you have any problems, see the FIX SECTION below for solutions to common issues or you can post a comment and we will get back to you.
DLC Fix
Note : This seems to be a problem with retail disks of the Game Of The Year Edition. The STEAM version should be fine.
Some people have difficulty in getting the DLCs to load. Normally you should receive a message after you have exited Vault 101. However, it seems that some people are not getting the message so the DLCs are not activating. This can be fixed by following the steps below :-
First open~/My Documents/My Games/Fallout3/FALLOUT.INI
Find the line bInvalidateOlderFiles and set it to 1.
Then open the fallout launcher (the .exe is in the same folder as the fallout3.exe) and click on DATA FILES and make sure that they are all selected. Click OK and then launch the game. The DLCs should load in after playing for a few minutes (you will have to have exited Vault 101).
Resolution FIX
Some people have a problem when starting Fallout 3. The menu is displayed but then crashes. This is because sometimes when the game alters your resolution it can break.
Solution 0: You can activate the virtual wine desktop
Solution 1: Set your
resolution in Linux to the game resolution manually before you launch
fallout3. Change it back to your normal Linux resolution when you
finish playing.
Radio / Music FIX
If VATS and Radio stations crash the game, and there is no ingame music, try this:
install quartz.dll with winetricks
Open winecfg, goto library settings, and configure:
quartz = builtin, then native
You can also try to install proprietary mp3 codecs: winetricks l3codecx
The corresponding wine bug: http://bugs.winehq.org/show_bug.cgi?id=31566
steamoverlay
Fallout’s mouse doesn’t seem to work correctly with either the mouse patch or these settings.
- The mouse patch: doesn’t work with Fallout’s 1.1.0.35 patch.
- bBackground Mouse -setting: setting it 1 DOES make menus
usable, but it’s quite a problem when you run this in windowed mode as
when you move enough the mouse, it goes outside the window... I have
dualhead so I need/want to run this windowed.
- MouseWarpOverride were thought to fix this problem with bBackground Mouse
-setting? Well, just gives problems here. Don’t set it. MIGHT be useful
if you have non-patched version. So you gan set to Direct3D registry
key MouseWarpOverride="enable" or MouseWarpOverride="force"
ÂUpdated (20th July 2010)
Note : If you experience issues during that installation of Games For Windows LIVE try changing your windows version to Windows 7 in your winecfg.
Patch 1.7 requires Games for Windows - Live 3.0 client. To install it follow these steps:
1) Download msasn1.dll from e.g. here
2) Override msasn1.dll in Wine Configuration. How to Override DLL
3) Download gfwlivesetupmin.exe from e.g. here
4) Install gfwlivesetupmin.exe but without .NET Framework
(wine gfwlivesetupmin.exe /nodotnet)
5) Only set xlive to native in Wine Configuration.
6) Download and install 1.7 patch for Fallout 3
Note:Should you have any issues running Fallout 3 because of 'xlive unimplemented function' errors, see the fix section above.
It has been reported that the game slows down dramatically when entering VATS or into a speech. The problem hits owners of GeForce 7xxx and older graphic cards. Proposed fixes are:
fix proposed by Bogdan:
fix proposed by Claudio:
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
by Rohit Aggarwal on Friday March 5th 2021, 1:29
by Rohit Aggarwal on Friday March 5th 2021, 1:28
by williamsmith on Wednesday October 21st 2020, 9:58
essaysnassignments.co.uk/assignment-service
by Xalalau Xubilozo on Wednesday October 11th 2017, 0:15
My specs:
Linux Mint 18.2 64 bits
Kernel: 4.11.0-14-generic
Resolution: 1920x1080
DE: Cinnamon 3.4.6
WM: Mutter (Muffin)
Inspiron 7520 A11
CPU: Intel i5-3210M (4) @ 3.100GHz
GPU: AMD Radeon HD 7730M
GPU: Intel Ivybridge Mobile
Memory: 5840MiB
Steps:
0) Note that I'm going to use PlayOnLinux and an open-source driver for AMD cards, so stop right here if they're not for you;
1) Install Padoka Stable PPA for the latest nice open-source graphics drivers: launchpad.net/~paulo-miguel-dias/+archive/ubuntu/pkppa (Read the description(s)!!!)
2) Install this special Wine: launchpad.net/~commendsarnex/+archive/ubuntu/winedri3 (Do not mess with DRI3)
3) Now lets enable DRI3, this is how I got it working:
-- Open the terminal;
-- Check DRI3 status with this command: cat /var/log/Xorg.0.log | grep DRI3
-- If it shows "enabled", stop this step go to the next one;
-- If not, write: sudo nano /usr/share/X11/xorg.conf.d/radeon.conf
-- Paste it in there and save:
Section "Device"
Identifier "Radeon"
Driver "radeonsi"
Option "SwapBuffersWait" "0"
Option "DRI" "3"
EndSection
-- Restart the computer. NOTE:
---- HOW TO UNDO IT: if things "turn black", use this command in the recovery mode to restore the system: mount -o remount,rw / && rm /usr/share/X11/xorg.conf.d/radeon.conf && reboot
---- You can ignore DRI3, but it's faster than DRI2. If it's the case, stop this step go to the next one.
-- Open the terminal and check DRI3 status again: cat /var/log/Xorg.0.log | grep DRI3
-- If it shows "enabled", congratulations, otherwise try what's indicated in the winedri3 PPA description.
4) Configure PRIME: wiki.archlinux.org/index.php/PRIME (PRIME GPU offloading section);
5) Install PlayOnLinux (POL): www.playonlinux.com/en/download.html;
6) Save this script as fl3.sh on your desktop:
#!/bin/bash
[ "$PLAYONLINUX" = "" ] && exit 0
source "$PLAYONLINUX/lib/sources"
TITLE="Fallout 3"
TITLE_CONFIG="Fallout 3 - Configurator"
PREFIX="Fallout3"
GAME_VMS="256"
POL_GetSetupImages "" "files.playonlinux.com/resources/setups/fallout3/left.jpeg" "$TITLE"
POL_SetupWindow_Init
POL_Debug_Init
POL_SetupWindow_presentation "$TITLE" "Bethesda Softworks" "fallout.bethsoft.com" "Xalalau" "$PREFIX"
POL_Wine_SelectPrefix "$PREFIX"
POL_SetupWindow_VMS $GAME_VMS
POL_Wine_SetVideoDriver
[ "$POL_OS" = "Linux" ] && Set_SoundDriver "alsa"
[ "$POL_OS" = "Linux" ] && Set_SoundEmulDriver "Y"
POL_SetupWindow_Close
exit
7) Select "Run a local script" from the "Tools" menu of POL and use the script from the last step to create your prefix (called "Fallout3");
8) Install Steam in the newly created prefix, log in and exit;
9) Install the latest winetricks on the system with this command: wget raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks -O winetricks && chmod +x winetricks && sudo mv winetricks /usr/bin
10) Install the game dependencies with this command: env WINEPREFIX=~/.PlayOnLinux/wineprefix/Fallout3 winetricks comctl32 directx9 dxdiagn l3codecx msasn1 msxml3 quartz vcrun2005 vcrun2008 vcrun2010 devenum
11) Open POL with this command: env DRI_PRIME=1 playonlinux
12) Go to "Configure > Fallout3 > Wine > Configure Wine" and:
-- In the "Staging" tab, select the gallium-nine option ;
-- In the "Library" tab:
---- Set dwrite to builtin if it's not already;
---- Set winegstreamer to disabled (because this: bugs.winehq.org/show_bug.cgi?id=42801#c14).
13) Some real fun? Add poison to the game:
-- 4gb_patch = multicore = www.nexusmods.com/fallout3/mods/21888/?
-- CASM = autosave = www.nexusmods.com/fallout3/mods/3729/?
-- Intel HD graphics Bypass package = game working with Intel = www.nexusmods.com/fallout3/mods/17209/?
-- FOSE = Scripts = fose.silverlock.org/
-- UPDATED Unofficial Fallout 3 Patch = A KAZILION FIXES = www.nexusmods.com/fallout3/mods/19122/?
14) Now open Steam using the POL "Debug" button, open and close Fallout 3 and close Steam. This will create the game config files and you'll be able to see messages in the terminal indicating that gallium-nine is working - these:
Native Direct3D 9 is active.
For more information visit wiki.ixit.cz/d3d9
15) Make the final performance adjustments with this command (from the "Installation Guide"): cd ~/Documents/My Games/Fallout3/ && curl "pastebin.com/download.php?i=SVqfWG0K" | patch
16) You're ready to go!!!
Well, I think it's all... My intention is just to collaborate a little. Ty, have fun.
by Xalalau Xubilozo on Monday January 8th 2018, 19:58
by Nalin Kanwar on Sunday January 29th 2017, 3:16
winetricks devenum
Apart from what's mentioned above; only then will it work. :)
Cheers,
nkk
by Nalin Kanwar on Sunday January 29th 2017, 3:18
by llldino on Friday October 2nd 2015, 18:15
First issue was launching the game. Took me forever to figure out, but for some reason doing:
export WINEPREFIX=.wine-fallout3
wine $HOME/.wine-fallout3/drive_c/.../FalloutLauncher.exe
would not execute and produce a read page error. I had to cd into the directory and then do
wine FalloutLauncher.exe
in order to get the game to run. Fixed music issues by downloading quartz and l3codecx, then setting quartz to builtin using dll-override however Pip-Boy radio music still doesn't work. I'll live with that.
A huge error I had was that the game would randomly crash, especially when entering dwellings or when entering Megaton. The non-depreciated guide above instructs you to patch FALLOUT.ini and add:
bUseThreadedAI=1
iNumHWThreads=4
However, I found that by using
bUseThreadedAI=1
iNumHWThreads=1
solved these crash issues.
Also I should mention I used winetricks and installed
comctl32
directx9
dxdiag(n)
l3codecx
msasn1
msxml3
quartz
vcrun2005
vcrun2008
vcrun2010
I think things are looking pretty good now. Still haven't played though it much, but just wanted to share how I got the game running and somewhat stable. I hope I don't have to eat my words. Also long time listener first time caller here. It's so great to be a part of a community that is so willing to help one another. Inspired me to try and do the same
Happy gaming!
SPECS:
Debian GNU/Linux 8
Linux 3.16.0-4-amd64
Intel i5 4690k [4.5 gHz]
Nvidia GTX 780
12 GB RAM
wine-1.6.2
Installed from DVD
by Rief on Sunday September 20th 2015, 17:22
I think the game should not be rated platinum or gold anymore guys, even the Playonlinux script doesn't work anymore.
by Jason on Friday September 11th 2015, 13:40
OS: Mac 10.9.5
Graphics Card: Intel HD Graphics 4000 1024 MB
Processor: 2.3 GHz Intel Core i7
RAM: 8GB
WineBottler Version: Both 1.6.1 and 1.7.37
Steam Wrapper: SteamBuild1bd3d
by sloof on Sunday August 9th 2015, 16:34
The .ini patch no longer works. Here is the .ini from my installation on 8/9/2015.
by sloof on Monday August 10th 2015, 1:23
by Frankie Baruch on Thursday June 11th 2015, 15:55
by Micah N Gorrell on Monday June 8th 2015, 21:27
steamcommunity.com/app/221410/discussions/0/828938354860178892/
I wasn't able to run XInputTest.exe, but copying all of the other files into the right place and running xboxdrv worked correctly.
These instructions are for an xbox 360 controller, but you should be able to make this work with any controller using the right options for xboxdrv. You'll have to experiment with the mappings though.
by Yash Jain on Wednesday May 27th 2015, 6:42
by Robert Gutschale on Sunday January 4th 2015, 13:05
Following steps:
-ensure the wineprefix is set correctly (echo $WINEPREFIX)
-execute the command 'regedit' from a terminal
-under CURRENT_USER\Software\Wine\Direct3D (create the Direct3D key if missing) make two keys (DWORD)
1.) VideoPciDeviceID = 0x00000402
2.) VideoPciVendorID = 0x000010de
"This makes any games think you have a GeForce 8800 GTS and makes them use their nVidia rendering path. This works well with the Intel HD's rendering system."
Read the linked thread for more information.
As of right now, I haven't really played the game, so I can't tell if it runs stable. I'm gonna update this comment if I run into more problems...
by Oinabilac on Sunday January 11th 2015, 12:48
by ED-E on Sunday June 7th 2015, 9:41
Environment:
Yosemite, MacBook pro mid-14, PlayOnMac with wine1.4.43., adding this keys stopped game from crashing on load, didn't improve overall stabilitiy (which is shite)
by ED-E on Sunday June 7th 2015, 16:21
this is more stable soultion: bugs.winehq.org/show_bug.cgi?id=36226
by Aldo Arriz on Friday January 2nd 2015, 13:55
2.7 GHz Intel Core i5
8 GB 1600 MHz DDR3
Intel Iris Pro
OS X 10.9.4
Error is this:
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x00addf7b).
Register dump:
CS:001b SS:0023 DS:0023 ES:0023 FS:1087 GS:000f
EIP:00addf7b ESP:16e3ecb4 EBP:00000001 EFLAGS:00010202( R- -- I - - - )
EAX:00000000 EBX:04b9ae38 ECX:93a29846 EDX:1656f0a0
ESI:00000000 EDI:04a18f4c
Stack dump:
0x16e3ecb4: 0000001d 04a18f4c 04a18f4c 00000000
0x16e3ecc4: 7bc41bbe 16e3ed38 7bc41c2f 00000006
0x16e3ecd4: 16e3ee28 740ddfee 767b1c1a 16e3efa8
0x16e3ece4: 04b8fb1c 0200cd0c 04b92524 16e3efa8
0x16e3ecf4: 74786554 7bc4116e 00029820 35200000
0x16e3ed04: 00000000 00000002 36863508 00000090
0210: sel=1087 base=81f00000 limit=00000fff 32-bit rw-
Backtrace:
=>0 0x00addf7b in fallout3 (+0x6ddf7b) (0x00000001)
0x00addf7b: movl 0x0(%esi),%eax
Modules:
Module Address Debug info Name (45 modules)
PE 330000- 346000 Deferred xinput1_3
PE 350000- 36e000 Deferred libvorbisfile
PE 400000- 136b000 Export fallout3
PE 1370000- 1738000 Deferred d3dx9_38
PE 1740000- 1873000 Deferred libvorbis
PE 10000000-10008000 Deferred xlive
PE 18000000-18068000 Deferred binkw32
PE 41b90000-41bb0000 Deferred comctl32
PE 41c90000-41cbe000 Deferred user32
PE 41de0000-41de4000 Deferred gdi32
PE 41f10000-41f14000 Deferred advapi32
PE 41f90000-41f94000 Deferred version
PE 41fa0000-41fa4000 Deferred d3d9
PE 41fe0000-41fe4000 Deferred wsock32
PE 43010000-43014000 Deferred wined3d
PE 43150000-43154000 Deferred opengl32
PE 43270000-43274000 Deferred setupapi
PE 432e0000-432e4000 Deferred rpcrt4
PE 43370000-4347f000 Deferred shell32
PE 43570000-43574000 Deferred shlwapi
PE 435f0000-435f8000 Deferred ole32
PE 43740000-43744000 Deferred msvcrt
PE 437e0000-437e4000 Deferred ws2_32
PE 43820000-43824000 Deferred iphlpapi
PE 43840000-43844000 Deferred dinput8
PE 43870000-4387b000 Deferred winmm
PE 438c0000-438c4000 Deferred msacm32
PE 438e0000-438e4000 Deferred dsound
PE 439e0000-439e4000 Deferred imm32
PE 43a00000-43a04000 Deferred winex11
PE 43c20000-43c24000 Deferred uxtheme
PE 453a0000-453a4000 Deferred dinput
PE 453f0000-453f4000 Deferred mmdevapi
PE 45420000-45427000 Deferred oleaut32
PE 45550000-45553000 Deferred winecoreaudio
PE 482a0000-482a9000 Deferred quartz
PE 483b0000-483b4000 Deferred msvfw32
PE 483d0000-483d4000 Deferred devenum
PE 48410000-48413000 Deferred avicap32
PE 48420000-48423000 Deferred msacm32
PE 48440000-48443000 Deferred midimap
PE 48450000-48454000 Deferred wineqtdecoder
PE 48570000-48573000 Deferred winemp3
PE 7b810000-7b866000 Deferred kernel32
PE 7bc10000-7bc14000 Deferred ntdll
Threads:
process tid prio (all id:s are in hex)
00000008 (D) C:\Steam\SteamApps\common\Fallout 3\Fallout3.exe
00000035 0
00000034 0
00000033 15
00000032 0
00000031 0
by Robert Gutschale on Sunday January 4th 2015, 13:08
Worked so far for me, see my comment above yours.
by Adam Pugh on Sunday September 4th 2016, 18:34
Using Play-on-Linux
Wine 1.9.17-staging
Intel® Core™ i7-4710HQ CPU @ 2.50GHz × 8
Intel® Haswell Mobile
64-bit
by Brett Plumley on Friday December 19th 2014, 11:06
1. For radio playback sound stutters and sometimes stops. (codec problem typically)
2. Textures stop rendering at certain times and areas turn black (not sure how to word this one).
3. Game crashes randomly.
4. Needing patched d3d9.dll for certain Intel graphics cards.
5. Game slows down significantly when using VATS.
6. Game crashes after pro-longed play time.
7. General issues with Games for windows live (only if you mod)
8. General misc npc, quest, texture, sound hi-cups (some things just never got patched in final game release)
Some of these can be fixed by installing some mods for the game or third party unofficial patches. (though, I have yet to try that in wine not sure how well that would work.)
(Also, I mean patches for the game not wine.)
by Vladimir on Friday December 5th 2014, 16:29
I was wondering if anyone knows how to fix the radio music?
I have read and reread this whole thread several times and tried some suggested techniques but nothing seems to be fixing it. I personally thing that the Music is very important as it gives that special ambience to the game.
The radio is choppy when music is playing and barely audible but when Three Dog or the President talk its perfect. Also In game radios and Enclave Bots that fly play the radio music perfectly. ?
I am running Wine Wrapper 1.7.31 on Yosemite on the latest Macbook Pro with Windows XP environment set but have tried blank install in another wrapper with Windows 7 too.
I found that the game runs flawlessly on Ultra Graphics and crashes only occasionally which is not a big deal as I use F5 to auto save from time to time.
Regarding the Game, I own the Fallout DVD GOTY edition and made ISO image of it with PowerISO on my old Windows Laptop. DLC's work perfectly too, did not have to change anything in the INI file except the suggested:
bUseThreadedAI=1
iNumHWThreads=4
Input much appreciated.
by Storm Engineer on Tuesday November 4th 2014, 8:40
I simply installed Steam under a new 32 bit prefix, and most of my games worked out of box.
For Fallout, You MUST let it "Games for Windows Live", it won't start without it (Screw you Microsoft!), then add these two lines to the end of fallout.ini INSIDE "My Games", not the ini inside, steamapps, the latter won't work. iNumHWThreads should be the number of cores obviously.
bUseThreadedAI=1
iNumHWThreads=4
Finally disabled Steam Overlay, and that's it. I really don't understand why the HowTo has all that voodoo in it.
by Mike on Thursday August 20th 2015, 12:57
The Live doesn't seem to do any harm installed, thank goodness.
by Mike on Friday August 21st 2015, 15:04
by Zootal on Wednesday October 15th 2014, 22:34
I don't know why it is deprecated, as the latest and greatest did not work for me.
The exception is that I have this in my fallout.ini:
bUseThreadedAI=1
iNumHWThreads=8
Cause I have 8 cores. Works great.
by Tony on Sunday November 29th 2015, 15:56
by max on Sunday October 12th 2014, 5:11
CPU: Intel Core i3-4330
VGA: Integrated Intel HD 4000
Video Drivers: mesa-dri 10.3.0-3, xf86-video-intel 2.99.916-3
Kernel: 3.16.4
You need to edit "My Documents/My Games/Fallout3/FALLOUT.INI" and change following:
- there is no need to disable water refractions or anything like that (even if installation instructions say/do so)
- add following right under bUseThreadedAI
iNumHWThreads=4
- If any of the following is set to 0, you'll get random crashes in game:
bUseThreadedBlood=1
bUseThreadedMorpher=1
bUseThreadedTempEffects=1
bUseThreadedParticleSystem=1
bUseThreadedAI=1
bUseMultiThreadedFaceGen=1
bUseMultiThreadedTrees=1
- setting bMultiThreadAudio to 1 will cause game to hang on exit and will make audio go out of sync in some outdoor locations, but you will have smooth controls/movement and no stutter
- setting bMultiThreadAudio to 0 - game wont hang on exit, but some outdoor locations (operation anchorage) will become unplayable because of stutter... really recommend setting it to 1
bMultiThreadAudio=1
If you have Intel video card game will crash, so you have to fool the game into thinking it's nvidia card, by running regedit and adding following to HKEY_CURRENT_USER\Software\Wine\Direct3D: (taken from bugs.winehq.org/show_bug.cgi?id=32973)
"AlwaysOffscreen"="disabled"
"DirectDrawRenderer"="opengl"
"Multisampling"="disabled"
"OffscreenRenderingMode"="fbo"
"PixelShaderMode"="enabled"
"VertexShaders"="hardware"
"VideoMemorySize"="512"
"VideoPciDeviceID"=dword:00000402
"VideoPciVendorID"=dword:000010de
by Jen on Friday August 8th 2014, 23:31
by Jonas Jelten on Saturday August 9th 2014, 8:23
bugs.winehq.org/show_bug.cgi?id=31566
I suggest you could try running fallout without l3codecx and quartz, and use as much wine-native dlls as possible.
If it still does not work, then open a bug report.
by Jen on Saturday August 9th 2014, 10:31
by Oinabilac on Tuesday October 28th 2014, 1:37
by Storm Engineer on Wednesday January 21st 2015, 12:45
by Storm Engineer on Wednesday January 21st 2015, 12:54
The codecs didn't install properly. Reinstalled them via "winetricks --force" and finally it all works properly! :D
by Erich E. Hoover on Thursday July 24th 2014, 18:27
by Jonas Jelten on Thursday July 24th 2014, 18:54
by newbie101 on Tuesday July 1st 2014, 12:26
Sadly the game will not load. I get the launcher screen but after I hit play, the launcher screen disappear, no game window appears, and the games title in steam briefly flashes "synchronizing" as if the game had crashed/quit.Also will not run if I try running the program from fallout3.exe. Wondering if I missed some little tip or trick to use or if I have to go back to square 1 with a new prefix.
Current distro: Ubuntu 12.04 LTS 64bit
Wine version 1.5.25 (running as XP)
POL: 4.0.14
Hardware:
AMD x6 6100
4gb RAM
AMD HD6770 graphic card using AMD's beta drivers (these were the only ones stable for system/Steam, go figure)
If I'm missing any details, let me know
by Jonas Jelten on Tuesday July 1st 2014, 14:07
it explains how to create a new wineprefix and all other installation steps in detail...
also, you might update your ubuntu version to 14.04.
by Jèrome Lumière on Wednesday March 5th 2014, 11:16
It runs smoothier than in Windows! With Windows8, infact, VAT sequences very quite slow, while with Gentoo there are really no problems, with identical graphic quality.
These are the tweaks I found in this page and on the web that proved to be essential for me:
1) bUseThreadedAI=1 and iNumHWThreads=2 in .ini files;
2) I couldn't get FalloutLauncher.exe to set antialiasing on; so I forced it through .ini files: iMultiSample=8
3) I had troubles with the background music - I could hear ambient sounds and radio speech, but not the wonderful music, so essential, imho, for Fallout3. I couldn't install quartz.dll via POL either, 'cos it gave me this error:
"Couldn't load in-process dll L"C:\\windows\\system32\\devenum.dll".
So I used:
$WINEPREFIX=$HOME/.PlayOnLinux/wineprefix/Fallout3 sh winetricks quartz devenum l3codecx
and the problem got fixed. l3codecx is *very* important - I think it was its absence to cause the music problem.
Very big thanks to everyone for the informations!
by ivarin on Monday December 23rd 2013, 6:35
by Carlos Rodriguez on Wednesday December 18th 2013, 11:39
Wine 1.7.6 (compilado)
Nvidia Drivers 331.20 (.run package)
Linux Mint 15 KDE 32Bit - Kernel 3.8.0.26 PAE
CPU: INTEL Pentium G3220 (Nucleo Haswell a 22nm) 3.0Ghz (Dual-Core) Stock Clock
MEM: 8GB DDR3 1333 (2x4) Patriot value (128 bit dual channel: 21.3 gb/s)
GPU: Zotac Nvidia Geforce GT630 (GK208 28nm: 384 Shaders / 8 ROPS) Zone Edition Passive Cooling 2GB DDR3 1800Mhz a 64Bit (14.4Gb/s)
MAINBOARD: MSI H81M E33
www.youtube.com/watch?v=Xahlb8Za3tQ
by Jonas Jelten on Wednesday December 18th 2013, 13:01
Can you submit a real test report, please?
by Claske on Sunday November 17th 2013, 4:12
Then I found postings on quartz.dll and I installed it with winetricks.
But the recommended settings made the game not start at all.
Disabling quartz gave the game back to me.
But with the winecfg libraries setting:
quartz = builtin, then native
(which is the revers of the recommended settings) suddenly music also worked!
This may be valid for more recent versions of wine (and Ubuntu) as well?
by Jonas Jelten on Sunday November 17th 2013, 7:35
Could you test this behavior with the most recent version of wine? 1.4 is a bit dated :)
by Claske on Sunday February 2nd 2014, 12:04
by Jeff Stewart on Monday December 16th 2013, 11:13
by James Gangur on Sunday February 2nd 2014, 7:34
You deserve a bloody medal!
In fact this works for Oblivion too!
by Claske on Sunday February 2nd 2014, 12:01
Please add your findings in the Oblivion thread - so others may benefit from that also
by Jonas Jelten on Sunday February 2nd 2014, 12:03
by shengzhanzhe on Friday April 26th 2013, 23:13
by Jonas Jelten on Saturday April 27th 2013, 7:37
under ubuntu, this should satisfy your needs:
help.ubuntu.com/community/MountIso
this could help as well: askubuntu.com/questions/164227/how-to-mount-an-iso-file
if you got further problems, comment here, please!
by Will on Tuesday April 2nd 2013, 17:46
Arch Linux x86_64 (kernel 3.8.4)
Steam - Game launcher will appear, I can manipulate the settings, just can't run game.
Wine Version(s): 1.5.27 (tried, 1.5.17-26), also tried 1.5.4.
I have tried running strait stick wine and I have also tried through PlayOnLinux.
The interesting part is; the startup launcher music clip is playing...
Has anyone else had this problem?
by Antoine on Tuesday April 9th 2013, 3:23
by Perry on Saturday January 26th 2013, 20:28
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:d3d:init_driver_info Unable to find a driver/device info for vendor_id=0x10de device_id=0xfd5 for driver_model=2
fixme:win:EnumDisplayDevicesW ((null),0,0x32f53c,0x00000000), stub!
fixme:d3d:init_driver_info Unable to find a driver/device info for vendor_id=0x10de device_id=0xfd5 for driver_model=2
fixme:win:EnumDisplayDevicesW ((null),0,0x32ee0c,0x00000000), stub!
error: xp_attach_gl_context returned: 2
X Error of failed request: 0
Major opcode of failed request: 148 (GLX)
Minor opcode of failed request: 26 (X_GLXMakeContextCurrent)
Serial number of failed request: 392
Current serial number in output stream: 392
Any help would be appreciated.
by Jonas Jelten on Sunday January 27th 2013, 16:46
you need to install this, it may be in the samba package, maybe winbind, figure it out by googling, or tell me your distro name.
the next error may be caused by missing graphics driver, i think you are on x86_64 and you don't have the x86 (32bit) driver installed. (are you using nouveau or proprietary binary blob?)
by Booman on Tuesday November 13th 2012, 15:30
Specs:
Mint 13 32-bit
AMD tri-core
4 Gigs RAM
GeForce 550 Ti
Wine 1.5.16
PlayOnLinux
Follow my Mint 13 step-by-step tutorial on how to install and configure with PlayOnLinux:
www.aoaforums.com/frontpage/software-news-reviews-60/linux/12412-fallout-3-linux-mint-13-tutorial.html
by Jonas Jelten on Tuesday November 13th 2012, 19:15
by Sebastiano Tibolla on Wednesday October 10th 2012, 16:37
I tested it with wine 1.4.1 and 1.5.14 with the same result. Also I can start the game only from the launcher, running wine Fallout3.exe doesn't work.
by Peter Tworek on Monday October 22nd 2012, 14:06
by Sebastiano Tibolla on Monday October 22nd 2012, 14:24
by Ian on Wednesday May 16th 2012, 10:12
by Storm Engineer on Tuesday November 4th 2014, 8:32
by Antonin on Friday April 27th 2012, 8:56
Couldn't inject dll.
this is fose_loader.log:
launching: Fallout3.exe (C:\fallout3\Fallout3.exe)
crc = FE5B82AE
hook call addr = 00C05F61
load lib addr = 00D9B0F0
dll = C:\fallout3\fose_1_7.dll
remote memory = 00370000
couldn't read memory (update winmain)
couldn't init hook
Couldn't inject dll.
terminating process
by Dmitry on Monday September 24th 2012, 15:13
by Simon Janich on Thursday April 26th 2012, 6:57
I found that these crashes stop when I disable the sound in either the game settings (bEnableAudio in Fallout.ini set to "0") or winecfg. However, this is a somewhat unsatisfactory solution as I'd prefer to play the game with sound.
I have yet to try if it is possible to tinker with Wine's audio drivers.
I tried this with a custom build of Wine 1.4 (without Xinput2) on my Mac mini (2.7 GHz i7, AMD HD6630, OS X 10.7.3).
by Steve K on Tuesday May 8th 2012, 12:25
by Steve K on Tuesday June 12th 2012, 19:29
by Antonin on Thursday April 12th 2012, 22:17
err:ole:CoGetClassObject no class object {e436ebb3-524f-11ce-9f53-0020af0ba770} could be created for context 0x1
err:ole:COMPOBJ_DllList_Add couldn't load in-process dll L"C:\\windows\\system32\\quartz.dll"
where can i find their explanation
by Zootal on Thursday March 15th 2012, 13:07
Slackware 13.37 64 bit
Wine 1.4 (doesn't seem to matter what version of wine I use)
Steam version of Fallout 3
by Brandon on Sunday March 4th 2012, 15:16
I can not for the life of me get the mouse cursor to respond accurately. It is all over the place and gets sucked to each side of the screen. I am on a late 2011 MBP. Is there a specific patch for this issue or specific settings I should be using to resolve this issue? I tried just about all resolutions including windowed and non as well as messing with v-sync just in case.
Game is unplayable for me and would like some guidance here as it's driving me crazy. Any help would be great!! Thanks in advance.
by Zootal on Thursday March 15th 2012, 13:09
by George on Sunday June 12th 2016, 8:29
My system is:
CPU: i5-3470
Mobo: Biostar TZ77A
Ram PNY 16GB 1600mhz 9,9,9,22,1T
GPU: EVGA GTX 970 SC ACX 2.0
PSU: Thermaltake SP-650P 650W
Display: HP2009m 1600x900
by Jonas Jelten on Sunday June 12th 2016, 9:40
Also, auto-capturing the mouse in fullscreen is useful (also winecfg).
Some mouse settings can be changed in the wine registry:
wiki.winehq.org/Useful_Registry_Keys
in $ wine regedit:
add / update the key:
KEY: \HKEY_CURRENT_USER\Software\Wine\DirectInput
STRING VALUE: MouseWarpOverride = force
This post describes things:
www.steamgamesonlinux.com/mouse-issues-wine-steam-games/
Hope it helps!
by Joey Tanner on Sunday January 22nd 2012, 13:00
When I launch the game, it comes up, and it does its thing and "figures out what settings would be best for my computer" like any other game I have. but after its done, I change the settings to my preferences (sometimes keeping it how it put it), then press play. But as soon as I press play it dosn't load the game, it just restarts it all over again.
I have a mac and updated version of wine and i have done everything i can think of to fix it, even restarting the whole process of downloading, installing, and restarting. Im out of ideas.
PLEASE HELP
by Brett on Wednesday February 22nd 2012, 21:09
Right click on the wrapper, click Show Package Contents, click on Wineskin, then click on Set Screen Options. There, you can set them more specificially to how you like them.
If that doesn't help in any way, look through this thread. There is plenty of stuff to work off of.
by Rémi on Monday December 12th 2011, 14:59
I'm having some troubles with a very fresh installation of Fallout 3 (1.7 with adds) under playonlinux using wine 1.3.26-xliveless2 version :
When I'm moving on specific locations (like riverboat landing) the game slowdowns dramatically, it lasts around 5-10 minutes then it runs normally (but only for 5 seconds before 'slowdowning' again... )
I tried to change wine version in play on linux but it did nothing.
I don't have sound too, but it worked one time for the first launching of the game after installation...
Except of that everything runs perfectly anyone has ever experience the same issue ?
I'm runnning :
Ubuntu 10.04.2 LTs
Intel(R) Core(TM) i7 CPU @ 2.80GHz
Nvidia GTX 295 1Go
4Go Ram
by Chris Wigman on Wednesday October 26th 2011, 14:39
by Gunman1982 on Monday October 24th 2011, 6:28
just for the record if you have the problem that your DLC isn't working and you try the fix mentioned above you may get the problem that your launcher crashes. If that is the case open winecfg and change the override of comctl32 to buildin. After following through with the DLC workaround you can change it back.
Greetz and have fun
by Silejonu on Thursday October 20th 2011, 13:26
The installation went fine, except a message I didn't understand : "Games For Windows Live is not installed skipping uninstall routine"
Then, when I launch the game I have a "Install" button instead of "Play". If I click on it, I get : "Fallout 3 does not appear to be installed and the installer could not be found. Try exploring to your DVD-ROM drive and selecting setup.exe to install the game."
Trying reinstalling the game over and over didn't solve the problem.
by Silejonu on Monday November 14th 2011, 11:20
by Rinaldus on Thursday October 20th 2011, 3:35
1. You don't have to install any d3dx9 from winetricks, only d3dx9_38.dll and set it to "native" on the Libraries tab.
2. Install msasn1.dll, xlive.dll, vcrun2005 as wrote in instruction above.
3. Install quartz from winetricks
4. INSTALL L3CODECX FROM WINETRICKS!!! I spent 2 days to understand that it's required codec, otherwise you won't hear any music on radio.
Wine 1.3.30, Gentoo Linux 64-bit, NVidia GTX 460
by blosomax on Wednesday December 14th 2011, 17:05
the music is one of the best parts a fallout, and I also was getting frustrated at not being able to get it running under wine
Thanks again!
by Lomax on Wednesday August 17th 2011, 0:29
by mojodoll on Sunday September 4th 2011, 20:03
there were areas that played flawlessly - at windows performance id say - but all of a sudden fps dropped to like one frame every five seconds.
as the error log didnt give any specific information (at least for me), i thought it might have been caused by water surfaces - which made sense as the game began behaving strange when being in megaton (around the bomb, which is surrounded by shallow water).
so, lazy as i am i changed my FALLOUT.INI settings to:
[Water]
bUseWaterShader=0
bUseWaterReflections=0
bUseWaterRefractions=0
bUseWaterDepth=0
bUseWaterHiRes=0
bUseWaterDisplacements=0
bUseWaterLOD=0
and ive yet to see a drop in performance, not a single one since three hours of gameplay.
these settings might be a little drastic, disabling less might also fix the issue, but i guess its worth a try.
the water now looks well, somewhat more funny than bad ;)
by William J Bowman on Monday August 1st 2011, 15:48
Here's a log: pastebin.com/y2Yy0vha
After launching fose_loader.exe, it looks like it's launching just as it does in windows, but then the whole screen freezes. I have to alt-tab and try to kill the Fallout 3 window a few times to regain control of my desktop.
by Jake ward on Saturday July 30th 2011, 4:41
www.youtube.com/watch?v=76Q3mn4LGNE
Gameplay video:
www.youtube.com/watch?v=Fgm7WZoN6NI
It installs and runs great, any lag in the gameplay video is caused by recordmydesktop!!
by Jake ward on Saturday May 14th 2011, 9:38
The game running brilliantly! It was installed through a wine prefix in PlayonLinux
by PoohBear on Tuesday May 10th 2011, 20:06
I just had to post this here because I was tearing my hair out. I have been running Fallout 3 in Wine for a few days, version 1.3.12. I played around with windowed mode and alt+tabbing back and forth between native applications (or else it was trying to run the same Fallout exe from a native Windows installation, can't quite remember when it happened), and Fallout lost all mouse visibility. At first when this happened, when I started the game up, it would scroll through the menu as though I was holding down the "down" key, and after I rebooted it stopped doing this.
I don't know if it just didn't display or if it didn't register the mouse at all, because I couldn't see to click on anything. I think it registered clicks because in the beginning you can click through some of the screens before the menu comes up and I *think* that did work.
After the mouse support disappeared, the keyboard still worked, but if I alt+tabbed out and back in, escape and enter didn't work anymore, as in I could scroll through the menu but couldn't exit or choose items anymore. One time I started playing with no mouse support, and the character was stuck continuously walking up and to the left.
I am describing this detail in case anyone else experiences these issues. What fixed it for me, just now, was I started up the game, and from the main menu used the keyboard to go to setting -> controls. The "invert y" option was changing back and forth from off to on like I was holding a button down, and I pushed up and down several times with the keyboard and moved the mouse around, and suddenly bingo the mouse appeared and the option stopped switching on its own, and I had mouse support back. I suspect I may have moved the invisible mouse somewhere that it triggered an event to do something in the application, like over the invert y option, or perhaps trying to change that option made it check for the mouse again. Anyway, even if it was a coincidence, that worked for me to get the mouse back. The Wine registry setting for MouseWarpOverride did nothing for this problem.
by julovac on Monday April 18th 2011, 18:42
now, mouse is showing weird behavior, cannot move cursor too far from center of the screen, fullscreen/windowed, no difference. solutions provided under "NOTE - Mouse Behaviour" did not help.
problem solved by switching back to wine 1.3.17
by Joni Larsen-Haikarainen on Monday April 18th 2011, 18:49
It also happens in other games like EQ2 and must be seen as a general bug in Wine, with high priority to fix.
by Dan Butler on Monday April 4th 2011, 23:12
by Mahen on Tuesday April 5th 2011, 1:59
Simple way, under Ubuntu :
- first uninstall wine and download the latest source code from winehq then :
- sudo apt-get build-dep wine (in order to install dependencies)
download the following patches :
- bugs.winehq.org/attachment.cgi?id=33595
- bugs.winehq.org/attachment.cgi?id=33700
- bugs.winehq.org/attachment.cgi?id=33893
apply those patches. To do so, go to the directory containing the sourcecode, and use the "patch -p1 *[path to patch files]" for each patch file
then ./configure && make -j 3 (if dual core processos) && sudo make install
Please replace * above with the "smaller than sign".
Thanks to Erich Hoover for providing us with those patches & helping us out.
by Dan Butler on Tuesday April 5th 2011, 17:52
by Pantelis Evgenidis on Saturday March 19th 2011, 15:50
Finally I managed to get it working by creating a 32bit wineprefix with:
WINEARCH=win32 WINEPREFIX=~/.wine32 wincfg.
by Vilém Otte on Saturday March 5th 2011, 14:52
The problem seems to be in D3D, as just before page fault, I get this issue:
fixme:d3d:state_zfunc D3DCMP_NOTEQUAL and D3DCMP_EQUAL do not work correctly yet.
and right after this, I get:
wine: Unhandled page fault on read access to 0x00000014 at address 0x7a6a8a4e (thread 0029), starting debugger...
and this kills the application of course - for me the address 0x00000014 seems a bit low - so I'd say it is not issue in game or wine, but it should be issue in some library?
Anyone met same issue, how can one solve it?
by Vilém Otte on Saturday March 5th 2011, 15:10
I'll post as soon as I'll get Fallout 3 working.
by Joni Larsen-Haikarainen on Wednesday February 2nd 2011, 19:31
and I got playable FPS aroun 15-25 or so I would estimate.
Now I upgraded to a MSI Geforce 460 1GB HAWK Tallon Attack.
In other games, and native games specificly I got an insae preformance boost. In another Wine game (EQ2) I got less of a preformance boost but a preformance boost non the less.
But in Fallout 3 my FPS went down to an unplayable framerate (
by Joni Larsen-Haikarainen on Wednesday February 2nd 2011, 19:37
Prolly cus I tried to type less than 10 fps but with a tag charecter. Get your html code detection code working right!!
Any way so the rest was something like:
...unplayable framerate ( LESS then 10fps)
I use Ubuntu 10.10 (same as before)
I have tried both the 2.60.x nvidia driver that 10.10 surgests.
Aswell as added the X Update PPA with the nvidia 2.70+ driver.
I have tried OSR fbo and backbuffer.
I have tried all kinds of diffrent graphical settings in the game.
It all gives the same low fps.
Has anyone else had this problem, and maybe found a solution?
by Joni Larsen-Haikarainen on Thursday February 3rd 2011, 4:18
I have no idea what exactly it was I did that helped though :(
by Joni Larsen-Haikarainen on Saturday February 5th 2011, 2:47
What solved it was to set *quartz and comctl32 to (builtin, native)
Before I needed quartz to be native for sound to work but now it works better with builtin first and second native.
Not sure if it matters that I have comctl32 (builtin, native) or not but as it now works so great Im just gona leave it as that.
As a note setting quartz as (builtin, native) for Oblivion also made that now run perfect. (from just crashing at launch)
by John Marszalek on Saturday December 25th 2010, 2:46
wine gfwlivesetupmin.exe /nodotnet
fixme:clusapi:GetNodeClusterState ((null),0x32ec24) stub!
fixme:advapi:DecryptFileA "c:\\f6cf7b7255e5ed8bc258f564d32fd9\\" 00000000
fixme:module:load_library unsupported flag(s) used (flags: 0x00000000)
fixme:shell:MLSetMLHInstance (0x71590000,0x7ec60000) stub
fixme:shell:MLClearMLHInstance (0x71590000)stub
Any suggestions, as I'm at a loss why I can't install :(
by Fergand on Sunday January 16th 2011, 23:01
www.fallout3nexus.com/downloads/file.php?id=1086
This program removes GFW Live from Fallout all together. Install the game and run the utility, it ran first try for me afterward.
Only issues I have are with the Anchorage DLC not wanting to work properly, and an unrelated issue with sound...
by Dan Kegel on Tuesday November 16th 2010, 20:56
All I had to do was winetricks -q xlive
to work around bug 23522.
(Actually I just used wisotool, and it did the work.)
It seems runs ok... it seemed to hang
the first time I got out of the playpen, and the
framerate got kind of low in the birthday party,
but otherwise it seems fine.
by Dan Kegel on Tuesday November 16th 2010, 20:58
on an i7 with a gt 240 graphics card.
by Mahen on Sunday October 17th 2010, 12:39
F3 (Fr version) used to work perfectly. I switched to Maverick + Wine 1.3.5. Now F3 complains that it cannot find the DVD drive.
Actually, I figured out it would work when specifying in winecfg a drive with the DVD path. The problem is that the path is "/media/Fallout 3" and there is no generic "/media/dvdrom". Thus the fix only works with Fallout 3 : another game will need to have this D: path changed...
Any idea ? I didn't have to specify this full path before.
by Torbjörn Olsson on Saturday October 30th 2010, 14:29
I have also switched to 10.10, and this comment helped me with the can-not-find-DVD problem.
Although, for some reason, my path is not "/media/Fallout 3", instead it is "/media/floppy1" strange...
by Ragnar on Monday September 27th 2010, 7:42
Help anyone?
by CommonOddity on Monday September 27th 2010, 11:03
Also add the /q argument after /nodotnet and try installing it again.
This might help. I'm not entirely sure if this will help you, but I will look into this further when I have a bit more time.
by Ragnar on Tuesday September 28th 2010, 6:01
by CommonOddity on Monday September 27th 2010, 11:06
MAKE A BACKUP FIRST OF YOUR CURRENT XLIVE.DLL!!!
I'm not sure why, but despite a successful (apparently) install of gfwl, it did not recognize xlive.dll for me either. I had to download it from dll-files.com and inject it myself (no need to tamper with registry, just set to native in winecfg) before the game loaded past that issue.
by Ragnar on Tuesday September 28th 2010, 6:09
fixme:ntdll:find_reg_tz_info Can't find matching timezone information in the registry for bias -120, std (d/m/y): 12/09/2010, dlt (d/m/y): 26/03/2010
fixme:wtsapi:WTSQuerySessionInformationW Stub (nil) 0xffffffff 4 0x94e6c4 0x94e6bc
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC90.CRT" (9.0.21022.8)
err:module:import_dll Library MSVCP90.dll (which is needed by L"C:\\windows\\system32\\xlive.dll") not found
Failed to load DLL xlive.dll
Obviosly the damned GFW is not installed.. But dll is there! FFS MS MUST DIE!
by CommonOddity on Sunday October 10th 2010, 13:02
I would love to tinker around with this, but I simply don't have the time to afford such a thing. I need to be on top of this stuff (learning MPLS can be fun, if you're a masochist).
I'll give this another once-over during break week. Cheers.
by CommonOddity on Monday October 18th 2010, 0:43
Something is missing here... I'm not quite sure what to do to figure this problem out, I'm actually relatively new at debugging and I am not a programmer (but common sense does generally help). I'll look into figuring these sort of issues out and see if there's something more substantial that we could point at before sending it off as a bug to the mighty wine gurus.
Cheers
by Ragnar on Sunday September 26th 2010, 8:02
by Ragnar on Wednesday September 22nd 2010, 16:28
by Kyle Hacker on Monday September 6th 2010, 20:14
Ubuntu 10.04.1 amd64
Wine 1.3.1
Also, if it makes a difference, I'm trying to install the non-GOTY version.
by Kyle Hacker on Monday September 6th 2010, 20:23
by James on Thursday September 16th 2010, 17:54
by Andreas Braml on Friday August 27th 2010, 18:21
1) winetricks dotnet20
2) install FO3 following the instructions here in the AppDB
3) install fomm
4) winetricks gdiplus
5) cd to fomm subdir in the Fallout 3 main directory && wine fomm.exe
6) start the fun!
by Jake ward on Monday August 9th 2010, 3:06
: www.youtube.com/watch?v=22jzP4VGS_M
The sound would previously be like this,
: www.youtube.com/watch?v=w0X_e7Phsxw
by Mahen on Tuesday August 17th 2010, 5:13
by Mahen on Saturday August 7th 2010, 9:09
I do get all sounds, except background music though. Any idea ?
by CommonOddity on Tuesday August 17th 2010, 10:30
Look it over, and list the ones that do have a * in front of them.
The first time I installed, for some reason Dx9 did not play nice and I had to re-install it.
by Mahen on Wednesday August 18th 2010, 1:57
Actually, I had disabled the XLive feature so I didn't have to go through the hassle of installing and overriding its dll. But just to check if it made a difference, I've just installed msasn.dll, xlive.dll and msvcp90.dll, which indeed made the game work with xlive enabled (I wonder if it is any useful).
Regarding sound (music, because other sounds are OK), I didn't notice anything particular with xlive.dll.
Here's the list of the entries with an asterisk in my winecfg :
mapi, mapi32, msaccess, msiexec, outlook, powerpnt, visio32, winword
As for quartz, it is specified "native, builtin"
Actually, to get it working, I only installed fallout from the DVD, upgraded to 1.7 and disabled xlive. I didn't have to do anything else. (crossover 9.1 with wine 1.2)
I'll try to install a different quartz.dll to see if it helps. (note : I have all sounds but no music)
Cheers & thanks a lot !
by Mahen on Wednesday August 18th 2010, 2:04
by Mahen on Wednesday August 18th 2010, 2:11
Apart from that, the game was definitely less smooth than with the builtin quartz.dll ! (even the menu was a bit slow)
by CommonOddity on Thursday August 26th 2010, 13:36
Hmmm. That is quite odd. Quartz.dll was just a suggestion. It could be also a codec issue. Do you have wine-mp3 installed?
What distribution are you running? Version?
Version of wine?
Did you install restricted formats? (There's usually an easy way to do this, ie: 1-click installer in OpenSuSE or the Ubuntu way, which I forgot about lol).
Not sure if Wine interacts with these, but this would also be a good way to start. I hope you made a backup of Quartz.dll. Throw the original back in, and regain your good ol' run speeds :D
by Mahen on Monday August 30th 2010, 8:11
Well, I tried with both Wine 1.3.x and Crossover 9.1 (powered by Wine 1.2 I guess).
I do have all Ubuntu restricted packages. I wonder if those are used by wine ?
What is "wine-mp3" ? Never saw it mentioned anywhere actually.
Cheers !
by Seth on Sunday July 25th 2010, 2:22
seth@linux-allj:~> wine .wine/drive_c/Program\ Files/Bethesda\ Softworks/Fallout\ 3/Fallout3.exe
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT" (8.0.50727.762)
err:module:import_dll Library MSVCP80.dll (which is needed by L"C:\\windows\\system32\\xlive.dll") not found
err:module:import_dll Library xlive.dll (which is needed by L"Z:\\home\\seth\\.wine\\drive_c\\Program Files\\Bethesda Softworks\\Fallout 3\\Fallout3.exe") not found
err:module:LdrInitializeThunk Main exe initialization for L"Z:\\home\\seth\\.wine\\drive_c\\Program Files\\Bethesda Softworks\\Fallout 3\\Fallout3.exe" failed, status c0000135
I have installed the GFWL and have set xlive to native in wine, I don't know what the other is and it is not mentioned in the instructions.
I would really like this game to work and I am REALLY questioning the gold rating as it seems there is a lot more to getting the game to work than "it works right out of the box". I run DDo and it was WAY WAY WAY easier to install.
by Seth on Sunday July 25th 2010, 2:24
by Kris Blackhall on Sunday July 25th 2010, 4:27
It seems that the problem preventing you is that the msvcp80.dll file is not being "seen" by wine. Hence xlive cannot run. Fallout must have a working xlive to work, and xlove needs msvcp80. So the problem stems from the msvcp80.dll. You need to make sure that you have downloaded the msvcp80.dll file and put in in your wine system32 folder. Then you have set an override for it in your winecfg.
Also, make sure you have the latest graphics drivers installed for you graphics card as if not that may also be causing problems.
Also, the rating for a program working "right out of the box" is platinum. A gold rating indicates that a program works well once certain overrides have been done.
by Seth on Monday July 26th 2010, 1:01
I really want to get this game working and I don't understand why I am having so much trouble. If there is something else I can do to give better info that will help let me know.
by Kris Blackhall on Monday July 26th 2010, 4:32
This looks like a problem with your system rather than with wine. The errors you got from the terminal output are the same as a lot of other people have seen. It simply means you are missing some dll files. If you have put them in system32 and overridden them in winecfg then wine is not the problem but something else. Have you messed around with your xorg.conf file? Or done anything strange with your graphics because it seems like the problem is not with wine but with other areas of your system. Your X seems to crash which would indicate that there is a problem with it and not a problem with wine. Do you have compiz installed and do you get 3D desktop effects?
by Seth on Monday July 26th 2010, 11:50
by Kris Blackhall on Monday July 26th 2010, 13:10
Why don't you use compiz? As if you did it would confirm for me that your graphics card and drivers are OK. Give compiz a try and give the 3D effects a go such as the paint fire and water etc. If they work then there should not be a problem with the drivers.
We need some sort of confirmation that your graphics card and drivers can run 3D stuff. Compiz 3D effects are an excellent way of doing this. Try out the complex 3D effects and get back to me.
It really does look like the problem lies somewhere either in your X setup or in your graphics drivers refusing to do anything 3D and just stopping whenever any 3D rendering is needed. SO give compiz a go as I mentioned.
by Seth on Tuesday July 27th 2010, 0:16
by Kris Blackhall on Tuesday July 27th 2010, 4:42
www.nvidia.com/Download/index.aspx?lang=en-us
Also, you said you use wine 1.1.44. Make sure you update that to the latest version of 1.2.
Another possibility is that if you did any overrides or tweaks to wine when you were putting on other windows programs. The overrides you used to get them to work may be interfering with Fallout 3. As the majority of the official information here will be for Fallout 3 on a clean wine with no other overrides for other windows programs.
by Seth on Tuesday July 27th 2010, 8:56
=>0 0x7bc4da68 in ntdll (+0x3da68) (0x02e76ae0)
wine: Call from 0x7bc4da68 to unimplemented function xlive.dll.5297, aborting
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0xf74dca66
wine client error:9: write: Bad file descriptor
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7d5545be
wine client error:9: write: Bad file descriptor
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7d5545be
wine client error:9: write: Bad file descriptor
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7d5545be
wine client error:9: write: Bad file descriptor
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7d5545be
wine client error:9: write: Bad file descriptor
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7d5545be
wine client error:9: write: Bad file descriptor
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7d5545be
wine client error:9: write: Bad file descriptor
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7d5545be
wine client error:9: write: Bad file descriptor
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7d5545be
wine client error:9: write: Bad file descriptor
It is looking like xlive is still the problem, as it is the only real error int he rest of the terminal output. I installed the GFWL, though I am not sure if it is installing properly, nor how to tell if it is or not. WHen I install it it flashes two small windows real quick and the status bars on them go by just as fast, but I get no errors in the terminal from it.
by Seth on Tuesday July 27th 2010, 9:29
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC90.CRT" (9.0.21022.8)
err:module:import_dll Library msidcrl40.dll (which is needed by L"C:\\windows\\system32\\xlive.dll") not found
err:module:import_dll Loading library MSASN1.dll (which is needed by L"C:\\windows\\system32\\xlive.dll") failed (error c0000024).
err:module:import_dll Library xlive.dll (which is needed by L"Z:\\home\\seth\\.wine\\drive_c\\Program Files\\Bethesda Softworks\\Fallout 3\\Fallout3.exe") not found
err:module:LdrInitializeThunk Main exe initialization for L"Z:\\home\\seth\\.wine\\drive_c\\Program Files\\Bethesda Softworks\\Fallout 3\\Fallout3.exe" failed, status c0000135
Then after installing the msidcrl40.dll I got:
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC90.CRT" (9.0.21022.8)
err:module:import_dll Loading library MSASN1.dll (which is needed by L"C:\\windows\\system32\\xlive.dll") failed (error c0000024).
err:module:import_dll Library xlive.dll (which is needed by L"Z:\\home\\seth\\.wine\\drive_c\\Program Files\\Bethesda Softworks\\Fallout 3\\Fallout3.exe") not found
err:module:LdrInitializeThunk Main exe initialization for L"Z:\\home\\seth\\.wine\\drive_c\\Program Files\\Bethesda Softworks\\Fallout 3\\Fallout3.exe" failed, status c0000135
I double checked and all dll's are installed and set to native as required.
by CommonOddity on Tuesday July 27th 2010, 9:53
There is a way I've found to get around this (in one of the last comments).
There's a website where you can download xlive.dll, and msvcp90.dll.
Xlive.dll seems to be newer, so it's 13.x MB in size (compared to the 9.x MB in size for the gfwlivesetupmin.exe version listed in the howto).
When you toss msvcp90.dll in system32, set override to native, and put its msvcr90.dll counterpart to builtin- the game should run.
I have this issue with OpenSuSE 11.3. It took me some tinkering to figure this out. The game lags occasionally, but it's able to run. I'm going to do my best to maintain this game (not yet an official maintainer, about to be though). I'll let you know when I come across anything else.
Like I said, check out my comments, and try out the suggested fix I listed there.
Good luck brah.
by Kris Blackhall on Tuesday July 27th 2010, 12:34
by Seth on Wednesday July 28th 2010, 3:11
by Kris Blackhall on Wednesday July 28th 2010, 7:45
This could be a distribution specific problem as the testers that used ubuntu and fedora etc. report that it is fine.
by CommonOddity on Wednesday July 28th 2010, 21:42
Check out the xlive.dll FIX in the section above. It explains how to do this.
It seems to run well enough for me (although the fps is a little lower than usual with momentary spots of lag).
by CommonOddity on Thursday July 22nd 2010, 22:13
OpenSuSE 11.3 (32-bit, I've attempted this on 64-bit also, but 'sh winetricks directx9 vcrun2005' does not work with 64-bit).
Fallout 3 installs. I've installed the Live client. All steps necessary were taken. However- upon installing the Fallout 3 1.7 patch, Fallout 3 crashes at start.
Apart for all the obvious fixmes, it spits out these lines in particular:
wine: Call from 0x7bc4af38 to unimplemented function xlive.dll.5297, aborting
wine: Unimplemented function xlive.dll.5297 called at address 0x7bc4af38 (thread 0009), starting debugger...
Unhandled exception: unimplemented function xlive.dll.5297 called in 32-bit code (0x7bc4af38).
And this is the backtrace:
=>0 0x7bc4af38 call_dll_entry_point+0x4a8() in ntdll (0x0303e1bc)
wine: Call from 0x7bc4af38 to unimplemented function xlive.dll.5297, aborting
wine: Call from 0x7bc4af38 to unimplemented function xlive.dll.5297, aborting
Segmentation fault
I'm not sure what to do. I've tried everything. I've tried installing the patch with /nodotnet- and it still does not work. I uninstall Fallout 3, and re-install it so it is unpatched and it runs successfully. It is just after installing the 1.7 patch that all this happens. Has anyone else had this issue? Is there a possible fix?
I tried this with wine1.2-rc6 AND wine1.2-4.1 from the OpenSuSE repos (OSS + Wine CVS builds).
EVGA GTS250 512mb video card
AMD 240 class, 2.8Ghz CPU
Biostar TA790GX
Nvidia binary 256.35 drivers (from site, installed after wine was).
by CommonOddity on Thursday July 22nd 2010, 22:15
by CommonOddity on Friday July 30th 2010, 8:39
I'm going to either file a bug or take this to someone in the OpenSuSE community to see what my next step should be.
IF ANYONE ELSE HAS THIS ISSUE AND IS USING A DISTRIBUTION OUTSIDE OF OPENSUSE 11.3- PLEASE LET ME KNOW. It might be an issue with Wine that affects certain distributions only (through configuration or lack of a component/switch to something else).
by Kris Blackhall on Friday July 30th 2010, 14:48
by Kris Blackhall on Friday July 23rd 2010, 4:24
Try the following suggestions below :-
When you were following the steps above, and you downloaded the msasn1.dll and put it into your system32 folder, did you also override it in winecfg? You have to do this manually. Open your winecfg, go to the libraries tab and add msasn1.dll to override it. The gfwl client needs the msasn1.dll to be present and set override in winecfg. I have edited the HOWTO above to include this step.
Also, did you see my note about possibly having to switch wine to Windows 7 during the gfwl client bit?
Also if you downloaded the patch using the link on the HOWTO it will have downloaded the US version. If you are outside North America you need to download the non US version. I have edited the HOWTO above to give a link to both the US and non US versions now. Download the one that is appropriate to you.
Finally make sure you are doing this on a clean wine install. Make sure if you remove wine to reinstall it you also MANUALLY delete the .wine and .winetrickscache folders in your Home folder.
Try these suggestions and you can always come back for more help is needs be.
by CommonOddity on Friday July 23rd 2010, 8:13
Thank you for maintaining this game, btw :) I see you tossing up a lot of posts. Greatly appreciate it!
Per your comments: I did install gfwl, it tossed out a lot of fixmes, but the first time around it did actually install. I did override msasn1.dll before installing, and I did set the default settings category to Windows 7. Like I said, I did everything to the letter.
I'm in Canada, so yes, still in North America- the patch thusly is fine, as the retail version is US as well.
There is one interesting caveat however: I am unable to remove gfwl using wine uninstaller... I attempt to either modify or remove the app, and it just does nothing. I'm thinking something is/was botched upon install. But it doesn't make any sense to me. Either I've bad luck, or there is something wrong with wine at the moment. Like I said, I've done everything to the letter. I'll still be fiddling around with this for the next little while.
I'm just trying to figure out whether this was a distro-centric problem, or whether the issue is originating in wine (thus, either way, a bug report should be pumped out).
I'll attempt to uninstall and wipe the .wine/.winet...etc cache, reinstall all of this, and bang my head against the wall some more.
I just got my GTS 250 too, so I've been all kinds of excited to get this game going. Starcraft 2 Beta made me drool all over the desk. Ultra settings at 1280x1024 and it runs without a hitch, 60fps. Nomnomnom.
by Kris Blackhall on Friday July 23rd 2010, 9:44
As for the gfwl. Wine uninstaller is notoriously unreliable at removing things. Basically if you uninstall wine completely and manually delete the .wine + .winetrickscache folders in your Home folder after you uninstall it will remove everything.
Also, wine often leaves some files in another location. In your Home folder there will be another hidden folder called .local. Wine entries can be found in /.local/share/applications make sure you manually delete these also.
The only other ting I recommend would be when you reinstall wine make sure you have the wine ppa in your software sources to ensure that you get the latest updates as there were some major issues with wine 1.2 that were promptly fixed with an update. Instructions in the link below if you need them :-
www.winehq.org/download/
Also, congratulations of the GTS 250! It is indeed a nice card. Hope you can get Fallout 3 working. If you do manage to get it up and running it should be excellent on a GTS 250. I runs very nicely on my 9400 GT.
by CommonOddity on Friday July 23rd 2010, 14:18
by Kris Blackhall on Friday July 23rd 2010, 15:19
www.winehq.org/download/
Perhaps you should try other distributions such as Ubuntu or Debian or SUSE etc. I would personally recommend Ubuntu as it has a lot of support due to its top popularity. The more major distros are more likely to work better with wine.
by CommonOddity on Friday July 23rd 2010, 17:07
It's only after the 1.7 patch that it breaks... But it's really awkward because GFWL client DOES install (I set default to Windows 7 during install).
It runs perfectly unpatched.
I'm stumped. I don't really want to switch distros at the moment. OpenSuSE is not really obscure, or small for that matter. I'll wait for an update to come out first, then I will try again. Until then, I'll just play it on my laptop.
by Kris Blackhall on Saturday July 24th 2010, 4:04
by CommonOddity on Sunday July 25th 2010, 9:45
So here's what I've done:
1. I've downloaded a version of xlive.dll from the web (in particular, this site: dll-files.com (www.dll-files.com/pop.php?dll=xlive)
2. I've dumped xlive.dll in system32 (it's already set to native in winecfg)
3. Loading fallout 3, it whines (ha ha! - Phil Ken Sebben) about not having msvcp90.dll... And thusly I download it, toss it into system32.
(www.dll-files.com/pop.php?dll=msvcp90)
4. I run winecfg, set msvcp90.dll to native...
5. I run Fallout 3, do the happy dance, and nuke some super mutants :D
YES! HOORAY FOR PERSEVERANCE!
by CommonOddity on Sunday July 25th 2010, 10:33
There's a slew of issues that appear by taking this route. Firstly, the music/sound (some sounds, not all) get botched (even with wine 1.2-4.1). The intro theme and the fallout launcher do not automatically begin. I attempt to use the radio via pipboy, and the game crashes, spewing this out:
fixme:quartz:parse_header Not a valid header: 21:34
fixme:quartz:parse_header Not a valid header: 34:c1
fixme:quartz:parse_header Not a valid header: c1:a6
fixme:quartz:parse_header Not a valid header: a6:78
fixme:quartz:parse_header Not a valid header: 78:92
There's much more of those lines, but I thought those would be sufficient.
I've also had the game crash once on me, for no apparent reason.
Sigh. Back to the old drawing board.
by Kris Blackhall on Monday July 26th 2010, 4:51
Perhaps you could try the "Sound Fix" from the FIX section above. It has been reported as solved in wine 1.2-rc6 onwards but it may work for you.
by CommonOddity on Monday July 26th 2010, 8:26
It works. Everything. Radio, and then some. It's slower than what I expected- but I think we can either thank DirectX or the engine for that (somehow, I doubt it's the engine at the moment).
I'll look into this further, play around with the game, and report anything odd/unusual.
by Seth on Tuesday July 20th 2010, 1:21
by Kris Blackhall on Tuesday July 20th 2010, 5:30
by Carlos Rodriguez on Sunday July 18th 2010, 8:37
DDR 2 800, IGP ATI Radeon 3100 512 shared memory, MSI K9A2VM
works good at least menus, after this mouse not work with/out dinput overrides
by Kris Blackhall on Monday July 19th 2010, 6:35
by Holly Bostick on Sunday July 11th 2010, 3:44
With vcrun 2005 installed, the Launcher would appear and allow me to run the installer, but the installer itself would not run:
motub /media/dvdrom0 $ wine H:\\setup.exe #The Launcher refuses to run the installer if you're not at the DVD;
motub /media/dvdrom0 $ err:ole:TLB_ReadTypeLib Loading of typelib L"C:\\Program Files\\Common Files\\InstallShield\\Professional\\RunTime\\IsProBE.tlb" failed with error 2
fixme:storage:create_storagefile Storage share mode not implemented.
err:ole:dispatch_rpc no apartment found for ipid {ffffffff-ffff-ffff-1e00-00001b000000}
err:rpc:I_RpcReceive we got fault packet with status 0x80010108
There was also a Windows error dialog saying something about an object or object class not being created, but I didn't write it down; I expect that this is the same error others are experiencing with the InstallShield installer, thus already documented. Nice clean crash, though.
Upon reading comments here, I reverted to rc6, where I knew the installer did run, and reinstalled under the same prefix with only vcrun 2005 installed and ALSA selected as sound (I'm using Linux Mint 9, which is based on Ubuntu 10.04, so I have PulseAudio, which I have not uninstalled as yet).
This time, I decided to let the installer run the game when it had completed (rather than saying no and installing the patch first).
To my surprise, I had sound in the main title (the clicks of the slide, not the music, but that's been gone so long that I don't even count it as a bug anymore), and the intro ran absolutely perfectly.
Then I got to the childbirth sequence, lost sound and again the first dialog did not appear (I have subtitles on, and so Dad's line did appear, but I got no 'choose your gender' dialog).
I hit ESC, thinking to quit, but then hit 'Continue' instead, and on a hunch from another comment, where the poster said they could only hit 'E' to cry, I hit 'E' to see what would happen.
The dialog appeared. I chose my sex, and the first line of Dad's dialog appeared, then the sequence "froze" again-- the lights continued to blink on the monitors in the background, but 'baby-head cam' stopped moving, and so did Dad and the lady doctor (avoiding spoilers).
I continued to step through the intro with the combination of ESC=>Continue=>E. This worked OK till Mom died, at which point I was pushed out into the hall (!!!)-- an area that I had never seen, because normally the whiteout occurs before my crib even reaches the door.
I hit the combo, twice I think, and the whiteout happened-- complete with the sound of my crying from either the beginning of the sequence, or from my last press of E, running over the whiteout dialog.
The whiteout faded, and my ears were blasted by Dad's voice, and the music from the baby music box (so sound seems to work once the actual game has started, but not in the childbirth sequence).
I am so weirded out that I wanted to write this down before 'upgrading' to RC7 and starting a new game via the same install (since I can't install under RC7) to see if the childbirth sequence is really fixed there as promised.
Because all this happened under RC6, which is technically behind the current RC, I don't feel like a bug report is appropriate, but this was all so strange and complicated that I did feel like it needed to be documented.
There you go, then.
by Kris Blackhall on Sunday July 11th 2010, 4:07
Also - RC7 is very problematic at the moment. We are having to rework a lot of areas. As you know Install Shield will not work.
Have you tried using the SOUND FIX written in the HOWTO section above. That may fix your sound. But the best bet for now is to stick with RC6. RC7 was released way too early.
by Indruck Balázs on Friday August 20th 2010, 6:13
by Stephen on Sunday August 29th 2010, 22:10
by Indruck Balázs on Monday August 30th 2010, 7:55
it's a bug. :)
by Torbjörn Olsson on Saturday July 10th 2010, 14:43
In fact, now it is worse than before RC-6. Then I could work around the problem by replacing winmm.dll.so. Now that trick no longer works.
There is one exception when sound does work for me in RC-7, and that is the sound that is played when the character dies, not very encouraging :p
Has anyone else experienced this problem? It seems like RC-7 will be the last RC before release of 1.2, so does that mean it is now too late to fix his last minute regression?
by Kris Blackhall on Saturday July 10th 2010, 14:47
by No OnE on Sunday June 27th 2010, 21:42
Still beats Windows 7 though(, which doesn't run anything else than the launcher, says "Fallout has stopped working"). ;)
by Torbjörn Olsson on Thursday July 1st 2010, 11:29
wine.budgetdedicated.com/archive/ubuntu/jaunty/wine_1.1.37~winehq0~ubuntu~9.04-0ubuntu1_i386.deb
and then unpack winmm.dll.so to /usr/lib/wine/ (sudo required) ?
In sound configuration I need to select both ALSA *and* OSS.
This makes it work perfectly with Pulseaudio.
I have used this configuration successfully for all versions from 1.1.44 to 1.2-rc5
Everything works, including radio (except for the Enclave radio station).
by Indruck Balázs on Tuesday June 22nd 2010, 3:01
I've managed to install the game, but it doesn't work sadly. I've installed al the necessary dlls, tried on different versions of wine (from 1.1.37 to 1.1.44), and I've tried all the ideas described here. Whenever I start the launcher or the fallout3.exe, I get the same fatal error messages:img254.imageshack.us/img254/906/fallout3polissue.jpg
I bought the game yesterday, and it's a localized version, I can't start it in English or whatever. Tried to change the language of Ubuntu but is doesn't work.
I use Ubuntu 10.04 LL, and I have ATI HD 3200 video card.
Oh, and whenever I start the game, it doesn't even starts to read from the dvd, and when I start the game from the dvd (launcher or fallout3.exe), i get the same fatal errors. I tried it with playonlinux but no solution.
I get this in the terminal:
bazsi@bazsi-laptop:~$ wine "C:/Program Files/Bethesda Softworks/Fallout 3/Fallout3.exe"
fixme:reg:GetNativeSystemInfo (0x32fc04) using GetSystemInfo()
fixme:volume:GetVolumePathNameW (L"C:\\Program Files\\Bethesda Softworks\\Fallout 3\\protect.x86", 0x37e942c, 32), stub!
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
fixme:reg:GetNativeSystemInfo (0x33f9f8) using GetSystemInfo()
bazsi@bazsi-laptop:~$
Any help would be appreciated!
by Indruck Balázs on Friday August 13th 2010, 10:51
thank you!
by Kris Blackhall on Friday August 13th 2010, 12:01
by Indruck Balázs on Friday August 13th 2010, 15:48
by Indruck Balázs on Friday August 20th 2010, 5:43
I don't know if I can link this: m0004.gamecopyworld.com/games/pc_fallout_3.shtml but here you can find a no-dvd exe for launcher and fallout3 too. Only download, if you have retail copy of the game! Then follow the instructions as described above. If you finished, the replace the fallout3.exe and falloutlauncher.exe with the new ones.
Now start the the launcher from your .wine directory (right click and run with wine). Set the options, then exit. DO NOT start via the launcher, use it only for set the options. Then start the game from your .wine directory: Fallout3.exe (right click and run with wine) :)
by dremon on Wednesday June 16th 2010, 10:23
When Fallout3.exe starts it crashes with:
wine: Unhandled page fault on read access to 0x00090928 at address 0x6ba993 (thread 0026).
If I change the version from XP to 98 (in wincfg) then it starts but there is no sound.
by ejwaxx on Monday June 14th 2010, 21:41
wine: Unhandled page fault on read access to 0x0000001e at address 0x1e (thread 001c), starting debugger...
Unhandled exception: page fault on read access to 0x0000001e in 32-bit code (0x0000001e).
err:dbghelp:pe_load_dbg_file Couldn't find .DBG file "COMCTL32.dbg" ("")
with stacktrace following. Consequently I can't get Fallout 3 to run, as the Fallout3 executable crashes with a reference to a missing function in xlive.dll that GFWL provides. Any advice?
by Piotr on Tuesday June 15th 2010, 6:42
by ejwaxx on Thursday June 17th 2010, 21:49
Incidentally, I can't even get the bloody thing to run with PlayOnLinux, either.
by ejwaxx on Friday June 18th 2010, 3:23
by Torbjörn Olsson on Sunday May 23rd 2010, 5:26
For me it crashes immediately after starting it...
by Piotr on Tuesday June 15th 2010, 6:45
by Henry on Saturday April 24th 2010, 0:13
Is someone being able to open the console with wine?
I have tried changing the keyboard layout, tried remmaping a key to send the tilde to fallout directly with xmodmap, tried even the windows application AutoHotkey to remmap a key to send the tilde (it worked for linux applications also!), and nothing helped to open the Fallout3 console!!! :(
on windows, ppl say we must disable infra red device, but I cant find it on wine... :(
by blaise on Saturday April 24th 2010, 20:57
Add bAllowConsole=1 to Fallout.ini under the [Interface] section.
by Henry on Saturday April 24th 2010, 21:49
but... I found this mod and it works like a charm!!!
Console Key Binder
www.fallout3nexus.com/downloads/file.php?id=2637
by blaise on Saturday April 24th 2010, 23:01
by Laurent - CyberSDF on Wednesday April 14th 2010, 6:11
I have this message : wine: Unhandled page fault on read access to 0x000003c0 at address 0x6848b63e (thread 0009)
Any idea to bypass this crash.
by Laurent - CyberSDF on Friday April 16th 2010, 4:53
by yog on Friday March 26th 2010, 4:22
get wine-1.1.41 compile and install it.
then get old wine-1.1.37 compile it but do not install it,
instead just grab its "winmm.dll.so" and use it.
cd /usr/local/lib/wine/
mv winmm.dll.so winmm.dll.so--
cp wine-1.1.37/dlls/winmm/winmm.dll.so /usr/local/lib/wine/
and you get all the sounds back..
by Gyz on Monday March 29th 2010, 15:36
I run wine 1.1.40 under Debian Lenny x64. I copied the 1.1.37 version of winmm.dll from the .deb package to /usr/lib/wine/ as suggested. It solved the 2 main problems affecting gameplay 1) no sound except voices 2) after a while the framerate decreases and the game needs to be restarted (underrun error of some sort).
The game now works flawlessly with Alsa driver set to Full at 44100Hz,16 (if that matters).
by Jake ward on Monday April 5th 2010, 8:19
by Dan Butler on Sunday April 11th 2010, 21:48
by yog on Sunday April 11th 2010, 22:32
rapidshare.com/files/374856823/winmm.dll.so.html
i don't know what the results will be depending how your architecture differs from mine but if you want to try out ..
by Dan Butler on Sunday April 11th 2010, 22:50
by Joni Larsen-Haikarainen on Monday April 12th 2010, 2:19
you can simply just open up that same distrubutions package with archivemanager and extract that file alone. and insert it to your installation of 41 or 42.
(did this myself on Ubuntu and it works fine)
by Dan Butler on Monday April 12th 2010, 17:57
by Dan Butler on Monday April 12th 2010, 18:02
by Dan Butler on Tuesday April 13th 2010, 0:12
by Türklinke on Thursday May 13th 2010, 9:42
by Piotr on Tuesday June 15th 2010, 6:51
Just place the 1.1.37 winmm as winmm.dll inside Fallout 3 folder. I think you don't even need an override as the sound worked without needing to add such override.
by Joni Larsen-Haikarainen on Wednesday March 17th 2010, 2:48
But I do get a general slowdown (much less FPS) if I move to a new area or sometimes when I zone.
Only way to solv it temporarely Iv found is to hit esc, save the game and quit and restart the game at that spot. Then the FPS is fine agin.
The specs I have:
Ubuntu 9.10 64bit
Intel Core i7 920
6GB RAM DDR3 1600MHz
Asus GeForce 8600GT 512MB Silent
If this was due to actualy loading new resources in the game I would expect it to go back to normal FPS agin, but it dosen't.
And if it where to the rather old graphics card i have I would expect sertan areas to allways be low FPS. But this is not the case ether as I get decent FPS agin after I restart the game.
Anyone else having this issue?
by Joni Larsen-Haikarainen on Wednesday March 17th 2010, 2:51
My game is GOTY Edition with the 5 addons. Patched to 1.7
Windows Live Disabled
I use Wine 1.1.37
With various tweaks Iv found on this page Iv gotten the game to otherwise run flawlessly.
by Robert Gregory on Thursday March 18th 2010, 19:43
by blaise on Friday March 19th 2010, 0:32
by Robert Gregory on Saturday March 20th 2010, 12:33
My CPU usage is up around 90% while the game is chugging, but memory usage is steady around 800MB, which doesn't seem out of place.
I guess I am not seeing the problem you describe after all.
Sorry I couldn't be more help.
by Jake ward on Monday March 15th 2010, 14:53
by Holly Bostick on Sunday March 14th 2010, 12:31
All of a sudden, I can't run FalloutLauncher.exe, or Fallout3.exe, because I get a Visual C++ Runtime error telling me that "an application has made an attempt to load the C runtime libraries incorrectly" (!!!) and that I should "contact the application's support team" (yeah, right).
So I uninstalled and reinstalled in the same .wine configuration; imagine my surprise when I got the same error trying to run FalloutLauncher.exe from the DVD. Setup runs fine, though, but when the installer tries to launch the game.... you guessed it.
I uninstalled again and renamed my .wine folder to create a new one, then attempted reinstall. With a clean .wine folder, FalloutLauncher.exe does run correctly, but the game itself does not; I can get to the first or second slide ("Please stand by" and sometimes the second test screen, but never the Beth logo screen) before a Microsoft "this application has encountered a serious error and has to close" messagebox shows up.
So I went back to my 'dirty' install, since the game wasn't working either way. I've reinstalled all of the Visual C++ runtimes with winetricks, as well as Windows Scripting host and common controls as well as common controls.ocx, but no joy.
Does anybody know if there's an override that I should install with Winetricks that would resolve this, or should I be submitting a bug on Bugzilla?
by Robert Gregory on Thursday March 18th 2010, 20:18
wineboot -i
wineboot -u
winetricks allfonts # I just like to have the fonts handy ;)
winecfg # set sane defaults (set windows version, make sure drives are detected correctly, etc.)
winetricks d3dx9 cc580 vcrun2008
# check elsewhere to download msasn.dll and xlive.dll
cp msasn1.dll .wine/drive_c/windows/system32
cp xlive.dll .wine/drive_c/windows/system32
winecfg # override msasn1 and xlive to native (and comctl32 to builtin)
wine /media/Fallout\ 3/setup.exe # install from DVD
wine gfwlivesetupmin.exe # say NO to .NET install
# download Games for Windows LIVE disabler
wine Games\ for\ Windows\ LIVE\ Disabler.exe
wine Fallout3_1.7_English_US.exe
winecfg # override comctl32 back to native,builtin
I launch the game using the following script (so that I can launch from an app launcher panel icon and still capture all the output to a log):
#!/bin/sh
_F3LOG=/var/tmp/`basename $0`.log
[ -e "${_F3LOG}" ] && rm -f ${_F3LOG}
fallout3_launch()
{
local _wineprefix="$HOME/.wine"
local _fallout3="C:\Program Files\Bethesda Softworks\Fallout 3\FalloutLauncher.exe"
wineboot
env WINEPREFIX="${_wineprefix}" wine "${_fallout3}"
return $?
}
fallout3_launch >${_F3LOG} 2>&1
exit $?
So if you name the script e.g. "myfallout3" (and make it executable) and run it, then the log would be created /var/tmp/myfallout3.log. And /var/tmp is not wiped out after a reboot, so you can still get to the log after a system hang :)
hope it helps.
robert.
by Robert Gregory on Thursday March 18th 2010, 20:38
[HKEY_CURRENT_USER\Software\Wine\Direct3D]
"VideoMemorySize"=512
I don't think that any other regedits are absolutely necessary though your mileage may vary.
by Holly Bostick on Sunday March 14th 2010, 12:31
All of a sudden, I can't run FalloutLauncher.exe, or Fallout3.exe, because I get a Visual C++ Runtime error telling me that "an application has made an attempt to load the C runtime libraries incorrectly" (!!!) and that I should "contact the application's support team" (yeah, right).
So I uninstalled and reinstalled in the same .wine configuration; imagine my surprise when I got the same error trying to run FalloutLauncher.exe from the DVD. Setup runs fine, though, but when the installer tries to launch the game.... you guessed it.
I uninstalled again and renamed my .wine folder to create a new one, then attempted reinstall. With a clean .wine folder, FalloutLauncher.exe does run correctly, but the game itself does not; I can get to the first or second slide ("Please stand by" and sometimes the second test screen, but never the Beth logo screen) before a Microsoft "this application has encountered a serious error and has to close" messagebox shows up.
So I went back to my 'dirty' install, since the game wasn't working either way. I've reinstalled all of the Visual C++ runtimes with winetricks, as well as Windows Scripting host and common controls as well as common controls.ocx, but no joy.
Does anybody know if there's an override that I should install with Winetricks that would resolve this, or should I be submitting a bug on Bugzilla?
by Robert Gregory on Monday March 8th 2010, 15:33
www.youtube.com/watch?v=YmFAyRwJ41g
Relevant bits are at 4:30 and 5:47
Every time I choose to "knock on the door" then a dialog appears with an elipsis ("...") and nothing further happens. The only way I can continue playing is to press escape and go back to a previous save, but I cannot finish this quest.
I checked the wine output, dmesg, and Xorg.0.log before trying to open the door and after exiting the game and there is no new output between the two events. Fallout3 wine output here:
pastebin.com/qnBmL5Zj
I have googled my heart out looking for reports of any similar issue, but I can't find one. Has anyone here had a similar issue with this quest in Fallout 3? I don't want to log it as a wine bug if I am the only one.
System specs as follows:
MOBO: Gigabyte GA-MA78GM-2SH (BIOS F11)
CPU: AMD Phenom II X4 940 AM2+ 3.0GHz
RAM: 8GB DDR2 800
Graphics: ATI RV730 PRO [Radeon HD 4650] (HDMI to Marantz receiver)
Display: Samsung 52" LCD TV (HDMI to Marantz)
Audio AMD RS780 onboard (SPDIF to Marantz)
OS: Ubuntu 9.10 Karmic Koala (using ALSA instead of Pulseaudio)
ALSA: 1.0.22 (from ppa.launchpad.net ubuntu ALSA repopsitory)
Wine: 1.1.39 (from ppa.launchpad.net ubuntu wine repopsitory)
(issue occurred with wine 1.1.37, 1.1.38 also)
Fallout 3: GFW DVD (not GOTY) version 1.0.0.12, patched to 1.7
(issue occurred both before and after 1.7 patch)
by Robert Gregory on Monday March 8th 2010, 16:02
libasound2 1.0.22-0ubuntu5~9.10~ricotz1 -> 1.0.22-0ubuntu6~9.10~ricotz1
wine1.2 1.1.39-0ubuntu1~karmic5 -> 1.1.40-0ubuntu1
Issue still occurs as described.
by Robert Gregory on Monday March 8th 2010, 16:10
by Robert Gregory on Thursday March 25th 2010, 15:53
by Mark Grant on Sunday September 12th 2010, 1:55
by Mark Grant on Saturday October 30th 2010, 0:49
by Dan Butler on Sunday March 7th 2010, 20:01
by Dan Butler on Tuesday April 13th 2010, 9:20
by Michael Griffith on Saturday February 20th 2010, 18:13
by Michael Griffith on Saturday February 20th 2010, 18:17
www.pastebin.com/m738a60d6
by blaise on Friday March 5th 2010, 23:17
by SiegeMachine on Friday February 12th 2010, 1:02
[ siegemachine@localhost Desktop]$ env WINEPREFIX=~/.wine-steam/ wine gfwlivesetupmin.exe
fixme:clusapi:GetNodeClusterState ((null),0x32ec3c) stub!
fixme:advapi:DecryptFileA "c:\\e98eea0cd3743c94c092\\" 00000000
fixme:advapi:LookupAccountNameW (null) L"siegemachine" (nil) 0x33f380 (nil) 0x33f384 0x33f378 - stub
fixme:advapi:LookupAccountNameW (null) L"siegemachine" 0x146ed8 0x33f380 0x14e028 0x33f384 0x33f378 - stub
err:msi:ITERATE_Actions Execution halted, action L"LaunchConditions" returned 1603
fixme:advapi:LookupAccountNameW (null) L"siegemachine" (nil) 0x6bd240 (nil) 0x6bd244 0x6bd238 - stub
fixme:advapi:LookupAccountNameW (null) L"siegemachine" 0x158568 0x6bd240 0x15f6b8 0x6bd244 0x6bd238 - stub
[ siegemachine@localhost Desktop]$
Can't install xlive *sigh*
by Michael Griffith on Saturday February 20th 2010, 18:20
by blaise on Tuesday March 2nd 2010, 18:50
by Robert Gregory on Monday March 8th 2010, 15:42
After installing gfwupdate and 1.7 patch, I set comctl32 back to (native, builtin) as it was before and everything is (more or less) fine.
I assume the howto says to "winetricks cc580" for a reason, but it got in the way of installing gfwupdate in my case. Perhaps this should be noted in the howto.
hope it helps.
by Kevin on Monday February 8th 2010, 6:49
working sounds are restricted to voices (and background music with the appropriate patches).
you will not hear bullet, collisions, jumps, environmental, menu, and other scripted sounds - only speech
by rgrwkmn on Friday February 12th 2010, 17:01
by GHales on Saturday February 13th 2010, 15:55
bugs.winehq.org/show_bug.cgi?id=21609
Unfortunately, the submitter didn't mark it as affecting Fallout 3, Oblivion or any other program it hits.
by NSLW on Wednesday February 17th 2010, 8:35
by Henry on Tuesday April 20th 2010, 17:56
by Kevin on Tuesday April 20th 2010, 22:04
pastebin.com/USExwnS6
assuming the link works, that's the net result
by Henry on Friday April 30th 2010, 0:29
by Jacob McGown on Friday April 30th 2010, 4:47
by hortonwho on Saturday February 6th 2010, 16:50
bugs.winehq.org/attachment.cgi?id=26095
Below is my regedit in wine.
[Software\\Wine\\Direct3D]
"DirectDrawRenderer"="opengl"
"MouseWarpOverride"="enable"
"Multisampling"="enabled"
"OffscreenRenderingMode"="fbo"
"PixelShaderMode"="enabled"
"RenderTargetLockMode"="auto"
"SoftwareEmulation"="disabled"
"UseGLSL"="enabled"
"VertexShaderMode"="hardware"
"VideoDescription"="NVIDIA GeForce 9800 GX2"
"VideoDriver"="nv4_disp.dll"
"VideoMemorySize"="512"
"VideoPciDeviceID"=dword:00000640
"VideoPciVendorID"=dword:000010de
by Skyggen on Sunday January 24th 2010, 20:48
Ubuntu wine has a ubuntu repo for karmic I used as Ubuntu Karmic is only 1.1.32 or something.
Then run winecfg just to generate files and default config. Make sure to navigate to the audio tab and select oss and the defaults should be fine.
Then follow the Games for Windows - Live Client as above making sure NOT to install .Net 3.5 because it breaks in wine as of yet.
A bit of clarity for the override.
winecfg -> libraries.
type msasn1 click add, then click edit set native only.
same for xlive.
Then get winetricks and run the sh winetricks d3dx9 cc580 command.
Install off the DVD. Fallout 3 has some sort of Securom BS which appears to break trying to copy it local and install.
Next download and install the 1.7 patch
static.bethsoft.com/fo3/patch/1.7/Fallout3_1.7_English_US.exe
Fallout 3 should launch at this point. Provided you have Disc 1 in the DVD drive and Wine can see it. Otherwise it will fail.
Next we need to get the FalloutLauncher working.
sh winetricks crun2005
Your FalloutLauncher will now be working.
To install the DLC just insert disc 2 into drive and install as normal. You still need disk 1 in the drive when you start it again or it will fail.
Sound is weird unless you install alsa-oss
apt-get install alsa-oss fixes this.
I run fallout with the following command:
aoss wine "C:\Program Files\Bethesda Softworks\Fallout 3\FalloutLauncher.exe"
Karmic Koala
2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 x86_64 GNU/Linux
winehq repo wine v.1.1.37
.Net 3.5 and Securom make this a pain.
by Skyggen on Sunday January 24th 2010, 20:53
by NSLW on Saturday January 30th 2010, 7:46
by Skyggen on Saturday January 30th 2010, 16:20
by Amarao on Saturday January 23rd 2010, 16:17
So, go to Fallout3 directory and run it directly ./Fallout3.exe (after settings have been setted in Launcher).
by wmute on Sunday January 24th 2010, 6:09
by Piotr on Tuesday June 15th 2010, 7:03
by Amarao on Saturday January 23rd 2010, 15:55
I solve this problem with using a windowed mode (in FalloutLauncher). I think this similar to problems of many games, which one see not a two xrandr screens, but a single very wide screen.
by William Lightning on Sunday March 28th 2010, 16:29
by wmute on Friday January 22nd 2010, 14:11
www.fallout3nexus.com/downloads/file.php?id=1086
and then copying the xlive.dll from my system32 to fallout3 directory.
That got me to the main menu. Now, if I could just get sound working ...
by evilgoblin on Wednesday December 9th 2009, 20:46
www.microsoft.com/games/en-us/live/Pages/livejoin.aspx
(the exe gfwlivesetupmin.exe not install fine, i just go /windows/temp/dx.... and execute all files to install ..)
i uploading video show like work....
www.youtube.com/watch?v=oFnEv3PPNew
by airtonix on Thursday January 21st 2010, 23:25
1) its vague
2) doesn't actually describe how you install Games for windows live.
3) the video is terrible
by Per Johansson on Monday December 7th 2009, 17:35
Ubuntu 9.10 Studio 32-bit w. 2.6.31-16-PAE-kernel
Nvidia 195.22, compiled on system
Wine 1.1.34, compiled on system, no patch but a lot of "winetricks" and GamesForWindowsLive3 + .net 3.5 SP1, using Windows 7 as alias, msasn1.dll added in system-folder
DX9 August 09 using the 3D3 registry-settings on this page
OSS 4.2, compiled on system
Fallout 3 installed through Steam(running on Wine), patched to 1.7.
The game runs fine and is very playable with good framerate and all menus are functional, and the graphics is great @ 1280x1024 @ highest settings, can't see any difference from Windows except a few flickering shadows sometimes.
E8400, 4GB(PAE), 9600GT 512MB
/Per
by airtonix on Friday January 22nd 2010, 4:50
Without it, how does it affect the running of fallout3?
(ie use default alsa or oss options)
by Sam on Saturday November 21st 2009, 8:51
I thought that maybe there might be a way I can get a copy of the files from my windows partition.
by Foone on Sunday November 22nd 2009, 13:10
One should try "Sandboxing" the Retail and compare differences in files from a update, to find out which files are necessary (game/story, dll fixes)
by Carlos Rodriguez on Friday November 20th 2009, 11:02
I use same register keys for nvidia but modify some values and copy ati files from windows/system32 installation folder to windows/system32 folder in wine directory
Also copy microsoft.net, fonts and system folder from win installation to windows folder in wine
Run regedit and browse to: Current_user/Software/Wine/Direct3D. If Direct3D key doesn’t exist, create it. You may want to set following values:
This is for ATI:
"DirectDrawRenderer"="gdi"
"VideoMemorySize"="512"
by Carlos Rodriguez on Wednesday November 18th 2009, 10:34
I use same register keys for nvidia but modify some values and copy ati files from windows/system32 installation folder to windows/system32 folder in wine directory
Also copy microsoft.net, fonts and system folder from win installation to windows folder in wine
I have installed in windows catalyst 9.11
Run regedit and browse to: Current_user/Software/Wine/Direct3D. If Direct3D key doesn’t exist, create it. You may want to set following values:
This is for ATI:
"DirectDrawRenderer"="gdi"
"OffscreenRenderingMode"="fbo"
"RenderTargetLockMode"="enabled"
"UseGLSL"="enable"
"VideoDescription"="ATI Radeon HD 4350"
"VideoDriver"="ati3duag.dll"
"VideoMemorySize"="512"
by NSLW on Friday November 20th 2009, 3:01
by oiaohm on Monday November 9th 2009, 7:11
bugs.winehq.org/show_bug.cgi?id=15839 that is closed
The patches are not related to the issue what caused this bug to be opened so yes it correct to be closed.
Even worse there is more than 1 solution to the problem.
bugs2.winehq.org/attachment.cgi?id=24289
bugs2.winehq.org/attachment.cgi?id=24230
Are two different paths around problem that are not being tested.
Really a new bug needs to be created for this issue or exist bug found covering the issue. Applications seeing the wrong video card information.(Ok better name require) Message posted on to end of bug 15839 pointing to the new bug over this issue. Links to the attachments that works need to be in the bug truly targeting this issue.
At no time should any attachment in bugzilla be disconnected from its bug number it was created on. Makes finding it for updates hard. Or in cases that a bug was valid closed to get in there to find out about any other patches created related that did not relate to why the bug was opened in the first place.
Current patch being used need a code clean up. Without a open bug number this is kinda not going to happen. Without a open bug number patch is not on any path to get merged. Only open bug numbers can be attached to applications to get voted to show need as well. Its being lost to the void.
This has just been process breakdown. Lets see if we can get it back on track.
by Mikael Ã…kersund on Tuesday November 10th 2009, 13:04
According to the comments in bug 15839 Fallout3 should play just fine with regular unpatched wine since 1.1.32.
The description/name of bug 15839 was never updated but it was about the FalloutLauncher not detecting graphic card capabilities properly, which according to the comments now are fixed.
The name of bug 15839 should have been changed, or it should have been closed and a new one opened up a long time ago.
by NSLW on Friday November 13th 2009, 15:16
by Brettskeh on Saturday November 7th 2009, 0:40
Edit your FalloutPrefs.ini
Under [Controls] add the following lines-
fForegroundMouseAccelBase=0
fForegroundMouseAccelTop=0
fForegroundMouseBase=0
fForegroundMouseMult=0
This disables mouse acceleration and seems to fix freaky mouse behaviour for the most part. Enjoy!
by ehren on Tuesday November 3rd 2009, 20:03
I have a Athlon x2 64 processor, a EVGA 9800GT video card.
Thanks for your help.
by ehren on Tuesday November 3rd 2009, 21:36
DaweyYT has done on his youtube video, to install using play on linux, except I used patch version 1.7, and it will not launch or show up at all. do you think the GOTY disc could have special security features on it like the Oblivion GOTY? if so how do I get around it?
www.youtube.com/watch?v=BnS-gf6FLLY
Thanks.
by NSLW on Wednesday November 4th 2009, 9:31
Does Fallout 3 launcher starts?
BTW. DaweyYT tested it on plain English Fallout 3 (not GOTY)
by Sam on Wednesday November 4th 2009, 15:32
Download the patch and add this patch to the folder. Once there cd in terminal to that directory then run:
patch -p1 > patch-name.diff
Patch-name being the name of the patch file when you downloaded it.
After run:
./configure
then:
make depend && make
then:
make install
thats how you install from source, its quite easy actually once you get the hang of it
by ehren on Wednesday November 4th 2009, 16:58
Thanks for your response.
by Sam on Wednesday November 4th 2009, 17:51
and it will save it as the patch :)
It will replace the other wine but it won't break your games. You are basically taking wine, adding a little addition to make it produce a workaround and installing it :), source or deb it is all wine.
prdownloads.sourceforge.net/wine/wine-1.1.32.tar.bz2
that is the address for the source code. The wine_source_dir is the folder to which you extract that archive.
also uninstall (select to completely remove) your previous wine before installing the patched.
by ehren on Wednesday November 4th 2009, 18:38
The HowTo says "Download it, paste it to wine sources dir and type
patch -p1 < filename"
Where do I paste the new patch file I downloaded? where is the "wine sources dir" is it in the downloaded and extracted wine source code? where do I type "patch -pl
by Sam on Wednesday November 4th 2009, 20:28
by ehren on Sunday November 8th 2009, 4:38
I believe my previous problems were mostly caused by wine not compiling correctly in my 9.04 64 bit OS, because a package needed for installation was not present.
How are you supposed to install the DLC from the other disk?
Thanks, at least I can play the game now.
by Sam on Monday November 9th 2009, 4:44
I haven't got DLC working yet and mines kinda bad since all my DLC is on Games for Windows Live so I can't get it until they somehow sort that out :(.
by ehren on Wednesday November 4th 2009, 21:50
But on the bright side now the Wine window pops up for a second when I run Fallout3.exe.
The window appears with a picture in the background, starts to play music, then the wine error message appears and tells me to close it, when I launch the FalloutLauncher.exe.
I also tried Play on Linux again, with different wine versions in the "environment" tab, one of them gives me the error message "3d accelerator missing, suggest you install it"
by ehren on Thursday November 5th 2009, 21:36
"configure: libgsm 32-bit development files not found, gsm 06.10 codec won't be supported.
configure: libmpg123 32-bit development files not found (or too old), mp3 codec won't be supported.
configure: Finished. Do 'make depend && make' to compile Wine.
ehren@ehren-desktop:~/Desktop/wine-1.1.32$"
I can't figure out how to fix the problem, or what it means; what should I do, has anyone else encountered this when compiling wine, or is there a work around?
Thanks
by Tuomas on Thursday November 5th 2009, 10:16
Scrolling gets harder, though, but then again you don't need to scroll much with a large resolution.
by ehren on Monday November 9th 2009, 17:09
I did get Fallout 3 working right, except I cant load any mods, or the official DLC from the second disc. If you have any ideas, it would be most appreciated, BTW I am running it in the "high" setting very smoothly.
Also, a absolute fix for it saying no sound device detected, and it usually loads sound correctly. when launching "FalloutLauncher.exe" is to remove the audio file called "MainTitle.wav", I think you will have to just move the file "out" of its normal folder (might have a little lock indicating write/delete protected.
by Tuomas on Saturday October 31st 2009, 6:35
I define the WINEPREFIX variable to the wine folder created with playonlinux, define WINEDEBUG=-all, and execute `wine Fallout3.exe' or `wine FalloutLauncher.exe' in the Fallout3 folder. The launcher seems to require the DVD.
The mouse was behaving strangely until I defined the WINEDEBUG=-all.
by NSLW on Sunday November 1st 2009, 9:48
by Tuomas on Monday November 2nd 2009, 2:01
by NSLW on Monday November 2nd 2009, 3:08
This isn't fixed on Wine so it don't work on PlayOnLinux.
Patches for 1.1.31 were compiled on Fedora 11 and patches for 1.1.32 were compiled on Debian Etch, so they should have more compatibility with most distros.
Crash at starting new game were probably caused by wine not being patched. This could happen if you had
"Default Wine version to run wine programs with PlayOnLinux" set to something else than "System"
by Tuomas on Monday November 2nd 2009, 10:36
>This isn't fixed on Wine so it don't work on PlayOnLinux.
Works with patched 1.1.32.
>Crash at starting new game were probably caused by wine not being >patched. This could happen if you had
>"Default Wine version to run wine programs with PlayOnLinux" set to >something else than "System"
By something else you mean patched wine 1.1.31?
Anyway, I got both the launcher and the game working by using playonlinux only to install. Then I got rid of playonlinux and the ubuntu packaged wine.
by NSLW on Monday November 2nd 2009, 12:42
By e.g. plain Wine 1.1.31
>Anyway, I got both the launcher and the game working by using >playonlinux only to install. Then I got rid of playonlinux and the >ubuntu packaged wine.
You hadn't to remove anything. You could compile patched Wine yourself and use it in POL.
by Sam on Wednesday November 4th 2009, 15:40
by Sam on Wednesday November 4th 2009, 15:44
by Tuomas on Thursday November 5th 2009, 10:03
I'm using pulseaudio with patched wine 1.1.32 without any problems.
by cosmophobia on Saturday October 24th 2009, 3:15
another question. : )
Fallout 3 works now with a self-compiled wine.
I tried enabling antialiasing in the gameoptions & forcing it through
the NVidia-driver, but it won't work.
Antialiasing works with other wine-games.
Do you have any idea how to get it working with Fallout 3 too!?
My system: Mandriva 2009.1 x86_64 @ AMD Phenom X4 940, 4GB RAM, NVidia GeForce GTX 260 (896 MB RAM)
by NSLW on Saturday October 24th 2009, 6:47
by cosmophobia on Saturday October 24th 2009, 12:24
In Current_user/Software/Wine/Direct3D Multisampling is set to enabled.
by cosmophobia on Saturday October 24th 2009, 12:38
err:d3d:IWineD3DImpl_CheckDeviceMultiSampleType Unable to color bits for format 0x25, can't check multisampling capability!
by NSLW on Saturday October 24th 2009, 12:44
by cosmophobia on Sunday October 25th 2009, 7:01
It's ugly withpout Antialiasing. : (
by cosmophobia on Saturday October 17th 2009, 12:37
I tried installing Fallout 3 with PlayOnLinux (3.7/patched wine 1.1.31) and without (unpatched wine 1.1.31 without any tweaks). In both cases the game installs and starts fine.
When I try to start a new game (or load a downloaded one) the game crashes after loading a few secounds.
I tried a patched (1.7) and unpatched game. I tried using cracks. It's always the same.
My gameversion is german.
My system: Mandriva 2009.1 x86_64 @ AMD Phenom X4 940, 4GB RAM, NVidia GeForce GTX 260 (896 MB RAM)
Any ideas, what should I try to do next!?
by NSLW on Sunday October 18th 2009, 3:16
bUseThreadedAI=1
iNumHWThreads=2
in "~/My Games/Fallout3/FALLOUT.INI"
BTW. What is your distro?
by NSLW on Sunday October 18th 2009, 3:16
by cosmophobia on Sunday October 18th 2009, 4:33
by NSLW on Sunday October 18th 2009, 5:18
by cosmophobia on Sunday October 18th 2009, 8:53
I have no idea.
Ps: This is not a general problem, Age of Empires 3/The Sims 3 are working without problems.
by Adrielus on Tuesday October 20th 2009, 11:39
wine: Unhandled page fault on read access to 0x00000000 at address 0xaddf7b (thread 002f), starting debugger...
This is on the self compiled and patched version of 1.1.31. PlayonLinux's 1.1.31 page faulted on starting fallout3.exe, until I copied wined3d.dll.so from the 1.1.31 playonlinux prefix, then it is the same results as above.
I've modified the .ini to support multiple cores.
All attempts have been made using the 1.7 patch of the game, but everything I've found suggests it should be okay to run this version.
I'm running out of ideas, my system is as follows:
AMD quad phenom, Geforce 9800 GT w/ 512MB, 4GB ram, running Ubuntu 9.04.
Any help is appreciated. Please lemme know if you need more information.
by NSLW on Thursday October 22nd 2009, 12:21
www.playonlinux.com/en/topic-2772-2.html
Instruction how to use it is in last post (Thursday 22 October 2009 at 13:39) If this version works then there will be no problems in future versions with Fallout 3 and POL for those who get errors.
by cosmophobia on Friday October 23rd 2009, 12:47
But I was always trying the patched wine version vom POL, so I compiled my own: Now it works.
by remo on Monday March 1st 2010, 11:47
Same here, installed with PlayOnLinux, wine 1.1.39 without any tweaks.
I managed to get through few scenes by switching off save in Options->Gameplay.
Game itself runs fine, no lag, funny shadows on people's faces.
Problem starts outside Megaton, any time I am trying to Enter (E) game crashes (Loading screen, progress circle not moving)
Can't close it, nothing (although I can see my linux cursor)
Only Ctrl+Alt+Backspace helps
My config
Intel E6400 C2D
4GB (800)
ATI 3650 512
---------------------------
next challenge: GTA4
by RC on Tuesday August 11th 2009, 23:07
With windowed mode on:
Failed to initialize renderer.
Windowed mode not supported on this Adapter.
With windowed mode off:
Failed to initialize renderer.
Your display doesn't support the selected resolution. Please set a
different resolution in Fallout 3's Launcher under 'Display Settings'.
(It shows this regardless of what resolution I set in FalloutPrefs.ini, including the Fallout defaults and my screen's native resolution.)
Versions: Fallout 1.7, wine 1.1.27 (built from source with the above patch applied), and with the following installed from winetricks: d3d9, vcrun2005, and vcrun2005sp1 (for a few required DLLs). Using XQuartz 2.3.3.2 on a Mac.
by DL on Friday July 31st 2009, 0:11
by John on Sunday August 2nd 2009, 9:50
by Jari Vetoniemi on Sunday June 14th 2009, 12:19
Heres how:
1) I checked my shaderpack in renderinfo.txt file
2) Replaced it with Shaderpack019 (You may try others also if 019 wasn't good)
3) Searched fallout.ini and falloutprefs.ini for word decal
4) Every occuranse of the word Decal i setted to 0
5) If you have Quad Core or more than 2 cores:
5.2) Make bUseThreadedAI to 1 in Fallout.ini
5.3) Insert this after it then iNumHWThreads=2
If the game still crashes at startup you have to put useFaceGenHeads=0 in fallout.ini, this disables heads, but the game will work. This is because Fallout 3 has poor hardware compatibly and don't work well with all hardware. Now the game works just like under Windows with same proplems and bugs. You still may get flickering after playing some hours and slowdowns and rare crashes, but this happens also in Windows. I play with Very High settings btw =)
I have Q6600 and nVidia GForce 8600 GT. Hope this helps.
Btw, i really suggest installing latest version of PlayOnLinux and install Fallout 3 with the script that is already in the POL Repo. Because this game can easily break compatibly with your other Wine programs. And the POL Script just works after you've done the stuff above.
by Jari Vetoniemi on Sunday June 14th 2009, 12:24
Also if you can't get to the Vault Escape part (Crashes at the beginning of game in some of the "After xx years" things) Get the save at this link. Don't worry it is at the Vault entrance where the game gives change to change your race, name, skills etc..
www.fileplanet.com/194401/190000/fileinfo/Fallout-3---Sexy-Pandora
by Shannon T on Monday March 30th 2009, 11:42
"Right after the nurse leaves and the mother says "we did it" the game becomes idle, only the e button works making the baby cry, the dad says nothing, nor leaves and nothing happens. "
And reading from a post from other forum, one of the guys said something like "you can tell straight away whether an install went right or wrong, If it detects it as all high but no water and no certain things, then u know its a goner." which is exactly happening to me, but it's a complete different story when the game is installed into my friend's PC, he's playing it right now.
i'd being trying and reinstalling for the 6th time so i dont know what to do.
while I was trying to find a solution, i stumbled across Wine
so i was just wondering, should i do the "Wine" thing? with the reg and stuff which is shown above the first post?
by Tymoteusz Paul on Monday March 30th 2009, 11:52
Also please fill a bug report since this looks like new issue.
by Jizaboz on Saturday April 25th 2009, 11:18
I am using a Geforce 9400 GT.
by Brettskeh on Saturday July 4th 2009, 9:18
I'm running directly off of my windows HD with exported registry. Running Wine 1.1.25 compiled with WinD3D fix as suggested. Vanilla 1.0 Fallout.
by Brettskeh on Saturday July 4th 2009, 9:29
by Jim Robert on Saturday December 27th 2008, 18:09
support.securom.com/fallout3/
good luck!
by Jim Robert on Saturday December 27th 2008, 18:16
www.securom.com/support/customers/bethesdasoftworks/Fallout3_t0030/FalloutLauncher.zip
by shnull on Wednesday November 19th 2008, 1:48
If anyone's interested, i wrote this perl script that helps me hack the terminals in (mostly two but) three passes.
Find it here :
paste.ubuntu.com/74200/
feel free to adapt, send me a msg if you do, if you know perl you can get the routine from it, if you don't, well, take some time, its a useful scripting lng when using linux, though not one of the youngest,
Keep up the good work , winers ;-)
by Milan Troller on Saturday November 22nd 2008, 11:15
Please, post everyting you can.
by Tymoteusz Paul on Saturday November 22nd 2008, 13:36
by Milan Troller on Saturday November 22nd 2008, 15:06
by Mirek Slugeň on Tuesday November 18th 2008, 1:03
link: bugs.winehq.org/attachment.cgi?id=17342
by MaraST78 on Wednesday November 26th 2008, 14:47
by Mikael Ã…kersund on Tuesday November 4th 2008, 8:13
To get past the New Game crash edit Documents/My Games/FALLOUT.INI and set bUseFaceGenHeads=0
You'll be able to see the intro movie, your birth, customize your character and take your first steps. All characters won't have any heads and the game is going to crash soon after that.
There's an effort over at www.oldblivion.com/sm/index.php?topic=5831.0 to rewrite Fallouts shader effects to SM 2.0, much in the same way as was done with OldOblivion.