Game Wont Play, Help Please?

[M48A5]

@GrindedStone

I saw that in the original post. Different game made for different systems. One example of this is that Fallout3 does not run properly on systems with a cpu with more than two cores. That's why there is a tweak for the .ini that will limit the cpu to only two cores when running the game. I don't have Fallout NV, so I am in the dark as to want the requirements are for that game. Regardless, he still cannot run Fallout3 properly.

[GrindedStone]

This isn't as helpful or wasn't ever helpful. Later in the post I found a 64 an counting post at windows seven forums. It seemed to me like better information that we can offer at this time. Posthumously changed to better information via specialist due to the complex nature of the problem.Fallout 3 Windows 7 @ Windows 7 Forums

 

Windows media player should be set up as the default player for .mp3 an .wav do this by finding a .mp3 an .wav an double clicking it to see what program opens it. If it's not WMP then you need to set it up. Right click the file, open with, chose program, check the always open with button. You can get WMP an more on the automatic updates web-page Microsoft Automatic Updates You can get lots of stuff there or the Microsoft download center.

 

You should install it in C:/program files/x86/bethesda softworks You can set UAC to ignore Fallout, thus being able to use both. That is what the x86 folder is for, 32 bit software... You shouldn't tweek anything in the config .ini until you get it running okay. Patch the game to 1.7 even if you have the GOTY edition then go to MyDocuments/MyGames/Fallout3 find Fallout an FalloutPref delete both of them. Then go to the game's folder C:/program files/x86/bethesda softworks/Fallout 3 Find the .exe that says launcher on the end, launch that. This will auto detect your system an also generate the config files you just deleted, dont tweek it.

 

Disable HDR-Bloom it ruins white an also isn't required the lighting FX are built into the game, HDR is just glowing colors it also ruins the color white. Disable shadows because they switch back an forth from one NPC to the other depending on which is closer to the player, hard to ignore how stupid it is. Set it up to run in windowed mode. Then go inside the game, set grass, object fade, tree LOD fade to 1/2, set the other sliders to 4 clicks or less, 2 click on actors if you want. Then set the sliders for music an radio all the way down to zero. If you want to hear music later on you can only turn it on when you actually want to hear it, rather than loading into it.

 

I got the retail 1.0 disc when Fallout launched. The last time I installed it GFWL actually broke the game after I put the key in for it. So what I did was use FOMM, FOSE, and the GFWL disabler to basicly disable GFWL. FOSE does this to a degree, but the GFWL disabler on Nexus actually contains a fake version of the Xlive.dll The question is how much do these effect the .mp3 DRM to which is a possible cause for the Win7 freezing issues. It's the launcher we use to run mods on the game, but it's worth a shot.

 

Fallout Mod Manager @ Nexus Installs in x86 I guess looks up the directory for the game. Set it to not automaticly update or search for updates. It will also launch new vegas but set it to automaticly set the configs to not read only. Create dummy folders for FO3 an FNV to store mod information in.

 

FOSE at silverclock.org installs in the game directory bethesda softworks/fallout 3 where the .exe is located. FOMM will also automaticly detect if you have FOSE an launch the custom .exe instead of the actual game .exe

 

GFWL disabler at Nexus It will disable GFWL just like FOSE, but unlike FOSE it also contains a fake version of the Xlive.dll which might have something to do with the DRM of the game maybe pertaining to .mp3 an audio codec issues.

 

If this doesn't work then you should consider the K-lite audio codec packs 32 an 64 bit. Then it's probably time to start un-installing 3rd party software an foundation software. Like any audio/video software you use including the K-lite packs you just dropped in Visual C++, .NET framework, direct x clean the registry, an try installing them again. There are also many players that have done this or that as a process in order to get the game running, the stuff above seemed like less work though. Search the internet an the nexus forums

Edited January 26, 2012 by GrindedStone

[theophantus]

Windows media player should be set up as the default player for .mp3 an .wav do this by finding a .mp3 an .wav an double clicking it to see what program opens it. If it's not WMP then you need to set it up. Right click the file, open with, chose program, check the always open with button. You can get WMP an more on the automatic updates web-page Microsoft Automatic Updates You can get lots of stuff there or the Microsoft download center.

 

You should install it in C:/program files/x86/bethesda softworks You can set UAC to ignore Fallout, thus being able to use both. That is what the x86 folder is for, 32 bit software... You shouldn't tweek anything in the config .ini until you get it running okay. Patch the game to 1.7 even if you have the GOTY edition then go to MyDocuments/MyGames/Fallout3 find Fallout an FalloutPref delete both of them. Then go to the game's folder C:/program files/x86/bethesda softworks/Fallout 3 Find the .exe that says launcher on the end, launch that. This will auto detect your system an also generate the config files you just deleted, dont tweek it.

 

Disable HDR-Bloom it ruins white an also isn't required the lighting FX are built into the game, HDR is just glowing colors it also ruins the color white. Disable shadows because they switch back an forth from one NPC to the other depending on which is closer to the player, hard to ignore how stupid it is. Set it up to run in windowed mode. Then go inside the game, set grass, object fade, tree LOD fade to 1/2, set the other sliders to 4 clicks or less, 2 click on actors if you want. Then set the sliders for music an radio all the way down to zero. If you want to hear music later on you can only turn it on when you actually want to hear it, rather than loading into it.

 

I got the retail 1.0 disc when Fallout launched. The last time I installed it GFWL actually broke the game after I put the key in for it. So what I did was use FOMM, FOSE, and the GFWL disabler to basicly disable GFWL. FOSE does this to a degree, but the GFWL disabler on Nexus actually contains a fake version of the Xlive.dll The question is how much do these effect the .mp3 DRM to which is a possible cause for the Win7 freezing issues. It's the launcher we use to run mods on the game, but it's worth a shot.

 

Fallout Mod Manager @ Nexus Installs in x86 I guess looks up the directory for the game. Set it to not automaticly update or search for updates. It will also launch new vegas but set it to automaticly set the configs to not read only. Create dummy folders for FO3 an FNV to store mod information in.

 

FOSE at silverclock.org installs in the game directory bethesda softworks/fallout 3 where the .exe is located. FOMM will also automaticly detect if you have FOSE an launch the custom .exe instead of the actual game .exe

 

GFWL disabler at Nexus It will disable GFWL just like FOSE, but unlike FOSE it also contains a fake version of the Xlive.dll which might have something to do with the DRM of the game maybe pertaining to .mp3 an audio codec issues.

 

If this doesn't work then you should consider the K-lite audio codec packs 32 an 64 bit. Then it's probably time to start un-installing 3rd party software an foundation software. Like any audio/video software you use including the K-lite packs you just dropped in Visual C++, .NET framework, direct x clean the registry, an try installing them again. There are also many players that have done this or that as a process in order to get the game running, the stuff above seemed like less work though. Search the internet an the nexus forums

 

Ok , i suppose this relates to my post aswell.

 

Im getting a conflict though between the two posts.

 

Do i install in: C:/program files/x86/bethesda softworks (which the game installs by default) or don't i, because ive been advised not to put it in the programme files, but to put it in C:/ at the custom set up?

[GrindedStone]

x86 but set UAC to ignore fallout rather than disabling UAC. If you are an advanced user then just disable UAC. These two games like to be defragmented after install. That is if you still have a hard drive, SSD you don't defrag.

 

The 1.7 patch is from the official site you can also get it at Nexus Official site 1.7 patch

 

A better way to look at it is that the x86 folder adds support for 32 bit applications in a 64 bit opperating system, then running applications in compatability mode provides support for applications designed to run on other opperating systems. Fallout was designed to run on Windows XP SP3. Any of the foundation software you get like Visual C++, .NET framework, windows media player, or even K-lite they all get installed to the default locations in the installer for 32 bit or 64 bit.

Edited January 25, 2012 by GrindedStone

[theophantus]

x86 but set UAC to ignore fallout rather than disabling UAC. If you are an advanced user then just disable UAC. These two games like to be defragmented after install. That is if you still have a hard drive, SSD you don't defrag.

 

The 1.7 patch is from the official site you can also get it at Nexus Official site 1.7 patch

 

A better way to look at it is that the x86 folder adds support for 32 bit applications in a 64 bit opperating system, then running applications in compatability mode provides support for applications designed to run on other opperating systems. Fallout was designed to run on Windows XP SP3. Any of the foundation software you get like Visual C++, .NET framework, windows media player, or even K-lite they all get installed to the default locations in the installer for 32 bit or 64 bit.

 

Thanks for the reply.

 

How do I set UAC to ignore fallout?

[GrindedStone]

You also need to be an admin on the computer for many of these gamer programs. I'm guessing it's just like a firewall an you add exceptions. The person that told me about it didn't say how. I would imagine it's located on the control panel in UAC settings. UAC could pop up a warning on Fallout to which you could pick ignore an such in a prompt. A lot of these gamer rumored problems are just that, rumor, they don't effect every player on every computer. My friend for example only had to run Fallout 3 in compatability mode to get it to work on Win7. There wasn't anything special he needed to do.

[theophantus]

You also need to be an admin on the computer for many of these gamer programs. I'm guessing it's just like a firewall an you add exceptions. The person that told me about it didn't say how. I would imagine it's located on the control panel in UAC settings. UAC could pop up a warning on Fallout to which you could pick ignore an such in a prompt. A lot of these gamer rumored problems are just that, rumor, they don't effect every player on every computer. My friend for example only had to run Fallout 3 in compatability mode to get it to work on Win7. There wasn't anything special he needed to do.

 

Well ok, I don't know how to run it in compatibility mode either.

To be honest I don't even know what UAC means.

I'm proberly one of the unfortunate ones who can't get the bloody thing to work.

It's never the case with computer games, that you can just pop the disc in and play straight away.

I suppose that's why consoles are the best medium to play games, minus the modding side of things of course.

[BlackRampage]

Well ok, I don't know how to run it in compatibility mode either.

Shouldn't be necessary.

 

To be honest I don't even know what UAC means.

UAC = User Account Control. It's a really "helpful" feature that comes with both Win Vista and Win 7.

Disable User Account Control (UAC) the Easy Way on Win 7 or Vista

 

I suppose that's why consoles are the best medium to play games

I beg to differ.

 

And I really don't see why you go through the effort of (attempting) to install Fallout 3 in either of the program files folder either. Just install it in some other folder and you won't even need to bother with UAC.

[theophantus]

Well ok, I don't know how to run it in compatibility mode either.

Shouldn't be necessary.

 

To be honest I don't even know what UAC means.

UAC = User Account Control. It's a really "helpful" feature that comes with both Win Vista and Win 7.

Disable User Account Control (UAC) the Easy Way on Win 7 or Vista

 

I suppose that's why consoles are the best medium to play games

I beg to differ.

 

And I really don't see why you go through the effort of (attempting) to install Fallout 3 in either of the program files folder either. Just install it in some other folder and you won't even need to bother with UAC.

 

 

I've tried to put it in another folder and got the same issue. I've un-installed and re-installed in 4 different places.

 

Each time i got the black screen & CTD when I pressed play.

 

The process has got to be disabling the UAC next, which I've not done yet.

 

There are a few suggestions given out these last couple of days on this forum, I'm a bit lost what to do really to be honest.

[GrindedStone]

Well you don't know that there is even a problem with UAC yet, trust me you need it on. If there is a problem it will let you know. Unless it's Bill Gates that comes in here, don't listen to them. They're just trolling. Where are you at right now? Edited January 25, 2012 by GrindedStone