Fallout 3 - framerate tanks when shooting/being hit, seems to go away if I wait 24 hours

Toggle sidebar Toggle sidebar
S

sno0ks

Honorable
Jun 11, 2015
61
0
10,630
This has been bedeviling me for days. I've done the ini tweaks for multicore processors. I'm using FOSE and the LAA to increase the amount of memory the game uses. When participating in combat, my framerate will drop to a crawl for a second or two when either me or an opponent makes a hit. It doesn't happen every time, and it appears to go away at least temporarily if I wait 24 hours. Does anyone have ANY idea what's causing this and how to fix it? There's something about the 24 hour waiting. It refreshes the map or some crap.

win 8.1
16gb ram
gtx 970
i5-4460 3.2ghz
 
Sort by date Sort by votes
I've done a clean install and validated files. This also existed before I installed the FOSE/LAA (no other mods). The whole reason I did the FOSE/LAA was because of this issue. I'm investigating my Sound Blaster Z audio card. I read somewhere that that might be conflicting with the game. I can't run Fable TLC with it activated, so I just disabled it and am testing it now.
 
Upvote 0 Downvote
Well now I'm damned confused. I tried disabling sound blaster via device manager, but my onboard realtek hd audio wasn't working.... I distinctly remember for Fable just disabling sound blaster and the onboard sound just automatically worked after restarting. wtf
 
Upvote 0 Downvote
I'm dumb, I just didn't have it plugged in the right jack. Tested onboard realtek audio and the problem persists, so I can rule out a sound blaster conflict.

I have no idea what would be causing this. I've done the FOSE and LAA and fixed the ini's for my multicore processor. I'm not having any CTDs. Just this retarded FPS drop that only occurs when hitting enemies or taking hits from enemies, and not on every hit, and it seems to be remedied by waiting 24 hours.

I read on a Playstation forum about the waiting 24 hours trick. The user said this problem is a "map leak," which I'm guessing he means memory leak having to do with the map. The 24 hour wait does seem to fix it as far as my testing tonight. This is so stupid.

Tomorrow I'll test it with all AA turned off. Transparency multisampling might be the culprit if it's being caused by the blood. Who knows? I'll turn off transparency AA and try it. If that doesn't work I'll try turning off regular AA as well and see what happens.
 
Upvote 0 Downvote


I have not, but reviewing the notes the restoring of cut content/shifting of some quest rewards makes me want to try it out. If I install it will it work with my current save or do I have to start fresh?

I'm going to test my multisampling theory before trying the patch to see if it's causing the problem. My rig is more than capable of running the game with AA, but the shoddy engine could be to blame. It runs MGS5, which is amazingly optimized, maxxed at 1080p with 8x AA and 8x transparancy AA on 1 card at 60 fps. This Fallout issue seems to be CPU related, but I haven't checked the loads.

I'll go from 8 to 4 to 2 and see if it changes anything.

UPDATE: just tried it quick by fiddling with the ini and it doesn't seem to be the issue. I'll try the patch and report back tomorrow, but I'm not holding my breath. I fear this game is just crap on modern hardware. I've tried several compatibility modes and it doesn't change anything.
 
Upvote 0 Downvote
Fallout is indeed CPU limited. You shouldn't have issues like you are with pretty much stock fallout.

I'm pretty sure you have to start fresh with the unofficial patch. It overwrites content you have most likely already done so it can cause some weird bugs.
 
Upvote 1 Downvote
Here's an old post on the steam forums discussing this issue: http://forums.steampowered.com/forums/showthread.php?t=1242154

Also this: http://www.gamesas.com/combat-fps-slows-crawl-t120750.html

And this: http://steamcommunity.com/app/22370/discussions/0/35222218627483983/

one of the people suggests the unofficial patch, too, but as with pretty much all of these threads no one provides info on a solution that's worked. Considering they end up ending the conversation maybe they fixed it.

I'll also try updating my sound drivers.
 
Upvote 0 Downvote


already did that, i'm afraid. threaded ai 1 and numhwthreads 2. fixed the issue temporarily, but it came back.
also i think the LAA incorporates those tweaks as well.
 
Upvote 0 Downvote
Have you tried booting you PC with just 2 processor cores and trying to play the game like that?

Here's how to do it

Windows key + R >> "msconfig" >> "Boot" Tab >> "Advanced Options" >> Check "Number of Processors" and select "2" from the drop-down box.
 
Upvote 1 Downvote
I'll try that.

I'm also going to try borderless windowed and also turning off v-sync. i have fpsclamp set to 60 so v sync is redundant and they could be conflicting with each other. i know that if your fps ever drops below 60 it will chug, so maybe im dipping to 59 with some blood spatters and that's causing it. I'm pretty sure it happens without fpsclamp, though, and without fpsclamp the game is a jittery unplayable mess, so maybe v sync is to blame. i know some people have issues with it.
 
Upvote 0 Downvote
I think I might have finally fixed it. After a work day's worth of time fiddling with things. I'm a little hesitant to count my chickens, considering how many false hopes I've had during this process.

I downloaded a borderless window mod, which required some finagling to get it to work with steam so that the overlay and time played counter works. The instructions are in the link below.

Apparently fullscreen causes significant performance loss, and it could be responsible for CPU lag caused by the blood or something.

Like I said, I'm hesitant to say anything's fixed, but both saves that were giving me issues every single time are now not giving me issues. Fingers crossed.

http://www.nexusmods.com/fallout3/mods/18909/?
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom