Fallout 4 PC Performance Thread

Sorry to say this, but iFPSClamp=60 may get rid of the stutter, but it also breaks certain game functions.

For one, sealed doors that need to be opened with consoles will not open, nor would a vault in a certain quest I was playing...until I disabled iFPSClamp.

Trust me, I really, really wanted to keep it enabled, but after repeated tests, it WILL cause the above, maybe more; I didn't want to find out what else.

Ugh... I wish I knew this earlier.

I removed the line but my vault doors still won't open using a save from before I tried to open it. So now I'm stick being unable to open a vault door for a quest line...
 
I had this issue at one point with my GTX 980s, but a reboot resolved it. Try doing a clean boot and remove everything non-essential from your start up.

Ya shoot., One of the first things I did and nada. Its killing my soul.

I've never had that issue happen even once with my 980.

Well thats not very helpful to us that do but lol I am glad its working for ya :) I wish we all could say that.
Now if you had it and had fixed it that would have rocked. Because sadly thats where we are right now if impacted.
 
I wish I knew that too. I couldn't get the door on Vault 114 to open. The animation would play but the vault door never opened. I had to use the tcl command to clip through the door. I wasn't able to use V.A.T.S. once I was inside though. Thankfully I was able to successfully finish the quest. I've always had to use certain commands to finish broken quests in Bethesda games. Part of the problem playing it when it first comes out.
 
Why are people suggesting to limit the framerate with Rivaturner instead of just forcing triple buffer v-sync through the drivers? Do you get better performance that way?

For many people, myself included, only using vsync doesn't get rid of the stutter that can occur despite having a solid 60 fps. Limiting the FPS on top of vsync fixes it.
 
I wish I knew that too. I couldn't get the door on Vault 114 to open. The animation would play but the vault door never opened. I had to use the tcl command to clip through the door. I wasn't able to use V.A.T.S. once I was inside though. Thankfully I was able to successfully finish the quest. I've always had to use certain commands to finish broken quests in Bethesda games. Part of the problem playing it when it first comes out.

VATs is buggy as hell in general. I lost hours worth of progress when I didn't realize that trying to open the Vault 81 door bugged VATs permanently for me. I never even used console commands, just tried to open the door and boom VATs was gone. Since I hadn't engaged in combat for hours (was settlement building), I ended up losing a couple of hours worth of progress.

...and now, I can't open Vault 114.
 
VATs is buggy as hell in general. I lost hours worth of progress when I didn't realize that trying to open the Vault 81 door bugged VATs permanently for me. I never even used console commands, just tried to open the door and boom VATs was gone. Since I hadn't engaged in combat for hours (was settlement building), I ended up losing a couple of hours worth of progress.

...and now, I can't open Vault 114.

Bleh. My vats isn't working now either. And I had to use tcl to get through the vault 114 door. Also using ifpsclamp=60. Sonovo...
 
Ugh... I wish I knew this earlier.

I removed the line but my vault doors still won't open using a save from before I tried to open it. So now I'm stick being unable to open a vault door for a quest line...

I wish I knew that too. I couldn't get the door on Vault 114 to open. The animation would play but the vault door never opened. I had to use the tcl command to clip through the door. I wasn't able to use V.A.T.S. once I was inside though. Thankfully I was able to successfully finish the quest. I've always had to use certain commands to finish broken quests in Bethesda games. Part of the problem playing it when it first comes out.


Yeah, mine happened in the quest at Vault 114 also. The first time I attempted to open the vault, my character performed the full animation, but the plastic cover on the button never flapped up, so he was essentially not hitting the button, and thus not triggering anything.

I had saved right before I opened the door, reloaded, and tried again, but it did the same thing every time. The only thing that fixed it for me was to remove iFPSClamp from my ini and reload at the beginning of the area. After that, the plastic flap finally popped up and allowed the animation to trigger the vault's opening.

As I previously mentioned, the tweak also renders terminal locked doors permanently shut; I would try to open one, the terminal would say it's "opening", I'd back out, and nothing would trigger. I'd then remove the tweak, and it worked. I would then put the tweak back, just to see what would happen if I tried opening another door of its kind, and sure enough, the same thing would happen on every one of them until I removed the tweak.

It's really too bad, seeing as iFPSClamp completely removes stuttering for those of us that can sustain 60+ FPS at all times. I'm just a bit confused as to why the Fallout games all have this stuttering issue when Skyrim doesn't, seeing as they run on the same engine.
 
For the no one that was asking: FO4 does run comfortably above 30FPS on my Iris Pro 5200 at 1440x900 (for an integer scale of my retina screen), with a mix of settings (textures med, most things low, I think lighting high, god rays low). Haven't optimized fully yet. If I want to drop to 720P I could probably rock mostly mid-high.
 
Anyone tried this yet that have a quad core or more?

https://www.reddit.com/r/pcgaming/comments/3t1hpy/fallout_4_pc_multithreaded_toggle_commands/

Supposedly fixes the slow to pop in textures, among other things. Going to try it later today I think

BvyOwM9IcAAtLcQ.jpg
 
Any sites that list which graphics settings are the most taxing?

I get some framerate dips while outside. I tried turning off AA but that didn't change anything.
 
Ugh... I wish I knew this earlier.

I removed the line but my vault doors still won't open using a save from before I tried to open it. So now I'm stick being unable to open a vault door for a quest line...

Yep, I started the game fresh with that setting and couldn't get out of Vault 111. Thankfully I was at the very beginning of the game. Removed that setting, started completely over, and the vault opened.

Remove that setting, people.
 
I tried this out and it did absolutely nothing for me. As with all the other 'tweaks' that have been posted on Reddit, it's provided with no evidence that it actually works...

I heavily advise against applying pretty much all of these random ini tweaks people are suggesting. iNumHWThreads is okay and that's pretty much it, but even that may not actually provide any tangible benefit.

The FPSClamp one will break your game. DO NOT USE IT.
 
Even though the iFPSClamp setting can bug vault doors ,I can't bring myself to get rid of it. It's too smooth with it on. No other tweak gets rid of 100% of the stutter. It hasn't interfered with doors locked through terminals that I can recall in 18 hours of playtime. I applied the tweak shortly after leaving Vault 111 around an hour into the game. I can be the guinea pig for playing like this. Should be able to either reload a save or clip through an area impossible to get to.

EDIT: Phone autocorrect sucks
 
Sorry to ask, as I'm sure it has been asked a million times, but way too many pages to read thru. For the i3 Alpha owners out there, what are the best settings for this?
 
Cross-posting from the modding thread:

Fallout 4 - Texture Optimization Project
By default in fallout 4 a LOT of textures come in huge resolutions with horrid compression for example 2048x2048 ground textures that take up 5.4mbs for 1 texture - which i turn into a 1024x1024 identical texture with better compression only taking up 650kbs (6/10ths of 1mb - literally 1 fifth of the data usage) but sense there isn't a working method for automatically resizing and compressing the base game textures ill be doing it manually which will take some time.
I'd love to see some reports. Sounds amazing.
 
Even though the iFPSClamp setting can bug vault doors ,I can't bring myself to get rid of it. It's too smooth with it on. No other tweak gets rid of 100% of the stutter. It hasn't interfered with doors locked through terminals that I can recall in 18 hours of playtime. I applied the tweak shortly after leaving Vault 111 around an hour into the game. I can be the guinea pig for playing like this. Should be able to either reload a save or clip through an area impossible to get to.

EDIT: Phone autocorrect sucks

It can break quests, too. One main story quest in particular will not progress in some instances with it switched on.
 
FPSClamp isn't an option for those of us that can't hit a solid 60, so please stop portraying it as some sort of holy grail fix-all for the game, 'cause it ain't. Besides, my performance is plenty smooth without it, even if it only holds in the 40s most of the time.
 
FPSClamp isn't an option for those of us that can't hit a solid 60, so please stop portraying it as some sort of holy grail fix-all for the game, 'cause it ain't. Besides, my performance is plenty smooth without it, even if it only holds in the 40s most of the time.

For real. Someone was pushing this fix pretty aggressively earlier and it made my game all Benny Hill. There are a dozen things I could think of doing before messing with some snake oil tweaks.
 
It's definitely not snake oil as it completely smoothed out my experience when no other tweak could. Could someone spoiler tag what quest wouldn't progress? I will test that if I haven't already completed it. So far at level 12 I haven't ran into any game breaking bugs forcing a reloaded save yet.

EDIT: I am using it in conjunction with iPresentInterval=0 / Exclusive Fullscreen / NVCP VSync if that makes a difference in the game having severe bugs or not.
 
I heavily advise against applying pretty much all of these random ini tweaks people are suggesting. iNumHWThreads is okay and that's pretty much it, but even that may not actually provide any tangible benefit.

The FPSClamp one will break your game. DO NOT USE IT.

I'm with you on that, even iNumHWThreads is useless to me. The only tweak I've made is upping the uGrids to 7. No changes to cell buffer as it's not necessary.

Those Reddit 'tweaks' either have no evidence they actually work or even worse, have been proven not to work by devs, but people don't seem to care even when you mention that. They'd rather listen to some random on Reddit tell them to put Oblivion 'tweaks' in their config files and just hope that it works, which is why people are now having issues with iFPSClamp screwing their games up.


Here's a thread on iFpsClamp's eventual effects on New Vegas: http://forums.nexusmods.com/index.php?/topic/1581420-effects-of-the-ifpsclamp-setting-on-new-vegas/
 
Finally got to dive into this yesterday and have settled with the following.

Core i7-5930K @ 4.2GHz
16GB 2666MHz RAM
GeForce Titan X

2560x1440 Ultra settings except for God Rays set at 'High", RivaTuner set at 60fps cap on a G-SYNC monitor.

So far so good, but I haven't hit a major landmark yet. The only issue I've been having is that I have a 21:9 monitor, and I have to edit the ini just to get full screen 1440p working correctly.

Hopefully a fully working mod to get the game running in 21:9 will come out soon, because so far the setting is so vibrant compared to the predecessors.
 
So, is there a way to save a playthrough that used iFPSClamp for the majority of it?

Exiting the area's not making the vault work. Do I need to find a save all the way before entering the area?
 
So, is there a way to save a playthrough that used iFPSClamp for the majority of it?

Exiting the area's not making the vault work. Do I need to find a save all the way before entering the area?

Loading a save from the area's entrance (not the vault's) before going down the stairs and triggering the first enemies did it for me. You're experience could vary however; I've seen a few reports of this bug, and some couldn't get it to work at all, no matter how far they went back. They never mentioned if they used iFPSClamp or not, but I'm assuming they did.
 
Those Reddit 'tweaks' either have no evidence they actually work or even worse, have been proven not to work by devs, but people don't seem to care even when you mention that.
The only one that I believe was confirmed to do bupkis is the one about pre-loading the video files. But the NumHWThreads did help me immensely in terms of stutter if not overall performance. My framerates stayed the same, near as I can tell, but it did smooth out quite a bit. Coupled with iPresentInterval=0 and G-Sync, and I'm in business. The game's running as well as can be expected for a 680, spends most of its time in the mid to high 40s, with occasional jumps north of 60 out in the open, only dipped down into the thirties in Lexington and the Corvega plant. The G-sync smooths that out quite a bit, it's not nearly as choppy as it was when I first booted it up.
 
Yeah, mine happened in the quest at Vault 114 also. The first time I attempted to open the vault, my character performed the full animation, but the plastic cover on the button never flapped up, so he was essentially not hitting the button, and thus not triggering anything.

I'm just a bit confused as to why the Fallout games all have this stuttering issue when Skyrim doesn't, seeing as they run on the same engine.

Skyrim also had a stutter problem, hence the stutter remover that is used for all of their games.
 
Top Bottom