Talk:Fallout 4

About this board

Tmplt (talkcontribs)

A recent change changed all usage of Fallout4.ini to Fallout4Custom.ini. Is this config file an addition in this game that overwrites parameters set in Fallout4.ini?

Is the usage of the file documented somewhere?

Megabobster (talkcontribs)

I changed this, it's not documented as far as I know (I found it by simply looking at it and trying it out), it works perfectly in all my testing, and it's how we should tell noobs/the non-tech savvy to do it so they don't mess up their default settings. Fallout4Custom.ini is easier and more intuitive, at least to me. It's like Bethesda was like "hey, this is the .ini where all your custom lines go, and we will use all the settings you put in here to overwrite everything else everywhere else." If someone gets frustrated with tweaks and mods there should always be the option of "delete the lines you added" and not "try to remember what the original values here were." Or something like that. I'm new to Bethesda games, and I'm pretty new to the whole Wiki thing, so someone feel free to tell me if I'm doing it all wrong [insert thumbs up here]. Now let's see if I can figure out how to sign this comment.

(oh I think I also forgot to add I standardized the formatting and wording between the sections that I changed to Fallout4Custom.ini as well)

Tmplt (talkcontribs)

If Fallout4Custom.ini works, then by all it should be used instead of the default ini file, for the reasons you've listed already. I wonder if this feature was a recent addition, or whether it may work in other games based on the same engine.

Megabobster (talkcontribs)

Some googling and an anecdote from a friend says that Skyrim had it but support was much more inconsistent and wonky. Fallout 4 is probably the first title that they've got it fully figured out.

Reply to "Fallout4Custom.ini"
500806 (talkcontribs)

Sorry, I'm relatively new to editing PCGW.

I previously posted a "fix" for the stuttering in this game, where modifying the iFPSClamp value in the config files will completely eliminate the stuttering.

I have now found that it can break the scripting in certain places and have removed this suggestion - but I want to warn against anyone else doing so. Where would it be appropriate to do this?

Additionally, the new suggestion to run the game in Borderless Windowed Mode does nothing to improve the stuttering on my system. Example video here.

Would it be appropriate to add a note to that effect, or should it be left up to the users' discretion? (it might work on some systems?)

RaTcHeT302 (talkcontribs)

Try iFPSClamp at one less than your rendered fps. On my machine this prevents the physics from getting screwed up in New Vegas for me. You could also try other values around the fps such as 58 or 61.


I'd rather just not add it all. And I remember the main menu stuttering without the borderless thingy, it fixes itself after a bit however. The game still stutters anyway, one of the main causes might be due to the game spawning way too many enemies when you can't even see them.

Sorry, sleepy.

Reply to "Adding a warning?"
Marioysikax (talkcontribs)

Once again, we have come to the same issue. Bethesda thinks that Vsync is a FPS cap, that doesn't mean everyone else should handle it like one. It can be used like a cap, but as it depents on screens refresh rate so it shouldn't be considered as universal capping method because of that users end variable.

So, while I'm writing this, key point is "Capped at 60 FPS with the Vsync mode." and scrolling down to 120+ FPS, first of all FPS capping link is removed, again, and for some reason state is set to true with text of "Uncapped, affected by some major physics issues at higher framerates." and still 60 FPS states clearly that 60 FPS cap is required if vsync is disabled.

I'm not going to edit this article that much because I do not own the game, will not own the game for long time, but if physics issues are considered as 120+ FPS true, then you mean something like this and something like this are considered working games at over 120 FPS values? It's true that techically game does allow higher frame rates, but vsync disabling option being deliberately obscured withing config files and stuff getting broken when frame rate exceeds 60 FPS, I personally wouldn't consider high frame rates to be true, at all. I would consider it Bethesda being ignorant about current PC hardware and them just assuming everyone has 60Hz monitor and not playtesting over 60 FPS values.

I already fixed Skyrim article, because I may not want to know can the game get to 144 FPS after getting the game, I want to know what the hell to do when horses starts flying everywhere in my screen preventing me from playing the game at all when I get to that 144 FPS value so simply noting "Yeah, 144 FPS works, just some physic issues" is not helpful at that point.

RaTcHeT302 (talkcontribs)

I don't know, I did a quick cleanup, I never finished editing everything, it's all pretty tiring, from what I've read the game should be fine at around 100 - 120 FPS, even with these issues. I like to play the game at 70 FPS, because capping the FPS to 60 in Fallout 4 sucks, I don't know if I should say "cap it at 70 optimally, or something".

I was just trying to keep things simple, I really wish you guys would stop taking everything so literally, and it's not my fault if the developers are fucking idiots.

RaTcHeT302 (talkcontribs)

I'm sorry but this is kinda frustrating, the idea was is that it's playable at a certain point, so I guess it should be set to false anyway. Whenever I have to edit these strange articles lot's of things go through my mind, so I need some time to think first. I really wish you'd keep your posts a bit shorter, seeing as I often miss the point of what I'm supposed to be doing, and it just confuses me, so I never know what I should do or add.

RaTcHeT302 (talkcontribs)

Now I set the 120 Hz field to hackable, but 60 and 120 only themselves should be fine apparently? But that doesn't seem like the case, I won't know without seeing it myself.

Meh... what a clusterfuck. If I had a DVI cable I could test the 120 Hz field, but I can't find that anywhere, I hate this crap already.

RaTcHeT302 (talkcontribs)

Okay I'm just going to say that anything past 60 is bad until someone on the wiki can properly test these things.

Reply to "Vsync is not a hard cap."
Mirh (talkcontribs)
Garrett (talkcontribs)

Bethesda's PC support topic covers the official stance on this--among other things, they only officially support 60 Hz and 120 Hz refresh rates. Adaptive Vsync methods are not mentioned but might be an issue as well.

Mirh (talkcontribs)

We are not here to stick with official stancesĀ :p

Anyway, not technically realted to stutter, but just stupid performance there's this and this

RaTcHeT302 (talkcontribs)

At the time I didn't understand what this really ment, I didn't think they'd do such a thing, editing that page got so frustrating at one point, seeing as the whole thing wasn't very clear to me.

I didn't realize the game had literally no cap, and they just used VSync as some hacky workaround, jesus.

Reply to "Frame rate awfulness round up"
Primey (talkcontribs)

I don't have the time to fix it but if you look at the reference it has a completely different way of removing the acceleration. Also whoever is writing these fixes need to learn Fallout4_default should not be touched.

Reply to "Mouse acceleration section is wrong."
There are no older topics