Fallout: New Vegas

Modified the value within ini file to disable joysticks and make background mouse available, but still hard to move the mouse and cursor, even the player camera.

assuming you have followed my other notes to setup symlinks:

$wine --version
wine-4.17 (Staging)

$ WINEPREFIX="/lutris/xedit" winetricks list-installed|grep -P '^\w+$'|tr '\n' ' '
andale arial comicsans courier georgia impact times trebuchet verdana webdings corefonts cmd remove_mono winxp dotnet40 win7 autohotkey vcrun2003 vcrun2005 vcrun2008 vcrun2010 d3dx9 remove_mono dotnet45

# note 1: pretty sure i just did corefonts initially and it is not collapsing the individual fonts back to it
# note 2: i never explicitly set remove_mono so that's probably a side-effect of installing dotnet via winetricks

------------------------------------------------
#works for Vortex (assuming you have proper symlinks set up for gamedir, game ini's, and plugin.txt/loadorder.txt)
#(I miss a few MO2 features but I like it a lot better than FOMM... has built-in LOOT and archive invalidation)
#see github.com/Nexus-Mods/Vortex/releases/tag/v1.0.3
usr/bin/env WINEPREFIX="/lutris/vortex" "/usr/bin/wine" "C:/Program Files/Black Tree Gaming Ltd/Vortex/Vortex.exe"

#works for FNVEdit (assuming you have proper symlinks set up for gamedir, game ini's, and plugin.txt/loadorder.txt)/
#see github.com/TES5Edit/TES5Edit/releases/tag/xedit-4.0.2
usr/bin/env WINEPREFIX="/lutris/xedit" "${HOME}/.local/share/lutris/runners/wine/3.0-i386/bin/wine" "C:/SteamGames/steamapps/common/Fallout New Vegas/FNVEdit.exe";

#works for Merge-Plugins (assuming you have proper symlinks set up for gamedir, game ini's, and plugin.txt/loadorder.txt)/
#see www.nexusmods.com/skyrim/mods/69905
usr/bin/env WINEPREFIX="/lutris/xedit" "${HOME}/.local/share/lutris/runners/wine/3.0-i386/bin/wine" "C:/merge-plugins/MergePlugins.exe"

# GECK - results in crash on launch (pagefault):
WINEPREFIX="/lutris/xedit" "/usr/bin/wine" "C:/SteamGames/steamapps/common/Fallout New Vegas/Geck.exe"

# GECK - results in crash on launch (pagefault):
WINEPREFIX="/lutris/xedit" "/usr/bin/wine" "C:\\SteamGames\\steamapps\\common\\Fallout New Vegas\\Geck.exe"

# GECK - results in crash on launch (pagefault):
WINEPREFIX="/lutris/xedit" "/usr/bin/wine" start "C:/SteamGames/steamapps/common/Fallout New Vegas/Geck.exe"

# GECK - results in crash on launch (pagefault):
WINEPREFIX="/lutris/xedit" "/usr/bin/wine" start "C:\\SteamGames\\steamapps\\common\\Fallout New Vegas\\Geck.exe"

#Works to launch GECK (assuming you have proper symlinks set up for gamedir, game ini's, and plugin.txt/loadorder.txt):
#Install from Steam or see geck.bethsoft.com/index.php?title=Garden_of_Eden_Creation_Kit
WINEPREFIX="/lutris/xedit" "/usr/bin/wine" start /d"C:/SteamGames/steamapps/common/Fallout New Vegas" "Geck.exe"

I should also mention that before you try anything in my previous comments, use the original launcher > option and change Screen effects to None (e.g. disable HDR and bloom). This made my game significant;y more stable.

I am also using quite a few NVSE plugins with relatively few issues:
JIP LN NVSE
MCM
UIO
Unnecessary Tweaks
Stewie Tweaks
NVSE Enhanced Camera
NVAC (including the DisableProcessWindowsGhosting.dll)
Console Paste Support

When I have only these enabled (e.g. no random mods I am testing), then I have almost no issues. these can all be found on the nexus

UPDATE - really really wish winehq would allow editing posts

3) I copy/pasted from my afkmods post, got a phone call, and forgot to finish replacing the folder names.... for vortex, it should be /lutris/vortex instead of /lutris/xedit unless you plan for them to share the same wineprefix. I prefer to keep separate wineprefixes on mine but a shared one would probably work fine. Anyway, sorry for any added confusion.

$ cd /lutris/vortex/drive_c
$ ln -s '/lutris/winesteam/prefix64/drive_c/Program Files (x86)/Steam' SteamGames
$ cd "/lutris/vortex/drive_c/users/$USER/My Documents/My Games"
$ ln -s '/lutris/winesteam/prefix64/drive_c/users/$USER/My Documents/My Games/FalloutNV" FalloutNV
$ cd "/lutris/vortex/drive_c/users/$USER/Local Settings/Application Data"
$ ln -s "/lutris/winesteam/prefix64/drive_c/users/$USER/Local Settings/Application Data/FalloutNV" FalloutNV

UPDATES (since winehq doesn't let me edit past comments):

1) For the 4GB patch.

In Lutris, you can actually have wine simulate the 4gb patch for you now. Update to latest lutris and make sure that a recent lutris/ge/tk build of wine is installed. Then click the configure button for wine steam. Under runner options, select the recent lutris/ge/tk wine build. Then under System settings, scroll down to Environment Variables, click Add and enter WINE_LARGE_ADDRESS_AWARE=1
Last, apply the same settings to any game-specific steam launchers (e.g. Fallout NV).

For Proton users, try this (untested):
PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%

3) For Vortex deployments to work correctly, you will need to setup symlinks for 3 folders: your game installation folder, the folder that contains your game ini, and the folder that contains your plugins.txt.
e.g. from a separate wineprefix ON THE SAME PARTITION:

# note: I moved my ~/.local/share/lutris/runners/winesteam folder to /lutris/winesteam
$ cd /lutris/vortex/drive_c
$ ln -s '/lutris/winesteam/prefix64/drive_c/Program Files (x86)/Steam' SteamGames
$ cd "/lutris/xedit/drive_c/users/$USER/My Documents/My Games"
$ ln -s '/lutris/winesteam/prefix64/drive_c/users/$USER/My Documents/My Games/FalloutNV" FalloutNV
$ cd "/lutris/xedit/drive_c/users/$USER/Local Settings/Application Data"
$ ln -s "/lutris/winesteam/prefix64/drive_c/users/$USER/Local Settings/Application Data/FalloutNV" FalloutNV

5) For BSA extraction, I actually had quite a few issues using BSAopt in practice and would like to retract my recommendation for it. What has worked better for me for FONV (I used it for extracting files in TTW setup) is:
jonwd7's B.A.E. - Bethesda Archive Extractor
www.nexusmods.com/fallout4/mods/78/?

I set mine up in the same wineprefix I used for my lutris steam games (e.g. /lutris/winesteam/prefix64/drive_c/bae), copied the BSAs to that folder, then launched through wine. Once open, File > Open File lets you select multiple BSAs and extract them all in one go.

NEW:
7) Using xEdit / FNVEdit also works although you will need to setup a separate 32-bit wine prefix as described for vortex and then run it under wine v3.0. More in-depth instructions can be found on this page:
www.afkmods.com/index.php?/topic/5509-xedit-and-linux-tutorial/

forgot to mention a few other things

4) I was never able to get LOOT (Load Order Optimization Tool) working natively or under wine but Vortex has a LOOT module built-in so if you use that, then you should be good for load order.

5) If you should ever need to extract BSA files it can be tricky because a lot of the mod utilities don't work too well from wine.

www.nexusmods.com/skyrim/mods/247?tab=files

Manually down the first one (BSAopt - Date uploaded=06 Jun 2012, 7:24PM, File size=960KB, Version=1.6.3)
Create a 32-bit wine prefix (not sure if you need to install the stuff i list but including what i used just in case):
env WINEPREFIX="/path/to/new/32bit/wine/pfx" WINEARCH=win32 wine wineboot;
env WINEPREFIX="/path/to/new/32bit/wine/pfx" winetricks cmd comctl32 corefonts dotnet45 msxml6 vcrun2017 win7;

create a working dir like "bsa", extract the archive somewhere under that, then copy your BSA file to the extracted folder and run winecmd:
cd /path/to/new/32bit/wine/pfx/drive_c/bsa/BSAopt-247-1-6-3/
env WINEPREFIX="/path/to/new/32bit/wine/pfx" wine cmd
cd /d "C:\bsa\BSAopt-247-1-6-3"

if you try to open the file/folder dialog from the gui then it will crash. but you can pass the bsa as a commandline arg and it will open it up just fine. i was able to open it this way and then extracting from the gui worked. e.g.
C:\bsa\BSAopt-247-1-6-3>"BSAopt x32.exe" "Fallout - Misc.bsa"

6) When you first start FO:NV BEFORE modding / patching / installing NVSE / etc, if you get a crazy mouse cursor that doesn't want to work correctly, this fixed it for me:

Edit your ..../Steam/steamapps/common/Fallout New Vegas/Fallout_default.ini (note I had initially tried in Fallout.ini / FalloutPrefs.ini under My Docs folder but those values kept getting wiped out and reset. when i made the change in this file it finally stuck). Change the Controls section to look like this (bBackground Mouse and all the fForegroundMousexxx values; anything else can be left as-is)

[Controls]
bAlwaysRunByDefault=1
bBackground Mouse=1
bBackground Keyboard=1
fForegroundMouseAccelBase=0
fForegroundMouseAccelTop=0
fForegroundMouseBase=0
fForegroundMouseMult=0

hopefully this helps somebody else out there; here are a few things I've found so far:

1) for the 4gb patcher, this one works from wine (32-bit wineprefix, i think i had dotnet45 vcrun2017 win7):
www.nexusmods.com/newvegas/mods/62552/

the ntcore 4gb patch did NOT work for me (I got steam pop-ups that the game failed to launch)

I'm hoping to eventually replace patching utilities with the new LLA flag in lutris.
If I succeed, will update here: forum.winehq.org/viewtopic.php?f=8&t=32854

2) NVSE works fine. Back up FalloutNVLauncher.exe and then rename nvse_loader.exe to FalloutNVLauncher.exe; should work for launching from steam (I am using it via lutris/wine but it ought to work for proton too)

3) Unfortunately, Mod Organizer 2's virtual filesystem does not work correctly without fairly involved workarounds (I did not test the wokarounds). Vortex does appear to work fine as long as you have it on the same physical partition (symlinks on the same partition work but symlinks to something on a different drive or partition fail to deploy). I used the lutris install from the site to set up a prefix for an older version of Vortex then manually deleted the install folder and run the v1.0.0 release instead. So far it seems to be mostly working fine. While I greatly prefer MO2's user interface over Vortex's, Vortex actually works on Linux so can't complain too much. One other nice thing about Vortex is that you can close it after deploying instead of needing to keep it in memory like MO2 and you don't need to launch games from it like in MO2, so launching from steam (wine or proton) should be fine. I did not bother testing FOMM as I wanted a mod manager that I could use for The Elder Scrolls games also.

my setup:
OS: Mint 19.2
System wine: wine-4.15 (Staging)
FO:NV installed via Lutris v0.5.3 using Steam wine
cpu: amd 990fx
gpu: nvidia 970
driver: nvidia-driver-430
os drive on a ssd
lutris / steam games / vortex all installed on the same partition on a large traditional hdd

When enabling HDR, I get lights popping at me through the terrain. This is really noticeable at the start of the game, as when walking out of Doc Mitchell's house and making a start down the road you get quick bursts of light popping at you from just above the road. I've seen this in other areas of the game too.

Without HDR enabled some of the lighting in some places looks kinda goofy, be interesting to know if anyone has managed to fix this or if it's a Wine bug.

I'm not sure where to put this and I'm not sure if this belongs on the bug list. If anything, I was hoping that someone had similar problems and/or this problem was encountered and fixed. My problems pertain to Fallout: New Vegas and is the reason why I am commenting here. I am using:

an Intel core i5 6600k with a
Gtx 1070 graphics card.

An additional information is that I a mod called YUP (the unofficial patch of Falllout: New Vegas). But I highly doubt the issue stems from this mod as the issues persisted before it.

I'm not sure if more information is required; so anyone who is willing to help, please ask me any questions to help me deal with my issues.
Now onto the issue:
Currently, the game is running smoothly and there are no immediate problems, but the bigger of my issues come later during my sessions. For some reason, at some point in the session, there are times and moments when I aim my camera to certain places in the world, the entirety of my HUD, the crosshairs included, just disappears; and the ambient brownish lighting that permeates Fallout: New Vegas seems to lift from my camera when I look at these zones. And while looking at these zones and I pull up my pip-boy, the background disappears and is left completely black. It's nothing permanent and as long as I look away from these seemingly arbitrary areas, then it isn't really that much of an issue. But that said, huge chunks of the world are part of the "zones". And also, as long as I restart the game, then the problem disappears until after some period of time. I am hoping that someone can help me out with this as it is extremely annoying to have to end a play session in order to be able to even see what I am pointing at and how much health I have and where my AP is at.

The secondary, and , imo, the lesser of the problems is that VATS refuses to work properly. When I first started playing, what occured when I tried to use VATS was that no matter how close I got to my enemies, I would always have 0% of hitting them. Then, the problem grew to where whenever I use VATS, not only do I always get 0%, but the entire world goes black. And if I were to rapidly switch VATS off and on, there was a chance that the world remains dark. The reason why I believe this to be a lesser issue when arguably it could be the bigger one is because I think I have found a workaround. I believe I have narrowed down the issue thanks to someone who seemed to have a similar problem in Fallout 3

Here is the forum where I got the idea: forums.nexusmods.com/index.php?/topic/161898-vats-only-gives-a-0-chance/

I have narrowed it down and the issue seems to be related to the anti-aliasing, because when I lowered it down from the max anti-aliasing, the VATS worked again - momentarily. I have currently turned off the anti-aliasing settings to see if that would completely fix the problem. So far, I have no encountered the problem again, but I have yet to play long enough due to the previous problem.
Please help me. And thank you very much in advance.

I'm getting the same graphical issue as you, using the AMDGPU open drivers with an RX 480. This suggests it's not related to whether or not you're using and NVIDIA or AMD driver. I tried isolating the graphical problem through the video settings, but couldn't find any one thing that prevented the same graphical glitch from occuring.

As of 2.11 staging, no winetricks or overrides are needed; the game will install and run.

I made an account just to post this because I'm quite excited by the possibilities. GOG just released Oblivion, Fallout 3, and Fallout: New Vegas, all DRM-free, which could solve the problem of Steam conflicting with the LAA flag. The guys at GOG even made a Wine wrapper, which could simplify installation, although I'm not sure how it might change modding. Also, the games are on sale for a few more days, with New Vegas being (I think) $10. I can't try applying the fix right away, but will in a week or so, in case anyone else wants to test it first. This is exciting!

I installed in my Fallout 3 wineprefix, it works perfectly.

Thanks for the info! I tried it in the GOG guy's wine wrapper, and found the same. I was also told that the executable is already Large Address Aware, hurray!

I see a lot of people here who are commenting on the issues of running this game on higher graphics settings and I believe none of you are actually aware of what the problem, most likely, is.

About two years ago I made a review for Fallout 3, and a video which went along with it (www.youtube.com/watch?v=j9OhaGEhj5I), demonstrating some of the issues with the game and how to fix them. Fallout 3 runs on the same engine as Fallout New Vegas does, and the same issues which exist for Fallout New Vegas also exist for Fallout 3, in example textures popping out, weapon and statistics regarding health and weapons disappearing, black screens, sudden changes in color etc.

Wine tells us that it is running out of memory. The reason Wine is running out of memory has to do with a developer choice of not making the game large address aware, that is to say, wine cannot use more than 2GB of system memory, the consequence is frequent crashes and or strange occurrences like those you have likely experienced.

For Fallout 3 all this can be easily solved by applying the LAA flag to Fallout 3 either manually by a suitable software or with the help from third party software downloadable from the Nexus. When the LAA flag is set, there is no limit to the amount of mods Fallout 3 can handle, the game stops crashing and all graphics settings work properly.

The same thing does unfortunately not work properly for Fallout New Vegas due to an issue with Steam, and it was quite a large issue for Windows users as well prior to hackers actually fixing the problem by application of certain workarounds. The tools used to make Fallout New Vegas large address aware do not work with Wine, at the very least not the last time I tried it. I filed a bug report back in the days about this specific issue: bugs.winehq.org/show_bug.cgi?id=37625, however so far there has been no progress in this regard.

Until this is actually fixed, we will not be able to enjoy Fallout New Vegas properly as it needs more memory to be run even in its Vanilla state, running it with mods is even more difficult.

This is for user-compiled wine where there is incomplete music, eg from Mojave Music Radio. Look for this in output from ./configure:
checking mpg123.h usability... yes
checking mpg123.h presence... yes
checking for mpg123.h... yes
checking for mpg123_feed in -lmpg123... yes
If missing install libmpg123-dev (i386).

Hi All,
I'm running FO:NV on my late-2013 Macbook (2.6 GHz Intel Core i7 & NVIDIA GeForce GT 750M 2048 MB) and continually get the error "Failed to initialize render. Pixel and Vertex Shader versions incorrect. Requires a GeForce4 4400 or Radeon 8500 or better. Is there a way to adjust the setting in the wrapper to allow me to bypass this issue?

After some testing, I can confirm to fix this issue, you have to turn off Water reflections and Water refection. Other comments mention turning of AA and antiscoptic filtering but just turning off Water reflections and refraction did fixed it for me.

This does not seem to be a fix for me. The HUD still disappears, and I have to restart the game for it to come up again. Has anyone else found a fix?

Thanks, this was the only bug on my system and it now runs like a charm.

Was getting an error ( Unhandled exception: page fault on read access to in 32-bit code) With every new game upon initial load (after introductory cutscene) The game would freeze on the loading screen.

It resolved for me by simply reducing the display quality. By default Steam was setting it to "Ultra", I simply reduced it to medium and it worked (also try High).

This was using PlayOnLinux (v4.2.5) using Wine 1.7.44, Steam install.

Some players (myself included) experience black screens in certain contexts (not necessarily consistent). I finally got to see my terminal output when this happens, and I saw a bunch of GL_OUT_OF_MEMORY errors while I was in the pause menu (where the black screen bug was occuring behind it).

Therefore, I'm submitting bug #13335 as one of the bugs that affects this game.

Wine version: 1.7.18 (not avail during registration)

The game plays just fine except 2 strange bugs.

1. Sometimes the hud disappears and the world is brighter

2. RMB Glitch

To reproduce:

While in-game, press RMB to aim

Double hit ALT-TAB to send FNV window to background, then once again select FNV window.

The aim-mode should be still up, and not possible to go back to normal mode.

So i installed Fallout New Vegas earlier today.. at first the game wouldn't even launch, instead it would pop up with an error reading "Application load error 5:0000065434" before quitting

Through many visits to a myriad of forums, however, i managed to get past THAT problem, only to be further accosted by the startup screen which seems to be stuck in some sort of infinite loop..

The startup screen starts up seemingly completely normally, until a box pops up with the message:

"Detecting Video Hardware: Fallout New Vegas will now detect your video hardware and set video options accordingly."

This box is almost immediately followed by another stating that video settings have been set accordingly.. Nothing really threw me off at first, I thought it was just all standard procedure, until i hit play and the screen went black..

Expecting the game to load up normally, eager to immerse myself in the fallout world (or lack thereof), imagine my surprise when instead of seeing opening credits or loading screens, etc.. I was looking back at the same startup menu that i had just clicked through. And, like clockwork, the video hardware detection box popped up once again. After clicking through the startup menu and it's popups 5-10+ times (on several occasions) its clear to me that this startup loop is no random glitch (which i had, obviously, hoped it to be. many times. obviously to no avail.)

Now, i'm definitely no tech guru (as you can probably tell) so please excuse my ignorance towards these matters. While my options are as limited as my knowledge, I have nonetheless found myself desperately restarting my computer, uninstalling & reinstalling the game, browsing back through many of the same forums that I had visited just a few hours ago, and even searching through every options/settings menu available from the games startup screen and even from inside wine itself, but i still haven't the slightest idea what could be causing this infinite startup loop from hell..

If anybody smarter than me has any idea what could possibly be causing this and/or what i could possibly do to resolve it, i would be forever grateful. I've already spent the past few hours gruelingly resolving the first application error I encountered, at this point i just want to play the game and forget about all this.. my limited knowledge of technology such as this makes these stressful obstacles damn near unbearable so i have humbly come to request any possible aid from the people who know much more about all this than I do. i don't expect any miracles, but any tips, advice, or general words of wisdom that you might be able to impart unto me would, at the very least, be something more than the nothing i'm facing right now..

I've definitely been at this too long, the stress is building up, I'm going to go buy the homeless man down the street a meal and hope that good karma fixes all this by the time i get back...

thanks in advance for anything you might have to say or might be able to suggest,

Ashley xoxo

I played Ultimate Edition of FNV and I often has following crashes. After I launch FNV and load game all seems fine, until I move or open Pip-Boy. Until then I can look around and all seems fine, but one move or any action like displaying Pip-Boy - and game crashes with error like this:

Unhandled exception: page fault on read access to 0x0000000c in 32-bit code

Sometimes game started normally, sometimes after playing with the iNumHWThreads or other change in config files game can be started once.

Finally, I found the solution: NVAC - New Vegas Anti Crash. It is a plugin for another program - New Vegas Script Extender (NVSE), which allows adding some scripts for FNV. And NVAC can catch some known situations when game could crash and handle them properly.

At first, NVSE should be installed. It can be found here: nvse.silverlock.org Just extract archive to FNV folder. Then download NVAC here: www.nexusmods.com/newvegas/mods/53635/ Put NVSE folder from this archive to game's Data subdirectory.
Now you can go to the FNV folder and launch the game using nvse_loader.exe
If you installed game through PlayOnLinux, you can modify shortcut in ~/.PlayOnLinux/shortcuts/

NVSE works with Steam version of game and there is one issue. It wants the game to be installed into default Steam folder (i.e. in Program Files). Otherwise you'll see this error:

Application load error: 5:0000065434

Either install game to default location or make symlink for game to be looked like it is sitting in Program Files. Also if game located in NTFS partition mounted like ntfs-3g, POL will complain about file in a FUSE filesystem, but the game works anyway.

So, after installing NVAC, I've got my FNV working with no crashes anymore!
Tested on Mageia 5 (Cauldron) on PC with Radeon HD 3200 and laptop with HD 8750M. Also I should note, that on latter machine it works with no crashes on Win 8.1 either with or without NVAC.

I had an issue with sound in new vegas (wine 1.7.23, 32bits on 64bits Debian, using winealsa.drv through pulseaudio): most of the time the sound would be okay, but sometimes - especially during gunfights, and especially during gunfights in exterior areas with echos and reverb sound effects - the sound would become extemely choppy/stuttering, to the point where the game itself would have a very, very low framerate (like 1FPS or less).

The issue *does* come from the sound since setting bEnableAudio=0 in the Fallout.ini file results in no sound but the game running perfectly smoothly even with very high quality settings and a high resolution.

The pulseaudio logs seem to suggest that the DirectSound/alsa implem in wine tries to open (way) too many alsa connections (had thousands of 'Created input 1689 "Alsa Playback"' in the PA logs).

Tried to update my kernel, alsa/pulseaudio binaries, to no effect. Using bMultiThreadAudio=1 in Fallout.ini as well as tweaking the DirectSound parameters in the registry (such as HelBuflen and SndQueueMax) seemed to help a bit - the sound was still very choppy/delayed but the graphics and the framerate was not affected anymore.

In any case, I finally found a fix if someone happens to have the same issue: do *not* use the wine DirectSound implementation, add an override so that the native dsound.dll is loaded instead of the builtin. Also, if you use the dsound.dll file from winetricks, you'll be likely to get a "dirty" sound with echoes and so on - using a 32 bits dsound.dll file from a Windows 7 install instead results in a perfectly crisp sound (with this file: www.down-dll.com/index.php?file-download=dsound.dll&arch=32Bit&version=6.2.9200.16384&dsc=DirectSound).

Anyway, there must something wrong in the wine DirectSound implem, probably occuring only on some set of hardware/software configuration. Using the override described above fixed the issue for me (and increased the framerate even further).

The same problem happens in F3, it's that the dsound mixer is trying to mix together a bunch of streams in a very inefficient way. You can take a look at Bug #30639 (bugs.winehq.org/show_bug.cgi?id=30639) for some solutions.

Can confirm that using winetricks dsound makes it sound like it has a very low sample rate. Using that dll fixed it.

I see an artifacts and have low FPS on my mac with latest version of OS X. I can count on fixes for Macs?

- Ran into issues running the game under a x64 wineprefix, so I created a clean x86 prefix.
- Installed d3dx9, vcrun6sp6, vcrun2008, vcrun2005 (I think only the first 2 are essential), and then ran the game setup wizard.
- DO NOT INSTALL QUARTZ (I did on my first attempt and it would cause the game to crash after a couple of minutes)
Thats it.
The game works like a charm from what I can see, the VATS are working, all the sound effect are there, I can save and load, etc...

I put in my specs that I have 2x4GB but it's actually 4x2GB Corsair Ripjaws (not sure of the specs). Have been playing and sometimes VATS looks weird (messed up graphics). I just exit (e) and hit it again, fixes it.

I have an interesting issue. I played a few minutes through the game and when I went gecko hunting with Sunny Smiles I ran into a nasty issue. Shortly before the first encounter where the game introduces VATS, I crawl closer to the geckos. Suddenly the screen went black. Only the HUD was still visible and when I turn around I saw the compass rotating as it should do. Sometimes when I move I can see the normal graphics flickering through for a short time but when I stop moving it stays black.

I use Gentoo X86_64, Intel Core i7-3630QM, Nvidia GeFore GTX 660M (via primusrun) using the properitary Nvidia driver version 331.20. The issue also occures with the onboard Intel HD 4000. Kernel is 3.12.3-tuxonice and I use Wine 1.7.8. Steam runs with WINEARCH=win32. To install steam I used winetricks and after installing Fallout New Vegas I ran winetricks d3dx9 and winetricks quartz (which did nothing good or bad to me).

In the video settings I set everything to Ultra and then disabled Antialiasing and Antisotrophic Filtering (do remove the VATS issues and to prevent the HUD from disappearing near big rocks while the picture gets more blue).

Ah, and I set OffscreenRenderingMode to backbuffer in the registry as mentioned by somebody in the comments. But this seems to have no effect.

I think this is a memory issue. Either you can try to disable all plugins if you have any and play around with the ini files (like disable all threading options and enable the "pre-emptively unload cells" option) or you can set the largeadressawareflag this should fix it without the need to disable all mods and play around with the threading options (I think you can enable all of them if you can get the LAA thing managed). Sadly steam is the problem here because it won't let you start the game if you alter the falloutnv.exe. There is a 4GB patch on the nexus which does exactly this and tricks steam but I haven't got it to run with wine.

Also: I found out that if you experience lag during fighting multiple npcs the dsound.dll from windows 7 fixes this. The one you can get with winetricks will give you sound problems. Or you can set multithreaded audio in the fallout.ini, that makes just the sound stuttering but not the fps, so it's an improvement but not as good as the dsound.dll. Unfortunately I ran into some problems with multithreaded audio but maybe that is just my system: ALSA underruns and garbled sound if the fighting lasted too long.

FYI: On my laptop quartz fixed the stuttering radio/mp3 files.

Ah almost forgot: The CSMT patch by Stefan Dösinger works wonders with the game. Doubled my framerate.

www.winehq.org/pipermail/wine-devel/2013-September/101106.html

The vanilla game works remarkably well on 1.7.7, but one thing to remember with mods is that mod makers don't need care about capitalization, so that may lead to problems with mod resources. One way to fix this is to use symbolic links, although some mods may complain that there are duplicate files (usually this can be safely ignored.)

How come you guys are giving this game a platinum rating when it clearly isn't? Yes, the game installs fine and APPEARS to run fine at max settings. But didn't you wonder why music was missing from most locations? Why the graphics get corrupted when you walk toward Primm? Why VATS always gives 0%, even using at point blank range? Why it crashes randomly for no apparent reason? People, this is NOT a Platinum rating game. This game is bronze, MAYBE silver at best. Anyone giving this a Platinum rating obviously hasn't played it in Windows.

Well I agree, but if someone says its platinum, you can only ask them to check the very valid points you made and get them to change their mind. Never know, it might actually work for them (my experience mirrors yours though, VATS works then very quickly ends up being 0% everywhere and it crashes all the sodding time).

Those ratings can give people a rough idea of whats going on, nothing more. bug reports are what matters imho.

Yah I know... Still though, it's a little frustrating when you see some recent platinum ratings and think "Hmmm, maybe it works now.", only to find out that the exact same bugs are still there. I've tried this with various WINE/Linux/Window Manager combinations and the results are always the same. I've even tried different video cards. So, I've come to the conclusion that the people posting platinum ratings for this either haven't played a working version of the game or don't know what a platinum rating really means...

when the game is in load screen it crashs and givces me a porblem screen note

I've developed a somewhat bizarre bug in my copy of New Vegas.
Probably tied to one of the many mods I installed mind. Going to reinstall and prune my mod list to see what happens.

Anyways the bug is that when I get a certain distance from Goodspring suddenly the entire game takes on a blue hue and I lose my HUD, hair and most non-landscape objects just vanish.

Well seems to have been resolved by just running the game in a window, turning off anti-aliasing and antisopric filtering

Disabling anti-aliasing was the solution for me as well.

Me :
ubuntu 13.04
Gnome Shell 3.8
wine-1.6-rc5
computer: Asus N76v (i7, 8GBRam, GeForce GT 630M)
nvidia binary drivers:
version 304.88 ( buildd@lamiak) Wed Apr 10 16:20:15 UTC 2013

New Vegas:
version: steam install as of this comment
mods: None
resolution: 1920x1080
anti-aliasing: off
multi-sampling: off
bloom/hdr: off

I still get the issue described.

hair disappears, screen tinting changes, HUD vanishes.

Sometimes I can turn around to a certain heading and then it all comes back.

I had that kind of problem with some mods. Not sure about that (cause I don't use steam, but could be some of the mods (not all of them are working on my linux-fallout NV instalation.

I have exactly the same problem and it's driving me nuts..

AMD FX-8350 Black Edition (8-core, not overclocked)
Nvidia GT650ti-ssc (2GB, not overclocked)
8GB RAM, 2x64GB SSD in Raid 0.

Ubuntu 14.04 (With KDE 14.3.1)
Nvidia 337.25 (drivers from their site)
Wine 1.7.20 32b (via PlayOnLinux)

New, clean, installation of FNV via Steam, no mods.
AA/AF/HDR/Bloom all turned off via launcher.

Game plays fine except for this issue, would appreciate any pointers as to how to analyse this as I've tried all the changes to Wine and FNV settings I can find.

I MIGHT have found another solution to this bug. After hours of messing around with various settings, disabling "Water Refraction" in the launcher settings SEEMS to work with my save game which pretty consistently failed with the no hud and blue screen / black screen with and without hud / flickering screen bug happening when entering the gecko area. I think it has trouble rendering the water in the wells there. I haven't had a PROPER test yet but it seems to solve the issue on my end so far.

Ti was quite a ride, getting this game to work on Ubuntu 13.04 but I did it! Here is the recipe:
Ubuntu 13.04
ATI/AMD proprietary graphic driver (which is a pain to install when you don't know what to read, all hail goes to Tomasz Makarewicz) - cause with open source it's laging a great deal
Wine 1.4.1 - newer give you all kinds of errors
In FNV Launcher settings I set "semi high" options - cause "Anisotrophic filtering" screws your VATS (I found that somewhere and it works, but if you have open source graphic driver it's not necessary, VATS is working good but laging)
In winetricks BEFORE the instalation I had to install "d3dx9" (for directx) and "vcrun6sp6" (for setup installer to work)
NO QUARTZ! - it screwed my game

That's it! I'm playing it for 2 days now, no problems on sight, game wise at least!
I have an never ending fight with my "console" in game. It doesn't work! AT ALL! I have an European keyboard (and key before one(1) is working ````````!) and mouse (no controller). I push it in game and nothing happens! It's not resolution (as some say) cause the game would pause no matter the rez, if it's working, and it's not pausing.
Also, it's not infra/whatever cause I have a desktop with no ports of that kind. In the .ini file console is on (as some suggested to check).

Can somebody help me please! I just want to add more "carry weight"! Can you tell me if that "console" has something to do with Ubuntu or Wine version, or it's something else entirely?!?
I have Radeon HD 4650 graphic card, AMD Athlon(tm) II X3 435 Processor × 3, 3Gb ram, Ubuntu 13.04 64-bit & Wine 1.4.1

You sure the console is enabled? Been a while since I touched F:NV but iirc there was a separate option to enable the console. Maybe in the initial setup screen.

Outside of that then all I can imagine is that for some reason your UI is grabbing that key before your app is but I don't believe that happens (maybe a ctrl+key combo).

Nope! I'm sure. I didn't have any option trough setup. I played that game on windows before, best gaming in a while. I tried that combo, no luck. Don't know what else to try, thus the question. For the record, I hate Steam and I'm playing it solo (have a dvd edition). Maybe that is why, but to my knowledge, doesn't make sense.
Anyway, will tri to install g.e.c.k. and maybe I can tweak my character that way. Don't get me wrong, I don't use cheats much, and I'm playing on hard settings, but traveling back and forth cause of weight is very irritating (I tend to clean the wasteland :).

I will try a new install with a different version of Fallout NV to see is there any changes. Will post the result.

The quest is still ongoing!
So, till now I tried deleting everything about the game from pc and installing NV Ultimate Edition. Everything works great except the console! Then I googled "tilde" key and tried everything I could find about it, and nothing helped. I changed my keyboard settings to "us", "uk", and some others but no luck.
But I'll keep trying!
Till then, if anybody has an idea, it's most welcome!

Can the game map the console key to another button? Other then trying a different window manager or playing the game in a virtual desktop with different window manager controls the window settings, I'm not sure what can be done.

No, the game doesn't have that option. Different window manager is out of the question cause game is running as good only on wine.
Update: tried to change the whole keyboard (nothing), tried even with different distro (Zorin - build on ubuntu 12.04) and nothing helped. My tilde key is working fine in every other situation except this game! :P

So, instead of banging in the wall, I decided to go around it! Installed everything back and added a few mods to manage the absence of console. Mods are working, and I don't need the console anymore. Still I leave to the thinkers, if anybody has an idea, I'll try it, maybe we can still resolve this mistery!

hi!

the problem is the RAM cache on linux!
to prevent startup crash (if it is happening) do this (put it on a script like clearRAMcache.sh):

sudo sync
sudo bash -c "echo 3 > /proc/sys/vm/drop_caches"
sudo -k

As there is no log messages to detect music failed initialization,
this will use Pulse Audio and arecord
to detect if the main menu music is playing
(in truth if any sound is being made so make sure no other sound is playing...)

when main menu music doesnt play, other in-game musics dont play either :(

so with this, the game can be restarted until it works!

here is the bash code:
pastebin.com/V8J2tf5p

PS.: other cases when the game just crashes at startup,
you can log its messages using: tee
and with: grep
look for this message in the log: "Unhandled page fault"
and automatically in a loop, kill the game and restart it!

hi!

I would like to share this workaround to autoload last save:

windowId=`xdotool search --name "Default - Wine desktop"` #this is the name of the right window when you use virtual desktop emulation
sleep 30 #time enough to main menu be enabled, your system may require more
echo '(SayText "auto-load")' |festival --pipe
for((i=0;i

the forum broke it all :(, is there a way to post code?

Pastebin is a handy way, but yeah, its a fairly basic forum :)

amazingly good! thx bro!

here is the link to the "fall back and relax while the game gets ready" script xD

pastebin.com/BA9EWUGe

Running wine 1.3.27 through PlayOnLinux on Fedora 16 with a Radeon 1200 series video card. Not entirely certain if I'm running the ATI driver or Xorg, though. No help from the PlayOnLinux forums, but I'll probably be posting about a different issue related to this one there.

For whoever might be curious about WHY it's using 1.3.27, that's the only one that'll successfully bring up the launcher. I may wind up having to uninstall it, set the wine version to a later one, then reinstall.

However, I ran the debugger, and managed to come up with something that made me wonder what it means and how to fix it should I see it again.

"err:ntlm:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path.
err:ntlm:SECUR32_initNTLMSP Usually, you can find it in the winbind package of your distribution.
wine: Call from 0x7bc4b410 to unimplemented function ADVAPI32.dll.StopTraceA, aborting
fixme:ntdll:RtlNtStatusToDosErrorNoTeb no mapping for 80000100"

There's a lot of fixme's in the log as well.

Ok, I feel silly. I just realized that the reason that 1.3.27 is the only one that'll run the launcher is because that's the only version that has the game installed.

So, I think the above post can be safely ignored until I hear back from Steam's tech support to find out if I have to go through the revalidation process every time or not...

Then I'll resubmit.

Running wine 1.3.27 through PlayOnLinux on Fedora 16 with a Radeon 1200 series video card. Not entirely certain if I'm running the ATI driver or Xorg, though. No help from the PlayOnLinux forums, but I'll probably be posting about a different issue related to this one there.

For whoever might be curious about WHY it's using 1.3.27, that's the only one that'll successfully bring up the launcher. I may wind up having to uninstall it, set the wine version to a later one, then reinstall.

However, I ran the debugger, and managed to come up with something that made me wonder what it means and how to fix it should I see it again.

"err:ntlm:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path.
err:ntlm:SECUR32_initNTLMSP Usually, you can find it in the winbind package of your distribution.
wine: Call from 0x7bc4b410 to unimplemented function ADVAPI32.dll.StopTraceA, aborting
fixme:ntdll:RtlNtStatusToDosErrorNoTeb no mapping for 80000100"

There's a lot of fixme's in the log as well.

I get the following crash while walking outside:

Unhandled exception: illegal instruction in 32-bit code (0x0076002e).

I haven't found a pattern yet, but I can reliably reproduce it with a few of my savegames.

So far, the only work-around I have found has been to go to rollback to a previous savegame until I found one that works.

Environment:
- Pulseaudio is not running, I'm using ALSA straight
- NVIDIA driver 295.40
- Ubuntu 12.04
- wine 1.5.10 and 1.5.12 (both crash)
- wine set to WinXP or Win7 (both crash)
- latest version of New Vegas run via Steam

Does this look like a bug I should file? If so, what sort of debugging information should I provide?

I have found a work-around: use wine 1.4.1

Using 1.4.1 fixed the random crashes out in the wasteland I was encountering.

Thanks.

1.4.1 still has the same illegal instruction crashes (where you have to go back to previous savegames) but they are much less common.

For some reason, the one area that tends to trigger these crashes is the part of the strip where the NCR embassy is located. Haven't been able to isolate things further though, it could just be a coincidence.

Those are well known vanilla bugs. You aren't doing anything wrong, it's just a buggy game. In fact, the very fact that you are crashing near the strip shows that everything is working just as it does on a windows machine.

Thank you Wine team.

[Ubuntu 12.04]
[PlayOnLinux - Steam]
[Tried on WINE 1.5.9, 1.5.10, and 1.5.11]

Installed FNV via Steam, loads great EXCEPT no matter where I stand when I target someone with a gun in VATS I get 0% chance to hit (my Guns skill is ~30).

Also, though the game will Save on wait, it doesn't actually wait. That modal dialog that says "Waiting" or whatever never shows up, and time doesn't pass.

Yes I had this problem as well, the VATS chances must be based on something in the engine that wine distorts. Normally, I'd load a game, vats would be working for a bit and progressively get worse every time i use it to the point that it would be 0% with me having all the skills right in front of them.

It got so bad I ended up laying NV without vats which wasted a few perks it must be said.

Bottom line, if a reload doesn't fix it for you, then you might have to live without it for now :(

Not giving up!

24.media.tumblr.com/tumblr_m4ymt0XCR21qb993yo5_500.gif

haha, well might be worth creating a bug for it, I have all the DLC's to complete so might do it myself when I get a chance to play this again

I have the same problem. I can wait just fine though. Vats will work for about two or three go arounds then turn up all zeros. I even tried cheating vats to 100% and it still did nothing. Vats are like super god damn fun so it would be nice if they worked

Hi. I had the same problem. I ended up solving this by setting both AA and Anisotropic Filtering to 0 in the game settings, and enabling them via my graphics card's interface (nvidia-settings for me). I am also running this game via an old version of wine (1.4.1), as I had various issues with every other version I tried, up to 1.5.18.

Did anybody find out how to fix the loading crash?

Apparantly not. I've got a backtrace I'd like to post, but I've given up on finding a way to post it as a link. It's big enough I don't want to post it directly.

Anyway, basic gist, I'm running a Toshiba Satellite, With an AMD Turion X2 64-bit proc, Fedora 16, ATI Radeon X1200 Series video card. I'll be happy to send a copy of the backtrace for review.

The nitty-gritty is, and I could simply be doing something wrong here, but I installed Fallout New Vegas with no difficulty. I open up Steam, hit the play button, and the launcher comes up just fine. Naturally, because of the limitations of my system, it shunted to ultra-low video settings. Wasn't unexpected there. So, like a good little expectant monkey, I hit the launcher's play button. Long story short, I've lost track of the number of attempts, but I've somehow managed to log 15 minutes of play time, and only saw something trying to be a video once. After that one time, my subsequent attempts to start the game crash, resulting in the backtrace that I have. I'm about to simply uninstall it, completely kill Wine, and start from scratch. It's been nearly a week.

Forgot my Wine version, which is 1.5.8 (I think. That's what my Add/Remove Software program says, anyway)

Unhandled exception: assertion failed in 32-bit code (0xf77c8430).

Hi, I just bought FNV Ultimate, I was so exited about it 'cause the installation went SOOOOOO smoothly. But When I started the game, I chose as usual the "New Game"option and I skipped the intro. But here's the problem: The game won't load! I waited for 3hours and still, it doesn't load! :'( I'm running Fedora 17 Beefy Miracle, I've got Intel Core i7, My graphic card's the NVIDIA GEFORCE with CUDA. Please help or if you already solved the problem, send me the link where you found the solution. thanks ;)

If you are using PulseAudio then it's possible that you've got the "game halts a bunch for the first dialog sequence" problem (Bug #23616). You can avoid that issue by opening up the game menu and closing it over and over again until it gets through the first dialog sequence, or you can just temporarily disable PulseAudio.

I'm not using Pulse audio, it's not a bug, the game crashes. I'm gonna report it at bugzilla and see what happens ;) Thank you :)

What is the bug number? Have you tried waiting through the intro to see if that makes a difference?

When entering vats or when enemies were in front of me I would experience a massive frame drop (1 fps if lucky).

Setting OffscreenRenderingMode to "backbuffer" seems to have fixed it.

Yeah I had that too, I also noticed that when I'd have a massive framedrop vats would no longer work in that everything I wanted to do had 0% chance of pulling it off.

kinda got used to not using that since only a game restart would fix it. Does it happen to you with the backbuffer trick?

Vats seems to be working perfectly, getting hits as you would expect.

falloutnv: Did you make sure you compiled wine with gcc-4.5? I was trying to reproduce your problem and I couldn't find a "good" version of Wine at all, then I switched to gcc-4.5 and tested on Wine version wine-1.5.6-216-gd0012f8 and it worked great.

Hi!

just to share this workaround:

I was getting my machine frozen when playing FONV,
I found out that the problem is if you leave the game in menu mode,
or in a paused state (inventory) mode,
if you leave the game running it seems to not freeze the CPU,
just do a quicksave, when you comeback just load its all ok!

good luck.

PS.: this happens to me on ubuntu 12.04

Hi again,

I have no music from radios (those that we can click to turn on/off)
and most of the times I have no environment music (when you are in specific places)

I am using latest wine 1.5.5
ubuntu 12.04
may be I am missing better (or older) codecs?

At old machine (disassembled heh) with ubuntu 10.04, I had music from radios and environment 90% of the time (sometimes wine started without any sounds, now I have the sounds all the time no failures on that, but music happens only about 10% of the times I start the game).

My guess would be to try get codecs matching ubuntu 10.04, and use LD_LIBRARY_PATH to not mess my 12.04?

any tips?

thx!

a bit better info I think:

I have all the musics from radio playing but as environment sound at the strip!

the radio boxes (I think it is positional audio) is what not being able to play music (as I have all other positional sounds working aka gun shots etc),
so no codec problem,

my guess is it is something related to wine or may be direct sound implementation?

Hi!

Since I upgraded my machine (it was an amd 64 3000+, now it is a 4 core), I cant run NVSE_LOADER.EXE properly, no matter what version of wine I use, I always get this error:
wine: Unhandled page fault on read access to 0x00342000 at address 0x342000 (thread 0025), starting debugger...
Can't attach process 0023: error 5

and it also gives me a popup saying:
"internal errors - invalid parameters received"
(I read this happens on a 64bit OS, but I am running ubuntu 32bit for sure)

btw, if I run falloutnv.exe without nvse I have no crashes (but thats pointless as falloutnv is only good to me with nvse mods..)

I would like to know if I can get better debug info in some way also?

btw, as I know, nvse launches falloutnv.exe, I am guessing the crash page fault, is from the "invalid parameters" that nvse may be trying to set? but how can I check/change/access such parameters? what are they??

btw also, I found another laucher for/likewise nvse called fnv4gb.exe at nvse homepage nvse.silverlock.org/, this one crashes too with similar error:
wine: Unhandled illegal instruction at address 0x7ecd57c1 (thread 0026), starting debugger...
Can't attach process 0024: error 5

I tried also with the configurations made by playonlinux.

I had to disable all threaded config options in the .ini files or the game would not run or crash a bit after while in the main menu...

my specs: ubuntu 12.04 updated
cpu amd bulldozer fx-4100
memory 6GB kingston
wine 1.5.5 (but tried several other versions)

no more guesses for the moment :(

I wonder if someone could have some/any info on this?

thx!

fixed!!

ok ubuntu 12.04 kernel have an extra security power (it is good but..) that mess windows applications known as hacks (dll injection)

here the details
www.bay12forums.com/smf/index.php?topic=65326.0

here the work around
echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope

yey!

Hey, I'm using Wine 1.5.2 on Arch Linux x86_64, and the game installs and runs fine except for a rather serious issue with the mouse; it just jumps around.

When I'm not moving the mouse, it's not moving on the screen, but the more I move it in any direction, the faster it will go in that direction. This happens both in menu navigation and in-game controls.

Any ideas?

Installing into a new wineprefix solved it.

Just in case if someone else fails to find this with Google for hours and then has to try all optiosn to find the reason. If you Fallout New Vegas gameplay video picture is upside down (the game world is flipped vertically, but all the UI elements are still in correct orientation) that what you need to do is to turn off anisatropic filtering and antialiasing.

it runs PLATINUM for me on wine version 1.4
I have in game music finally! (not only the radios) environment ones!

I;d like to share that to the game run smoothly I have to set its priority (all threads) to -9,
just make a bash script and put this on it:
sudo renice -n -9 $$
before the line that runs fallout

the game will run almost smoothly on a 5 years old 2.6GHz (overclocked) monocore!

Ah good to know, I still need to go back and do the game again for a different ending and all the DLCs. Cheer for this!

I had one additional problem

Sometimes when I would begin a conversation, or when an enemy would do it's death animation, there would be crippling lag for 5 or 6 seconds, full processor usage both of my cores.

To solve it I restricted wine to run on one cpu:

e.g. taskset -c 0 wine "C:\Program Files...FalloutNV.exe"

After doing a bit of research and watching a few youtube videos, I still cannot figure out how to activate .esp and .esm files for some of the weapon mods I've downloaded for FO: NV on my MacBook Pro. I'm running the latest wine and every one seems to be pointing me to the Fallout Mod Manager, which I've also downloaded and have running through Xcode. It seems like a very deep rabbit hole just to get a couple of files to activate and be usable in-game. Is all this necessary or is there an easier way to enable some of these weapon mods?


Thanks.

wine 1.3.34 (until recently, 1.3.28, but I had the same problems)...

First, let's go with the sound problem: Launcher has it, even if in the options doesn't recognize any kind of sound card (which I don't have, except for the on-board one...), but in-game, the sound is TOTALLY inexistant. Not a pip out of the menu, nor the game itself. :( The sound works in other games and apps, so it's something related to the game itself. For this, killing pulseaudio is not an option.

Second: The mouse is WAY off center. You move it a milimiter and it runs off the screen (not literally, since it can't escape the window, but you get the idea). In 1.3.28, you couldn't even us it to select the options in the menu, but now at least you can do that. Too bad the game is unplayable like this. :(

Both problems are inexistent in the stable version (1.2.3), since I used that version until a couple months ago.

Thanks for the help. :)

I finally solved the mouse problem in 1.3.34. I have Mass Effect installed, and one of it's prerequisites is DInput, which is used as "Native". All the games (Grotesque 1&2, Bethesda's, etc.) that have mouse issues, should loose them just changing DInput from "Native" to "Buil-in". Having it "Disabled" or with dual option ("Native then Built-in" or viceversa), won't work (if disabled, most games won't even start...). Hope this helps anyone having this annoying problem. :)

Sadly, the sound problem persists... :(

Hi Guys,

I'm a newbie with this but I think I gave it a good shot.

The game message gives me:

Failed to initialize renderer.
Pixel and Vertex Shader versions incorrect.
Requires a Geforce4 4400 or Radeon 8500 or later

The error log gives me:

fixme:d3d:init_driver_info Unable to find a driver/device info for vendor_id=0x10de device_id=0x863 for driver_model=2
...

What I've tried:

- force (MAC, installed the packages separately to update) to update drive of my graphic card

- regedit from Wine HKEY_CURRENT_USER\Software\Wine\Direct3D PixelShaderMode (windows XP)

- even tried to install the Nvidia Windows XP driver in wine ( using the exe package)
=> Unknow error

System :

Mac OS X 10.6.8
8GB DDR3

2.26 Ghz Intel Core 2 Duo

Chipset Model: NVIDIA GeForce 9400M
Type: GPU
Bus: PCI
VRAM (Total): 256 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0863
Revision ID: 0x00b1
ROM Revision: 3427
Displays:
Color LCD:
Resolution: 1280 x 800
Pixel Depth: 32-Bit Color (ARGB8888)
Main Display: Yes
Mirror: Off
Online: Yes
Built-In: Yes

Any help or suggestion ?

Thanks in advance.

sorry forgot to mention.
tried with and without
- winetricks d3dx9
- winetricks quartz
- winetricks vcrun2008

wine version 1.3.29

Try disabling GLSL using the wineregedit

The launcher runs, but it seems that my ATI Radeon X850XT gets identified as an ATI 8500 serie. When the 'PLAY' button is hit on the launcer panel, wine chokes and the last messages on consoles are:

fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x1b31c8,0x1af44c): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x33eb9c,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x33ebec,0x00000000), stub!
fixme:d3d:swapchain_init Add OpenGL context recreation support to context_validate_onscreen_formats
fixme:d3d9:D3DPERF_SetOptions (0x1) : stub
fixme:xinput:XInputGetState (0 0x33fa38)
fixme:d3d9:IDirect3DDevice9ExImpl_CheckDeviceState iface 0x1b49a0, dst_window (nil) stub!
wine: Unhandled page fault on read access to 0x00000000 at address 0xbc1a65 (thread 002a), starting debugger...

Nothing else happens untill i 'kill -TERM [pid]' where [pid] is the process id of FalloutNV.exe.

I'm testing wine-1.3.29 and as others have suggested,
in a clean wineprefix, I've also run (one at a time)
- winetricks d3dx9
- winetricks quartz
- winetricks vcrun2008

I didn't install either directx or visual c++ during the game initial setup,
but I did that in an earlier attempt with the exact same end result.

Any suggestions?

I got the game installed, but the launcher does not come up when I try to run it. Does anybody know what to do?

Is yours a steam version? What version of FNV is installed?

SKIDROW is the crew behind the version I have.

I have New Vegas from Steam.

I press E on the door to leave the Doc's house and enter Goodsprings. As soon as the loading screen finishes, the screen goes black and I am told there was a problem with FalloutNV.exe and it needs to close.

Because it's from Steam, getting console output to find out what's causing the problem is impossible as far as I can tell.

I have tried to revalidate the game files, 1 file was indeed inconsistent and was redownloaded but the crash continued to occur.

d3dx9 and vcrun2008 are installed. Steam runs in its own wineprefix that has no other programs installed.

You need to apply the patches in Bug #24478, I haven't had a chance to simplify a small part of one and they all need to go in together.

Even the Pulseaudio specific one?

OK I'm not so clear on patches, I rarely have to use them.

I'm trying to compile 1.3.27 with the patch, I've saved both as diff files (is that correct?) and I have executed:

patch -p1 -R < fallout-patch.diff

This produces the following:
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/dlls/quartz/filtergraph.c b/dlls/quartz/filtergraph.c
|index 1becf11..edcb0c5 100644
|--- a/dlls/quartz/filtergraph.c
|+++ b/dlls/quartz/filtergraph.c
--------------------------
File to patch:

I've obviously done something wrong, I'm not just so sure what. I've only ever dealt with patches once before.

Nevermind. Fixed with a Windows 7 native quartz.dll.

Hi again,

After being able to launch the game, I have a new problem.
I have sound when launching FalloutNVLauncher.exe
But then I have no sound after the intro.
I tried multiple things, like using OSS instead of ALSA (dont work), override quartz lib to native (dont work for me), using the "winetricks quartz", and it still doesnt work.
The winetricks quartz seems to soluce this error:
fixme:quartz:Parser_OutputPin_QueryInterface No interface

But now I have an other one :
fixme:d3d:resource_check_usage Unhandled usage flags 0x8

I'm a bit lost again.

Help?

what OS are you using? It could be that the launcher isn't closing it's audio stream before the game loads up, so once the game loads up it doesn't think it has sound.

Might either be worth trying to use pulseaudio OR launching the game directly perhaps?

Im using Ubuntu 10.04, wine 1.3.24
I have now a bit of sound of the intro, after the launcher, then its stopping.
I have pulseaudio but don't want to uninstall it. I'd prefer an other way to make it work.

You won't need to uninstall pulseaudio :). Erm I'm really unsure what the issue is, have you tried launching the game directly without using the launcher?

Also, try and start a new game and see if things like speech, sound effects work, could just be the music which as I understand it can be bugged on some systems?

I use Gentoo myself so hard to test this for you

Nice advice !
By launching the game directly with FalloutNV.exe, I have no music but I have speech and other sounds ! Big progress !
At least its sure that there is a link between the Launcher music and the sound problem ingame (but which one ?).

The sound stays a bit laggy, like footsteps 1 sec after jumping, etc...
I also have no music.

I made a few tests:
-When adding quartz.dll to native, I have (laggy) sound ingame but no music in intro and ingame
-When not adding this lib, I have intro music, but then no sound at all ingame.

Any ideas ?

There are bugs regarding music and what not on this game, check out the bugs above the posts and see if theres anything in those that help! Again, I run Gentoo and have no problems at all, so they do seem to be very Ubuntu related :S.

Some news !
By setting quartz.dll to native AND unable winegstreamer lib, I have sound AND music, seems not laggy !
I just dont have the intro music.
Good thing !
Seems solved (by launching the game via FalloutNV.exe AND by FalloutNVLauncher.exe)
Hope this will help other people.
Thanks a lot !

Thank you!!! Your last comment was very helpful for me .Now I am running FNV _with_ sound. Thanks once more!!!

Hi,

I just installed Fallout New Vegas.
I have Ubuntu 10.04, Wine 1.3.24
When I launch the game via FalloutNVLancher.exe or FalloutNV.exe, I have the following error in a messagebox:
"Failed to initialize renderer.
Pixel and Vertex Shader versions incorrect. Requires a Geforce4 4400 or Radeon8500 or better."

But I have an NVIDIA Geforce GT430, which (as I read) is compatible with FNV.

I'm a bit stucked. Help ?

Hi, usual pre-amble just so I can make sure nothing is assumed;

1. Is opengl working on your system?
2. Can you play other direct3d games on wine?

It could just be that you either aren't using the proper nvidia drivers or you have vertex shaders turned off, both would produce the same error.

Cheers,
Maq

Thanks !
My problem is fixed.
As you said, I just didnt enabled the PixelShaderMode in regedit.
I went in regedit to
HKEY_CURRENT_USER/Software/Wine/Direct3D/PixelShaderMode
and put it to "enabled".

Thks again

Happy to help :)

Now as I have got the game running perfectly, I feel obliged to tell you all how I did it.
The following is for Ubuntu (or other debian distros).

1. install git and patch
$ sudo apt-get install git-core patch

2. download latest wine
$ cd ~
$ git clone source.winehq.org/git/wine.git ~/wine

3. install dependencies to wine
$ sudo apt-get build-dep wine

4. download this two patches (right-click and save as)
bugs.winehq.org/show_bug.cgi?id=24478#c48

5. apply the two downloaded patches
$ cd ~/wine
$ patch -p1 < /path/to/the/patch/fallout-bgmusic.patch
$ patch -p1 < /path/to/the/patch/f3-pulse-problem.diff (with this it says something about assuming anything, but just continue)

6. compile wine (this takes some time)
$ cd ~/wine
$ ./configure
$ make
$ sudo make install

7. install fallout with both direct x and the visual studio extras

8. run the game using the FalloutNVLauncher.exe.

Confirm!
I patched wine-1.3.24 and game running with background music and Radio music!

"2. download latest wine
$ cd ~
$ git clone source.winehq.org/git/wine.git ~/wine "

I am new to Ubunto and not sure how to create directories, download source files, etc.

In the terminal, when I enter this code it says, "fatal: repository 'command' does not exist"

Any help? thanks

Keep in mind that the post you are replying to is quite old by wine standards. The patches mentioned there I believe are no longer required. Get wine installed from the main page for ubuntu and see if it works before you try and patch a git version.

From my own experience I can honestly say it was working fine from vanilla wine as recently as a couple of months ago.

Cheers,
Maq

After a good bit of reading, I got F:NV to install with wine 1.3.17 on Ubuntu 10.10 x64. In the process of installing I had to disable two native libraries, one called quartz.dll and the other devenum.dll. Now the game starts, but there is some pretty severe weirdness. Firstly, Doc Mitchell looks like a Hannibal Lecter mask with a mustache. Interesting... The other problem is that the game pauses between sequences. The game opens with a blurry vision of a ceiling fan...and the Courier just sits there looking at the fan forever. However, if I pause the game then hit 'Continue' the Courier will tilt his head to look at Doc Mitchell, who then (silently) says his first line. There is another infinite pause, after which if I hit pause and continue he'll say his second line, etc.

I'm also seeing lots of lines like this:

fixme:d3d_shader:print_glsl_info_log Error received from GLSL shader #178:
fixme:d3d_shader:print_glsl_info_log Vertex shader(s) linked, fragment shader(s) linked.
fixme:d3d_shader:print_glsl_info_log Error received from GLSL shader #182:
fixme:d3d_shader:print_glsl_info_log Vertex shader(s) linked, fragment shader(s) linked.

Anyone have a clue?

Fixed the weird texture problems by upgrading to Catalyst 11.3. Found that the issue with Doc Mitchell is a known problem. Just continuing through the scene, then saving your game resolves the problem going forward. Sound also appears to be functioning properly with a clean wine install - no winetricks. I'm using the following registry settings, though I'm not sure which are necessary.

DirectDrawRenderer opengl
Multisampling enabled
OffscreenRenderingMode backbuffer
PixelShaderMode enabled
RenderTargetLockMode readtex
UseGLSL enabled
VertexShaderMode hardware
VideoMemorySize 512

I used a vid mem size of 512 even though I have 1024MB. The GLSL errors still appear, though they don't appear to make a difference. Performance is poor compared to my Vista install, but I wasn't really expecting emulation to outperform a native solution.

wine is not an emulator

WINE is a native solution and some times WINE does outperform Windows.

I also get quite a lot of those logs, using catalyst11.5 and latest wine from git. So far does the game work for me - in maximum 15 minutes . Did you get things straight? Does it run for you? If yes, exacly how did you do?

I did get it working, but performance stank. I fixed this by getting out an old Nvidia 8800GT and popping it into my Linux machine. As old as the card is, it outperforms the 5750 by considerable margin. All I can figure is that the Nvidia drivers are much more mature than the AMD ones. Fortunately, I was able to put the AMD card into another Windows machine for Windows gaming. See my replies for how I got it working.

When I start a new game and the intro is done when it loads it says it has a "wine" problem. can anybody plz help?

Hi,

my F:NV Launcher recognizes my graphic-card as a 2900 XT although it is a HD 3870. I know there are some issues with ATI-Drivers. The game does work fine and runs smoothly most of the time.
I've installed the newest Linux-Driver available on the AMD/ATI-homepage.
Does anyone know this problem or even has a solution for it? I'd be glad to hear some other experiences with ATI-cards.

Thankies in advance,
Fred

i've had the same experience on an hd 3850, but like you it seems to run fine using wine 1.3.19. unfortunately, sound doesn't work on 1.3.21, and i experienced frequent crashes to boot.

So I just updated to the latest Wine (1.3.15) and downloaded the DLC and updated Fallout. My mouse movement in the game is very jerky/unresponsive--but only when I'm in the game or conversation. If I have the Escape or Companion Dialogue menus open, the mouse seems fine. The mousewheel also doesn't work.

I did not have this problem before any of these updates. The only problem is that there are so many variables that might be causing this problem. It could be mods (had to update NVSE...) or it could be Wine. So, I'm wondering if anyone else has had this problem.

Yes, there was actually a short period where the whole game was locking up about once a second (when moving) right before 1.3.15 was released. I haven't had a chance to narrow down the cause yet, but the input management in Wine recently had a major overhaul. If you'd like (and have the time) you could perform a regression test (wiki.winehq.org/RegressionTesting) and file a bug for the issue.

Hmm, indeed. In the interim I will probably just downgrade to 1.3.14. I use WinePulse, so that will be an extra complication. I may try a regression test, but I'm not sure if I have the time. The last time I tried compiling Wine I had serious issues, but that was on Solaris XDE. I think it will be a bit easier on Ubuntu.

Provided that you have Wine's PPA added to your repository list you can just run:
sudo apt-get build-dep wine1.3

If you don't have the PPA added you can use the old one in the main repo (most of the same dependencies):
sudo apt-get build-dep wine1.2

Well the problem is that I use WinePulse. I use the c-korn PPA to keep that up to date, but that PPA doesn't keep older versions (apparently). I'm actually attempting to compile Wine 1.3.14 right now.

I'm not suggesting that you move away from using WinePulse for your normal uses, just for the regression test - you don't exactly need audio to test this bug :)

That's true. After I am done compiling wine 1.3.14 with the WinePulse patches I will try compiling for the regression test. I can't actually *try* it since I'm at work. I don't think Fallout would run well over an X forwarding connection somehow.

As a related problem, FOMM was crashing under wine 1.3.15. I compiled wine 1.3.14 and ran FOMM and it worked fine. In about 30-45 minutes I will be able to test Fallout itself and see if 1.3.14 works with that.

Note: this is not the regression test. I will do that if I have time.

Confirmed that the mouse is not jerky in 1.3.14. So for people who are having mouse issues, don't use the latest unstable Wine (1.3.15). Use 1.3.14.

I confirm that 1.3.14 works _better_ than the latest 1.3.16 but mouse is still jerky because game can't keep it in window bounds. Same for a joystick. I can actually play the game now but it's still impossible to shoot someone outside V.A.T.S.

Hello guys, I have the same issue as was described here www.youtube.com/watch?v=22jzP4VGS_M . This video even has an explanation how to fix this, but it seems that it doesn't work for me. My os is Archlinux x86_64, wine 1.3.14, I followed the instructions of Neptune Raider, game runs correctly except these sounds... I tried to replace winmm from 1.1.42 and 1.3.6 but still got the same. Can anyone help me, please? :)

never mind, problem is fixed. The issue was about bad image of the disk

I'm wokring on 2 monitors each 1680x1050 with nvidia twinview enabled, which merges them to one 3360x1050 virtual monitor.

Basically I'm trying to run the game on one of those monitors with 1680x1050 native resolution.
I managed to get the game running, but it chops off something on top and on the bottom off the screen.

Already tried "Emulate a virtual desktop" function, it uses BOTH screens, and if i try to change the screen size in FalloutPrefs.ini (which is 3360x1050) it always says invalid resolution.

Any ideas?


wine-version: 1.3.11
Fallout NV version: 1.2.0.314
nvidia drivers: 260.19.29

Best I have manager to get is to run the game in windowed mode (and tell my window manager to not display the borders) - dosent quite fill the screen though (the window is just short by about the size of the title bar).

Using disper ( willem.engen.nl/projects/disper/ ) now to switch one monitor off before playing (disper --single) and restoring my configuration afterwards with the import-feature. Runs much smoother in fullscreen than the windowed-approach.

www.youtube.com/watch?v=XGl0sCNtsUg

Showing the game runs really good :)

The lag in the video is caused by recording software + Bad specifications.

Hi!
I am not being able to run FNVEdit.exe to solve mod related crashes, any tips? :(

Does anyone know why I would be getting the error below? I think it might be related to some minor stuttering that I am experiencing. Anisotropy is not enabled, but the game is still complaining about it?

err:d3d_texture:basetexture_apply_state_changes >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from glTexParameteri(GL_TEXTURE_MAX_ANISOTROPY_EXT, aniso) @ basetexture.c / 503

Is it me, or do only characters cast shadows? On my box objects (rocks, houses, vegetation, etc) simply don't any shadows.
Anyone else getting something similar to this?

I just tried the game on Windows, and this appears to be a limitation on the engine.....
It's unbelievable pathetic. The game looks bland and boring.

I installed the game as described by devil666, for about 3 minutes it works perfectly, but then I start to see messages like these below and the game becomes real jerky (as in 1 FPS) also no audio when these messages start to become more freaquent. Anyone know how to fix this. Standard Ubuntu 10.10 install.

Note: Illegal Audio-MPEG-Header 0x217396bc at offset 96256.
Note: Trying to resync...
Note: Skipped 226 bytes in input.


mmap() failed: Cannot allocate memory

Have you enabled the wine debug messages? (err: or fixme:-lines of output?) maybe this helps to find out more.
Maybe there are those lines before the "Note:"-lines appear?

Do you use the steam-version or the standalone-version?
Have you patched the game to the latest version? (steam does this automatically if you dont disable it)

i use ubuntu 10.10 and wine 1.3.9, too. the steam version of the game, newest patches applied, works for me.
i saw the mmap error too, but (iirc) in relation to gstreamer-fixme-messages, so i had to disable "winegstreamer" under libraries in winecfg.

I am running New Vegas with wine 1.3.9, on Ubuntu 10.10, and the sound is lagging by about a half second. I've tried different video and windows setting, but none of them seem to help. Other than the sound, the game is running great--I even get a higher frame rate than in windows.Any help I could get would be much appreciated, because once this game works properly, that's all I need to banish windows forever from my system!

It's probably the pulse problem, have you tried the winepulse?

No I haven't and I have no idea how to

Just use Neptune Raider's Information.

"2. Installed msvcp90.dll & xlive.dll in c:/windows/system32
2.a. Using winecfg, under libraries tab, set msvcp90.dll to native (Windows)."

solved that one for me.

(A Wine with compiled pulseaudio also solved it, but the above solution is better, because it works without recompiling wine.)

But still no music ...

Same issue here. I was able to fix it by setting "Hardware-Acceleration" to "Emulation" in the "Audio" tab in "winecfg".

Using Wine 1.2.2 with Alsa-Driver on Ubuntu 11.04. Now sound plays fine.

Hi Everybody,

i installed as told in several guides (winetricks, regedit etc.), using a fresh ubuntu 10.10 with wine 1.3.9.
Starting a new game results in a reproducable error after entering the players name and using the ESC+Left Mouse-Workaround. Anyone else has this problem?

err:d3d:resource_init Out of memory!
err:d3d9:device_parent_CreateSurface (0x144904) CreateSurface failed, returning 0x8876017c
fixme:d3d_texture:texture_init Failed to create surface 0x5beb8588, hr 0x8876017c
wine: Unhandled page fault on read access to 0x00000030 at address 0x439e0a (thread 0046), starting debugger...
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x80000

thanks!

Finally i found the solution: i had to disable winegstreamer in winecfg, that solved my problem. (see ubuntuforums.org/archive/index.php/t-1602000.html)
Now the game runs fine with wine 1.3.9 / ubuntu 10.10.

Hello,
Go the game runnig just fine seems to be working lagfree untill i talk to somebody then the lag is unbearable. Any sugesstions to why it only lags in dialogue mode and how to fix it?

Do you get any unique messages in the terminal?

I realized that this is actually and old bug from fallout 3:
bugs.winehq.org/show_bug.cgi?id=16816
But none of the fixes works for me, guess i will have to get the xbox360 version =/

I'm still not getting it to work: everytime I start the FaloutNV.exe with wine (1.3.7.1) I get "Application load error 5:0000065434" and I have absolutely no idea of how to solve it.

I've did everything Carl told me in his guide ( pastebin.com/DiqH64Qx ), except there is one difference (except for the not-working part): If I install FaloutNV, wine automatically places it in the directory:
/.wine/drive_c/Program\ Files/Bethesda...

instead of

/.wine-fnv/drive_c/Programfiler/Steam/SteamApps/common/...

The guide also says that steam will patch the game, but when and where, and most important how

I'm at a loss, I've been trying to get it to work since the game got out, so please help me

> "Application load error 5:0000065434"

That's the "steam not found" error code. So, either you don't have steam installed properly or you're not running the game from the correct folder. When the game is first installed it should launch steam and have you enter your CD key, after that it will perform an update through steam. Once that is done then every time you launch the game it will start steam (or pop up that error code) and make sure it's updated and your key is valid. I'm pretty sure it's important to have the game in "C:\Program Files\Steam\SteamApps\common\fallout new vegas" though, as when I try to launch the game from a symbol linked folder in another location it will generate that "steam not found" error code.

After updating from unstable PPA today (Ubuntu 10.10) the game crashes every couple of minutes or so. It seems the game is flooding my system memory since system monitor reports 100% memory usage up until the crash, and the game sometimes complain "out of memory!" I had this issue with Fallout 3 too, but not nearly as often as this. It might be because I play FNV with rather demanding graphics settings. It sucks though. I've gotten to level 15 (or more? oO) and now it doesn't work anymore... Will roll back to the previous version I used to see if it helps. Will report bug later if that proves to be the solution.

Yup, downgrading to 1.3.7 from 1.3.8 fixed it.

Hi, used PlayOnLinux, wich installs wine 1.3.7, vcrun2008 .NET Framework 2.0 Common COntrols Directx9 GamesForWindwos. The installer fails in the first attempt, because tryes to install vcrun2008 before .NET Framework 2.0 to solve this, in terminal i executed:

WINEPREFIX=~/.PlayOnLinux/wineprefix/FalloutNewVegas wine "/home/martin/.PlayOnLinux/ressources/vcrun2008/vcredist_x86.exe"

After that, I executed the installer from my downoads HDD

WINEPREFIX=~/.PlayOnLinux/wineprefix/FalloutNewVegas wine "/home/martin/Escritorio/FalloutNewVegas/Setup.exe"

Disabled windows composite effects from System->Preferences->Appereance

When Running the game from Desktop Icon, the game starts, the crashes, so I copyed the d3d9.dll (the one to fix some lag issues) to the installation folder.

The game run, a crash window appears, then the game resumes without music (but with sound ok)

Best regards!

Under the "Testing" section, you can install this game using PlayOnLinux.

It work good, expect the weird bug at the beginning of the game (describe in the test comments), you must press ESC and return in game 4 ou 5 time to make the game script star...as soon as you can move freely (after this buged "presentation"), the game is working as usual.

And don't delete this comment, PlayOnLinux help too easy the install process and manage wine version, it DO NOT modify wine so it's THE SAME as testing with wine only but it's easier and faster !!

Hello,

I installed New Vegas on my iMac (Core i5 2.8 Ghz, Radeon 5750 1 GB, 8 GB RAM), but i can't play it because of the low performance.
I used PlayOnMac with latest wine (1.3.7). The game runs without crashes or other problems but is too slow even on low graphic-settings.
At the beginning inside the house the game is playable, but outside not.

Any idea!?

Perhaps OSX version of wine suffer same problems as Linux one with AMD/ATI cards. Under Linux ATI/AMD driver is very poor and dirty, offer horrible performances, especially with wine.

Is it possible to eplace Mac graphic cards? If yes, perhaps you could, at least, try with a Nvidia Card to see if you have better performances.

A friend of mine use PlayOnMac too on macbook pro (with an Nvidia 9400M) and he say it work good, he played Devil May Cry 4 and Mafia 2 with it.

I'm not sure if wine on Mac has the same problems with Radeon cards, because Mac should use another driver.
Native games like starcraft 2 work great, it seems to be a wine issue.

Changing the graphicscard isn't easily possible.

FoMM (sourceforge.net/projects/fomm/): Nice tool for handling lots of mods for the game. Requires .Net2.0 or maybe Mono.

NVSE (nvse.silverlock.org/): New Vegas Script Extender. Allows mods to do even more. Requires the steam community overlay (gameoverlayrendeder) to be enabled. Go to "Steam->Settings->In-game", click on "Enable Steam Community In-Game". Then click the "Friends" tab and in the "Notifications and Sound" section make sure that all "Display a notification" settings are off, otherwise FoNV will crash on startup.

both the directx9 from game iso and from winetricks fails with

err:setupapi:do_file_copyW Unsupported style(s) 0x144

and

err:rundll32:wWinMain Unable to load L"streamci"


can anyone help?

gentoo 2.6.36
nvidia gtx460 with drivers 260.19.12
wine 1.3.6

I had the missing textures bug for characters models on Ubuntu 10.04 with a Radeon HD5770 and the latest Catalyst (10.10) driver.

I tried to install the former Catalyst 10.9 and it solved the problem for me.
It can be downloaded here (yeah, they screwed up their URL):
support.amd.com/us/gpudownload/linux/10-8/Pages/radeon_linux.aspx

> Now, the intro to the game went just fine for me, however when I came to the scene where you see the fan in the ceiling, I had to press Escape and then Continue for the game to continue. You have to do this until you get out of bed. Also, I had no sound when doing this, and no subtitles so I don't really know what was said.

I have this problem in my dual-booted WinXP SP3, game patched 1.1 AND sound problems (I cant hear half of the dialogs/ambiance, and from time to time all the sounds which did not sound do it at once, freezing the game for a moment. So may that happen to you it's Bethseda's devels to blame, not wine's xD.

I had the same problem on Ubuntu 10.04.
It was solved by uninstalling pulseaudio.

In this case you'll need an alternate mixer like gnome-alsamixer because the sound indicator applet depends on pulseaudio.

I had exactly the same problem as forum.winehq.org/viewtopic.php?t=10098&view=previous
This one:

Unhandled page fault on read access to 0x00000008 at address 0xeb890c

but with DirectDrawRenderer = gdi in
HKEY_CURRENT_USER\Software\Wine\Direct3D
it runs.

Weird.

Correction: It does not really work. It worked once, and after that, the same error appeared again. So this has probably nothing to do with it.

As Carl A. Myrland says in his text, when the error occurs, just press ESC once and then the left mousebutton. Game will load then and the error disappears!

Doesn't work for me. If it crashes, it crashes for good. However, there's a maybe 30% chance that it will start. And if it does, it runs for hours.

I updated my Ubuntu distribution from 8.10 to 9.10, and after recompiling wine 1.3.6, I get the nonfatal crash described above plus there is no music in the menu or ingame. Ubuntu 8.10 had gcc 4.3.2 and linux 2.6.27, whereas Ubuntu 9.10 has gcc 4.4.1 and linux 2.6.31. I also tried configuring the wine build by excluding features that were not available in the previous installation, but to no avail.

Currently, I have to use a wine built in Ubuntu 8.10 to get music and avoid the crash during startup.

Why do you compile Wine in Ubuntu? Using the package from the wine ppa works just fine.

Fine as in no crash in startup, as described above?

Nevermind, just edited the registry to add direct3d and now it seems to work. An error window appears and then it disappears after a while.
BTW, had to add the registry keys by hand, regedit didn't leave me rename.

Sorry, hit "post new" instead of "reply".

I have Wine 1.3.6 after trying run game it crashes immediately.
Here is my log from console:
pastebin.com/Ck1vFQF8

at the end is this backtrace:


Backtrace:
=>0 0x00a002a5 in falloutnv (+0x6002a5) (0x0032f994)
1 0x00708d81 in falloutnv (+0x308d80) (0x0032fa1c)
2 0x00707e42 in falloutnv (+0x307e41) (0x0032fa54)
3 0x006fff1c in falloutnv (+0x2fff1b) (0x0032fa78)
4 0x00865195 in falloutnv (+0x465194) (0x0032fe00)
5 0x00ec30d0 in falloutnv (+0xac30cf) (0x0032fe90)
6 0x7b85656c call_process_entry+0xb() in kernel32 (0x0032fea8)
7 0x7b85720f ExitProcess+0xc9e() in kernel32 (0x0032fee8)
8 0x7bc728e0 call_thread_func+0xb() in ntdll (0x0032fef8)
9 0x7bc75450 call_thread_entry_point+0x6f() in ntdll (0x0032ffc8)
10 0x7bc4a72a call_dll_entry_point+0x659() in ntdll (0x0032ffe8)

Any ideas why?

See my detailed installation description here:

pastebin.com/yJdpJaiH

It's submitted to appdb for approval. So long, I'm gonna go roam the Wasteland for a while :)

Tried to install with your way.. But same problem occured

From your pastebin, line 1:

err:winediag:X11DRV_WineGL_InitOpenglInfo Direct rendering is disabled, most likely your OpenGL drivers haven't been installed correctly.

Please list all your relevant hardware/software so we can see what we're dealing with.

Okay, so you have an ATI Radeon HD 45xx graphics card. Have you installed the AMD Catalyst driver for your graphics card? If you enter lsmod you should see "fglrx" in that list.

What is your distro? Distros these days normally provide the proprietary graphics driver through their repository, otherwise you can download the newest version for your distro from amd.com.

Yes i have fglrx driver:

~$ lsmod | grep fglrx
fglrx 2523725 129

but when i run glxinfo i see i have not enabled 3d rendering:
~$ glxinfo | grep rend
direct rendering: No (LIBGL_ALWAYS_INDIRECT set)
OpenGL renderer string: ATI Mobility Radeon HD 4500 Series

BUT when i try it in xterm i got this:
~$ glxinfo | grep rend
direct rendering: Yes
OpenGL renderer string: ATI Mobility Radeon HD 4500 Series
GL_NV_conditional_render, GL_NV_copy_depth_to_color

and my fglrxinfo:

~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon HD 4500 Series
OpenGL version string: 1.4 (3.3.10237 Compatibility Profile Context)

Okay, I still cannot get the game running.

I've made a complete list of proceedings and put it up for you here:

pastebin.com/DiqH64Qx

I've followed tips, tricks and advice from all of you in this thread and the Fallout 3 thread, but it still crashes. Please help.

WOHO!

I got it to work! It's a bit messy, though, and toward the end of my "worklog" I need to make amends for my frustration ;)

Anyway, here's what's new since I posted my original post:

$ WINEPREFIX=~/.wine-fnv sh ~/winetricks comctl32 cc580

Installed just fine

Still doesn't start.

$ WINEPREFIX=~/.wine-fnv regedit

changed multisampling to enabled. Broke steam. Doesn't start anymore, even after changing it back.

Changed to Vista. Steam starts again. Yep, all good. Switched back to XP, getting as far as before. Tried changing sound to emulated, game refuses to start since it doesn't detect a sound card.

($ fixme:gameux:GameExplorerImpl_VerifyAccess (0x1bf940, L"c:\\programfiler\\steam\\steamapps\\common\\fallout new vegas\\GDFFalloutNV.dll", 0x33b910) What does this mean?)

$ WINEPREFIX=~/.wine-fnv winecfg

Changed winver to Vista.

Changed sound to emulated, started FNV with

$ WINEPREFIX=~/.wine-fnv wine ~/.wine-fnv/drive_c/Programfiler/Steam/SteamApps/common/fallout\ new\ vegas/FalloutNV.exe

Clicking Play only tells me the game can't find a sound card and won't start.

WITHOUT exiting steam I go back to winecfg, change sound back to "full", and start FNV again with

$ WINEPREFIX=~/.wine-fnv wine ~/.wine-fnv/drive_c/Programfiler/Steam/SteamApps/common/fallout\ new\ vegas/FalloutNV.exe

In pure frustration I just kept hitting Escape and Left MouseButton (LMB) after pressing "Play".

The window for "serious error" seems to appear (it's being drawn), then it disappears again and the game loads like it should! Sweet!

Game is fully playable, however the character generator scene with the Doc is a bit buggy. The sound dies, and I can only see his lips move. When he stops talking I need to press Esc and Continue for him to continue. Anyway, once I'm out of bed the game works perfectly! My gfx card is a bit weak so I experience the occasional bit of lagging, but it's nothing serious and I've played for almost two hours without problem.

When I try to exit the game it locks up so I have to alt-tab my way so system monitor and kill the FalloutNV.exe process and then it shuts down.




After install, how to get the game running:

Start game and Steam with

$ WINEPREFIX=~/.wine-fnv wine ~/.wine-fnv/drive_c/Programfiler/Steam/SteamApps/common/fallout\ new\ vegas/FalloutNV.exe

When the launcher appears, click exit.

in a terminal, hit

$ WINEPREFIX=~/.wine-fnv wine ~/.wine-fnv/drive_c/Programfiler/Steam/SteamApps/common/fallout\ new\ vegas/FalloutNV.exe

again, and this time in the Launcher click "data files" and check for "load loose files", then hit play. When the game loads, hit Esc and LMB continuously. The game appears to crash before it continues loading. From here on it runs just fine.


Consider this a raw "worklog".

I'll post a refined version later.

Try to launch the game without :
bUseThreadedAI=1
iNumHWThreads=2

Because, i have a Core I3 330M (4 Cores) and with this option, the game crash but without, the game works correctly.

Hm! It appears the game did this itself, cause when I opened the file to look at it it was back to default. Weird.

On my system when I tried to run "New Vegas" first time, wine 1.3.6 not only crashed itself, but also caused segfault in my window manager (Enlightenment). So I had the only choice to completely restart X (attempts to restart window manager didn't help).
To avoid this problem I unchecked "Allow the window manager to decorate the windows" and "Allow the window manager to control the windows" boxes in winecfg graphics tab.

It seems to me that vcrun2008 is the problem.

My setup:
Ubuntu Maverick 32 bit
Intel E4500
2 GB RAM
Nvidia GeForce 9600 GT 512 MB

Wine 1.3.6

Tried to install directx9 and vcrun2008 through winetricks, this is my output:

Install of directx9 done
Renamed drive_c to harddiskvolume0
Using native,builtin override for following DLLs: msvcr90
Executing early_wine regedit c:\winetrickstmp\override-dll.reg
err:rundll32:wWinMain Unable to load L"streamci"
err:rundll32:wWinMain Unable to load L"streamci"
err:rundll32:wWinMain Unable to load L"streamci"
err:rundll32:wWinMain Unable to load L"streamci"
err:rundll32:wWinMain Unable to load L"streamci"
err:rundll32:wWinMain Unable to load L"streamci"
err:rundll32:wWinMain Unable to load L"streamci"
err:rundll32:wWinMain Unable to load L"streamci"
err:rundll32:wWinMain Unable to load L"streamci"
REGEDIT4

[HKEY_CURRENT_USER\Software\Wine\DllOverrides]
"*msvcr90"="native,builtin"
Executing wine /home/carl/.cache/winetricks/vcrun2008-ms09-035/vcredist_x86.exe
fixme:clusapi:GetNodeClusterState ((null),0x32ec24) stub!
fixme:advapi:DecryptFileA "c:\\31cce58ce355bb56d671\\" 00000000
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:advapi:LsaOpenPolicy ((null),0x33f324,0x00000001,0x33f34c) stub
fixme:advapi:LsaClose (0xcafe) stub
fixme:storage:create_storagefile Storage share mode not implemented.
fixme:advapi:LookupAccountNameW (null) L"carl" (nil) 0x7addcc (nil) 0x7addd0 0x7addc4 - stub
fixme:advapi:LookupAccountNameW (null) L"carl" 0x16a330 0x7addcc 0x17b4f8 0x7addd0 0x7addc4 - stub
fixme:advapi:LookupAccountNameW (null) L"carl" (nil) 0x7add98 (nil) 0x7add9c 0x7add90 - stub
fixme:advapi:LookupAccountNameW (null) L"carl" 0x1ad330 0x7add98 0x1c1c98 0x7add9c 0x7add90 - stub
fixme:msi:msi_unimplemented_action_stub MsiUnpublishAssemblies -> 10 ignored L"MsiAssembly" table values
err:msi:ITERATE_Actions Execution halted, action L"MsiPublishAssemblies" returned 1627
------------------------------------------------------
Note: command 'wine /home/carl/.cache/winetricks/vcrun2008-ms09-035/vcredist_x86.exe' returned status 91. Aborting.
------------------------------------------------------

Through various testing I've managed to get to the splashscreen where Bethesda claims its copyright etc, but when it's supposed to fade away the FalloutNV.exe crashes with a "serious problem".

Because I'm using Steam I don't know how to get a proper errorlog to paste here.

To get an error log on steam games, just run steam from the terminal.

had the same prob.
switching windows mode to xp worked for me

Hello,

I have a laptop, Samsung R580 with :
- Intel Core I3 330M
- Nvidia GeForce 330M
- 4Go Memory RAM
- Debian Sid 32Bits
- Nvidia drivers 256.53

The games runs correctly if you install "directx9" and "vcrun2008" with winetricks before to install the game.

Which wine version? Can you please post an exact list of proceedings? I get the first splash where it says everything about copyright, but then it crashes. Wine 1.3.6

I use Wine 1.3.6 with Fallout NV box version (no-steam).
I install the game in a clean prefix :

1- ~/Wine/Game/FalloutNV winetricks directx9 vcrun2008
2- ~/Wine/Game/FalloutNV wine /media/cdrom/Setup.exe

For your error when you launch the game, launch it in the console and paste the output here.

I made a mistake :
1- WINEPREFIX=~/Wine/Game/FalloutNV winetricks directx9 vcrun2008
2- WINEPREFIX=~/Wine/Game/FalloutNV wine /media/cdrom/Setup.exe

Okay, I'll try it out later today. Thanks for the tip. Still, I'm a bit puzzled that vcrun2008 aborts with "error 91" on me though.

Hm, I still get the same error with vcrun2008. Directx9 installs just fine.

Ah. I had to set windows version to Windows 7 for vcrun2008 to install. How do you override the Steam install? I can't figure out how to install the game w/o Steam.

did they mark this as a garbage app and it was gold the other day

Hi,


Fallout works for me (gold!) when applying the patch by hand and recompiling wine;
However (as I only became aware of later) the ratings are only for using the regular (unpatched) version of wine.

It looks like (but I didn't check) that the new version of wine has the patch build-in.

Alex.

Hi,

I just installed latest wine (1.3.6) and Fallout NV works ! (without the patch).
I did do all the steps described for Fallout3 ( in fact installed next to fallout 3).


Also I wanted to add that it indeed makes sense to only count ratings for the official Wine versions since otherwise it will be very hard to track what works and how....
(i didn't think about this and was just happy that i got it to work using the patch :-) )

Alex.

Hello,

Do you use a no-cd to play at this game?
Because, i installed d3dx9 and vcrun2008 with winetricks and after, i installed the game.

And i replace the .exe (FalloutNVLauncher.exe and FalloutNV.exe) by the no-cd and the wine crash when i launch the game.

I use wine 1.3.6 and the version no-steam.

Hi,

I think you need the new d3dx9 that is compiled specifically for your version of wine (so maybe not the winetrick-version). there should be a hint/error message somewhere in your output about this.

Which version of d3d9 you need depends on the version of wine you are using.

What version of wine do you have ?
Can you post the output on your terminal when wine crashes?
( btw: my system is debian squeeze, 64 bit)

Alex.

Hi Alex,

I have Wine 1.3.6 and with this wine version, the bug of d3d9 if fixed no ?

When i launch the game with FalloutNVLauncher.exe, wine crash after the splash screen like in the screenshot :
pix.toile-libre.org/upload/original/1288536584.png

And in the output console, i have this message :
pastebin.com/5RsrhiED

Thanks

I forgot to specify that i use Debian Sid 32bits + drivers 256.53

Hi,

>>I have Wine 1.3.6 and with this wine version, the
>> bug of d3d9 if fixed no ?

Yes, it is.
However you might have replaced the ´working´ d3dx9 with an older one using winetricks. You can try to replace that file with the newest one you compiled.

Your error messages seem to indicate some problem with d3dx9, and it might be an imcompatibility with your wineversion.

Alex.

PS although it shouldn´t really matter, try runnin falloutNV.exe instead of the launcher.

When you launch d3dx9 with winetricks, there were only these files who are extract in system32 : d3dx9_24 to d3dx9_42.
And the 'working' file is d3d9 so is not replace by this command.

For my wineversion, i compiled myself the source.

If i launch FalloutNV.exe, i have the same error... :(

Other question,

Have you installed comctl32 with winetricks ?
If i install this, regedit crash and the game doesn't works too.

mmm, I don;t remember about comctl32. (did it when playing FallOut 3)
However, regedit works for me.

One other thing: I get a similar error ( i think, my french is not so good :-) ) when running at a high resolution.
Did you try running lowest resolution ?

Good luck,

A.

In the launcher, i can only use these resolution :
1366x768 or 1360x768

I will change in falloutnv.ini and try it

Ah, for me it works only at lower resolution. The highest ( similar to resolutins you say) do not work.
Best performance is for me at 800x600, but a bit higher works too. (but i have a somewhat older videocard).

Doesn't works even if i change resolution...
I stop it... :(

Ah, i see you got it to work now :-)
What was the problem ?

A.

I installed directx9 instead of d3dx9 and i resolved the problem :x

I bet everyone is busy playing Fallout New Vegas... :)

I'm using Ubuntu 8.10, kernel 2.6.27, gcc 4.3.2, nvidia drivers 256.53.
The machine is a core2duo with 2 GB ram and GF 8600GT graphics card.
The game was installed and played though Steam.

Prior to installing the game itself, I followed the winetricks procedure described for Fallout 3 excluding the Live client installation.
I disabled the `gameoverlayrenderer' dll using winecfg.

The game was crashing after a couple of minutes of walking around in the wasteland, and upon entering interiors. The messages produced when the game crashed were:

err:d3d:resource_init Out of adapter memory
err:d3d9:device_parent_CreateSurface (0x1b5264) CreateSurface failed, returning 0x8876017c

Apparently wine is not detecting my video memory size (512 MB) correctly. I fixed this by adding the registry key:

[HKEY_CURRENT_USER\Software\Wine\Direct3D]
"VideoMemorySize"="512"

After this the game is playable. The game behaves well, at least with default graphics settings and 1280x800 resolution.

Weird issue here. New Vegas is only stable at the lowest resolutions possible: 800x600 or 800x500, and with the lowest possible graphics quality settings. As I bump up the resolution slowly the game may crash when I look at the pip boy, go to the game menu, enter an inventory menu when looking in a container, or loading a new game area as I enter or leave a building. As I bump up the resolution more, the game will crash when I continue from a saved game, right when it is about to render the game world.

I can run Fallout 3 with no issues and at appropriately high resolution and graphics quality, fullscreen.

Ubuntu 10.04
Core2 Duo 2.8GHz
4GB RAM
GeForce GTS 160M/PCI/SSE2
Using the current Proprietary Nvidia drivers with Ubuntu 10.04
Wine 1.3.6 compiled from source which has the fix for the gamebryo renderer error

I hesitate to create a wine bug ticket since this seems like it may be a configuration issue on my part, but it may be related to specific hardware. Let me know if you are having similar issues.

Here is the very short and cryptic winedbg output when the crash happens. Should probably mention I'm running 64bit.


Wine-dbg>info proc
pid threads parent executable (all id:s are in hex)
0000000e 3 0000000a 'services.exe'
00000011 4 0000000e 'winedevice.exe'
00000019 1 0000000c 'explorer.exe'
0000001d 22 00000008 'Steam.exe'
0000003a 22 00000027 'FalloutNV.exe'
Wine-dbg>attach 0x3a
0x005e3542: movl %ebp,%esp
Wine-dbg>cont
Unhandled exception: page fault on read access to 0x0010b963 in 32-bit code (0x0010b963).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:0010b963 ESP:0033e9b8 EBP:21000700 EFLAGS:00010206( R- -- I - -P- )
EAX:7eae5a00 EBX:1b0d3b40 ECX:0033e9f4 EDX:0010b963
ESI:00000000 EDI:0587fe80
Stack dump:
0x0033e9b8: 00e6dd61 7eae5a00 0033e9f4 0587fe80
0x0033e9c8: 0887f934 1b0d3b40 00000fff 00000024
0x0033e9d8: 0000196e 001f3ab0 00000000 00000024
0x0033e9e8: 1c0f90b4 0033ea00 00000001 00000024
0x0033e9f8: 011ebd38 011bbc80 0033ea28 0033ea40
0x0033ea08: 00a9a382 00e69826 0887f934 00000000
Backtrace:
=>0 0x0010b963 (0x21000700)
1 0x00000002 (0x010e4dec)
2 0x00cf42a0 in falloutnv (+0x8f429f) (0x00e6fa00)
3 0xb9502c46 (0x8bf18b56)
0x0010b963: addb %al,0x0(%eax)

Hello,

I compiled latest git version and copied the d3d9.dll.so file from that to the /usr/lib32/wine to get rid of the gamebryo error (using an ubuntu-ppa 1.3.5 version).

I have a set of problems.
1) Audio sometimes stops for like 10 seconds and then returns (I tried setting audiofade in the ini file to 0, but that doesn't seem to be the problem). I'm using alsa. Never had been a problem on any other game including Fallout 3.

2) I get pagefaults when trying to enter specific locations. This happens for example on Helios Power station. When I try to enter, the loading screen appears with the roulette-ball spinning. After a while it stops moving, sound stops and nothing happens.

3) Sometimes I just get a blank screen when the game starts. Closing it and starting again seems to fix it most of the time.

4) Random crashes happen a lot, like after playing 10-20 minutes. Reload from save and I can continue.

Okay, problem 2) and 4) did not occour again after setting the graphics settings to LOW. I can enable ansiotopic filtering and 1280x1024 resolution.

Sorry, n00b here...
Launcher works fine, but the game crashes after the loading screen appears.
Running Wine 1.3.5 (applied patch from bugs.winehq.org/show_bug.cgi?id=24831), on Ubuntu 10.04 LTS (Lucid Lynx).

Log from terminal here:
violence.iespana.es/NVCrash

Hi,

How did you apply the patch ? (either patched wine or just replaced the dll-file ?

Patching wine works fine for me ( wine 1.3.5, patched, on Debian Squeeze 64bits). I launch the game directly, not via the Launcher...

A.

Patched and compiled wine.

I've hit the same problem here.

It's a threading problem, so with a bit of luck Bethesda Softworks will run into similar problems with Windows and provide a update... If not, well, then YOU[not me] will have to fix wine.

Trying with wine 1.3.6... d3d errors, and something about quartz.dll...
Tried both native & builtin quartz, native appears to give the least errors (builtin results in like a dozen "quartz.dll not found" messages).

New log:
pastebay.com/109001

Oh, BTW, Fallout 3 is running fine, this must be something specific to New Vegas.

In Fallout 3 I had issues with VATS and textures occasionally. It was always accompanied by a memory related message in the terminal. I'd try setting the texture settings lower to see if that helps.

Oops I meant to have this be a response to the below message.

I was able to start the game successfully (after the fallout 3 things are installed + bug patch applied) but all the characters are missing clothes and skins. So eg: the doc in the beginning has only hair and eye. Mine character is similar but has gun + pipboy on it too. Dog have only eyes.
The VATS shows 0% chance to hit anybody...
It is vary hard to play like this :-)

Any idea?

picasaweb.google.com/lh/photo/3PvKfgbjoPP2Cv9NrJCQwg?feat=directlink

Here is how I look like.

How did you get the game, It has been proven that the steam version downloaded corrupted texture files which lead to the infamous doc glitch where his head would spin while talking.

I have the DVD version.Meanwhile I have tried with wine 1.3.5 but with the same result. Installing under normal Win7 it works fine. Can it be some configuration error of wine?

Did you put Fallout:New Vegas in its own prefix. Its the only configuration problem I can think of that might make a difference.

Solution:
* Start wine regedit
* Create key "HKEY_CURRENT_USER/Software/wine/Direct3D", create string "UseGLSL", set value to "disabled"

See ubuntuforums.org/showthread.php?p=10361115#post10361115

Hi,

I had the texture problem and I tried this manipulation but the game won't launch at all (I have the icon in the control panel but it won't go further and my desktop freezes).

Any clue?
Thank you !

PS : this bug reminds me of Morte, the flying skull in Planescape Torment !

I realize that my previous post was a bit light.

I have a Radeon HD5830 with the 11.2 catalyst driver and 10.10 Ubuntu.

If UseGLSL = enabled > no NPC texture
and if UseGLSL = disabled > the game doesn't launch

I install with winetricks vcrun2008, d3dx9 and cc580. After this i see launcher and can change settings, but after hitting play i get error " no sound card detected" Anywhere else is sound pretty normal.

Run FalloutNV.exe after configuring with the Launcher, will work if you have applied the patch

And where can i found this patch?

I had this issue too (1.3.11), but I kept clicking and it started working after the launcher's own intro music ended, like the intro was locking the sound card and confusing it. So I tried renaming MainTitle.wav so the launcher wouldn't be able to find it to play it, and the problem went away.

I tried to run it through my old prefix for Fallout 3 and I got the error" Failed to initialize renderer, unknown error creating gamebyro renderer." So I put New Vegas in its own prefix and replaced vcrun2005 or vcrun2008 since it now requires that and same error. I am not sure why it is not working as no error in console.

Ubuntu 10.04

Same exact thing for me. wine 1.3.5, Arch linux 64 bit, nvidia gtx260 using the 260.19.12 drivers. Im able to open the fallout launcher and change the settings...but everything i have tried has no effect and i get the same error everytime. Really hope this is something minor and a easy fix.

There is a patch added to this bug, it works. Imo the game is golden

How do you apply the hack/patch? Been running into the same issue gamebryo issue

Just compiled latest wine with that patch and it does indeed make the game work. Have only played it for around 15 mins and it played VERY well....had slightly low fps...but all the settings where the default that fallout chose...most things where on ultra and all effects enabled. Im sure i can squeeze some extra fps by tweaking the settings in fallout and the wine registry.

I might say this is working as High as Plat after the patch. With my settings I am getting very good fps ( visual only because my fps counter seems to be broken. every game reports me at 1-3 fps even though I see no jittering and regardless of settings)

how did you go about applying the patch? and would you happen to know how to do this in a playonlinux prefix?

No, I don't have the slightest idea how you would do it with playonlinux. You need to build wine from source anyway, so you probably don't need playonlinux.

I made myself a git-repository according to this: wiki.winehq.org/GitWine

applied the patch and compiled wine:
/usr/src/wine-git# patch -p1 < falloutnv.patch
/usr/src/wine-git# ./configure
/usr/src/wine-git# make

However, now I've got a different crash. The title-screen appears, followed by an "Unhandled Page fault" shortly thereafter.

The console gives me this error:
err:d3d:IWineD3DImpl_CheckDeviceMultiSampleType Unable to color bits for format 0x24, can't check multisampling capability!
And alternatively a few ten-thousand lines of
fixme:d3d9:IDirect3DDevice9ExImpl_CheckDeviceState iface 0x1a1fa8, dst_window (nil) stub!
after it.

I had that error too then I configured the regedit with the ff;

DirectDrawRenderer='Opengl'
Multisampling='Disabled'
OffScreenRenderingMode'fbo'

It stopped crashing. but then again it might act up and crash again...

but I hope this helps.

Could you please specify the path to where you did this? Is the game working correctly for you now?

HKEY_CURRENT_USER > Software > Wine > Direct3D

if there is no Direct3D folder, just make one. and enter the values in my recent post.

the game works perfectly, but at first I get crashes. to get around this, I changed the windows version to Vista and load the game, then change the version again to XP and reload the game.

you only need to do this once (in my case) then no more crashes!

hope this helps

i was having this error last night solved by installing the wine 1.3.10 game launched right afterwards didn't have to do the escape sequence thing or nothing .have the same as mentioned above. offscreen rendering fbo and direct draw render set opengl..also in the wine config i had to set audio to esound driver, set comcat32 to built in under libraries(not sure if that did anything but i have been playing 15 minutes @ ultra high graphics settings with 1024x768 and have noticed anything out of the ordinary.

Same engine as fallout 3. So the things in appdb.winehq.org/objectManager.php?sClass=version&iId=14322 should apply to this version as well.