20FPS?

[GrAnd944]

I paid however much for a 4080. This game came out ten years ago, and I should know, I went to the ♥♥♥♥♥♥♥♥ midnight launch. Can somebody please explain to me why I'm getting worse FPS now than I was in 2014. I mean ♥♥♥♥ me sideways.

Someone must have fixed this by now - I know mods are an option but considering not only have I never bothered modding before but also that most of the mods have now been broken, how do I fix it without.

Any help appreciated.

[🦊Λℚ𝓤ΛƑΛᗯҜᔕ🦊]

Originally posted by Alio:

In most DX12 games it doesn't matter between the two and they are within a margin of error difference both in performance due to FSO and input latency due to API changes in pre-rendered frame behaviour + Nvidia Reflex.

Just so everyone is aware, they just did it again (proving they know nothing): DirectX-12 games do not support Exlusive Full Screen Mode. It's literally impossible with DX12. There is no "different between the two". All DX12 games all run borderless windowed mode only.

Also this:

Originally posted by Alio:

For example, he tried calling me out on Vsync without even understanding VRR 101 or where Vsync input lag comes from and how to get rid of it.

Almost everyone that has used a computer or played a game within windows within the past 24 years has always known that vsync will always incur some sort of input lag or delay in input. It can not possibly be removed. It's inherent to the very design of Vsync and how it functions. No one should ever be using VSYNC for any reason in any game or program or app. Recommending someone to turn on vsync is single-handedly the worst suggestion anyone could ever possibly make for anything.

[Alio]

Originally posted by 🦊Λℚ𝓤ΛƑΛᗯҜᔕ🦊:

Originally posted by Alio:

In most DX12 games it doesn't matter between the two and they are within a margin of error difference both in performance due to FSO and input latency due to API changes in pre-rendered frame behaviour + Nvidia Reflex.

Just so everyone is aware, they just did it again (proving they know nothing): DirectX-12 games do not support Exlusive Full Screen Mode. It's literally impossible with DX12. There is no "different between the two". All DX12 games all run borderless windowed mode only.

Also this:

Originally posted by Alio:

For example, he tried calling me out on Vsync without even understanding VRR 101 or where Vsync input lag comes from and how to get rid of it.

Almost everyone that has used a computer or played a game within windows within the past 24 years has always known that vsync will always incur some sort of input lag or delay in input. It can not possibly be removed. It's inherent to the very design of Vsync and how it functions. No one should ever be using VSYNC for any reason in any game or program or app. Recommending someone to turn on vsync is single-handedly the worst suggestion anyone could ever possibly make for anything.

Vsync input lag comes from pre-rendered frames being used. You can literally use ULLM to debunk this myth immediately.

There is inherent input lag, but none that makes any meaningful difference and 99% of users wouldn't ever be able to tell. As long as a CPU can hold a locked framerate under the refreshrate, it will not use pre-rendered frames. If you are experiencing input lag from Vsync it's because you can't hold a locked framerate or aren't using one to prevent pre-rendered frames from being used. Vsync input lag becomes apparent/troublesome when pre-rendered frames cause overshoot past the refreshrate.

[🦊Λℚ𝓤ΛƑΛᗯҜᔕ🦊]

Originally posted by Alio:

There is inherent input lag

You just openly admitted just what I said: You are attempting to suggest and/or recommend that people intentionally introduce input lag into their gaming experience by trying to tell people to turn on vsync. At least you admitted your motives in public.

And now that we know that everything you say, suggest, or recommend to anyone in the steam forums can not be taken seriously. You openly admitted to telling everyone to degrade or worsen their gaming experience on purpose.

[flayman]

This comment on another thread gives very good details on all the setup for getting the game running as well as you can. It was written before the update but still applies, as the update seems to have messed some of the sensible defaults: https://steamcommunity.com/app/377160/discussions/0/4364626348100218422/#c4364626348100326950

[Alio]

Originally posted by 🦊Λℚ𝓤ΛƑΛᗯҜᔕ🦊:

Originally posted by Alio:

There is inherent input lag

You just openly admitted just what I said: You are attempting to suggest and/or recommend that people intentionally introduce input lag into their gaming experience by trying to tell people to turn on vsync. At least you admitted your motives in public.

And now that we know that everything you say, suggest, or recommend to anyone in the steam forums can not be taken seriously. You openly admitted to telling everyone to degrade or worsen their gaming experience on purpose.

You have to use Vsync to avoid screen tearing 100%, VRR doesn't completely remove screen tearing as I said before. If you get massive input lag from having it enabled, that's likely because your monitor has trash latency already, you aren't capping to a framerate your CPU can handle 99.9% of the time under your maximum refreshrate which causes pre-rendered frames to be used, and you aren't limiting pre-rendered frames in DX9-11 games using LLM or ULLM.

I only notice the input lag with Vsync on because I'm a top 500 FPS player and can notice those things, and the difference between it on vs off is about a 1% difference in input latency on my system/monitor when my CPU is holding a locked framerate. To the average user, this would literally be unnoticeable and I still have it turned ON while I'm playing competitive top 500. Any type of tearing in the image is going to affect me worse than the 1% of extra input latency. If you have your monitor at 144hz, and you can run a game at 144hz locked, those pre-rendered frames are going to introduce the input lag you claim to be a problem because it will force your framerate over 144fps (145/146fps), which is like a 20-30% difference in input latency. The fact that you don't know how to cap your framerate properly to avoid Vsync input lag is hilarious.

I could force my monitor to 60hz fixed without VRR, cap to 59.993 with Vsync on and still walk circles around you in every FPS game. It makes no difference and this has long been debunked by BlurBusters. You can literally check this on your own system.

Also, yes, my stuff runs in exclusive fullscreen because Full Screen Optimization is a completely optional setting that you have control over for DX9-11 games. Lmfao.

[kkitts]

Originally posted by kkitts:

Originally posted by Friendly Ghostface:

At the moment, nothing. Your best bet is to turn off weapon debris and Vsync in the Fallout prefs file. Bethesda somehow wrecked performance with this latest update.

Seconded. I went from 60 FPS smooth as glass before the patch (with unplayably fast lockpicking), to 34 FPS standing still with nothing else moving (but the lockpicking worked). In vanilla, no mods (ever). For a "next-gen" update, they completely botched the next-gen PC version. They deliberately slowed down the game to unplayable levels to make 2D stuff work, rather than putting in the work to de-couple 2D stuff from the frame rate.

And the patch of the Next Gen Patch didn't do anything to fix the problem.

[Neo]

Yeah if you are getting 20fps on a 4080 there is something very wrong on your system. Don't expect a fix from bethesda if it's your machine causing the issue. You will be waiting a very long time.

Try running Geforce experience and pressing the optimise button.

[sdack]

Originally posted by kkitts:

Originally posted by kkitts:

Seconded. I went from 60 FPS smooth as glass before the patch (with unplayably fast lockpicking), to 34 FPS standing still with nothing else moving (but the lockpicking worked). In vanilla, no mods (ever). For a "next-gen" update, they completely botched the next-gen PC version. They deliberately slowed down the game to unplayable levels to make 2D stuff work, rather than putting in the work to de-couple 2D stuff from the frame rate.

And the patch of the Next Gen Patch didn't do anything to fix the problem.

Actually they did. They changed iPresentInterval back to its old behaviour (sort of). It is useable again.

If you still cannot get your game to run at expected frame rates then the problem has to be on your end. One does not have to use mods and can completely disable VSync in the game just for a test. If it then still syncs then it is a tool, an extra layer, or the driver doing it.

https://steamcommunity.com/sharedfiles/filedetails/?id=3241230342

[Gub]

Originally posted by GrAnd944:

I paid however much for a 4080. This game came out ten years ago, and I should know, I went to the ♥♥♥♥♥♥♥♥ midnight launch. Can somebody please explain to me why I'm getting worse FPS now than I was in 2014. I mean ♥♥♥♥ me sideways.

Someone must have fixed this by now - I know mods are an option but considering not only have I never bothered modding before but also that most of the mods have now been broken, how do I fix it without.

Any help appreciated.

Same here and no help sadly. I was running 6600xt that before patch was getting rocksolid 60 fps ( with or without mods) everywhere in the game ( unless you detonate 100 mini nukes at once).

After patch barely 30fps in downtown.

Changed my card to a 4070, deleted the game and all game files from mods, I did the cleanest clean install ever. Same area same 30fps with a card twice as powerful as the previous one. This patch is a joke.

[sdack]

Originally posted by Gub:

Originally posted by GrAnd944:

I paid however much for a 4080. This game came out ten years ago, and I should know, I went to the ♥♥♥♥♥♥♥♥ midnight launch. Can somebody please explain to me why I'm getting worse FPS now than I was in 2014. I mean ♥♥♥♥ me sideways.

Someone must have fixed this by now - I know mods are an option but considering not only have I never bothered modding before but also that most of the mods have now been broken, how do I fix it without.

Any help appreciated.

Same here and no help sadly. I was running 6600xt that before patch was getting rocksolid 60 fps ( with or without mods) everywhere in the game ( unless you detonate 100 mini nukes at once).

After patch barely 30fps in downtown.

Changed my card to a 4070, deleted the game and all game files from mods, I did the cleanest clean install ever. Same area same 30fps with a card twice as powerful as the previous one. This patch is a joke.

My RTX 3060Ti is doing 60-70fps in the toughest spots downtown Boston.

Did you disable fullscreen and windowed optimisations in the Windows settings by any chance? I know some folks turned those optimisations off, thinking it lets them get around their vsync problems, and it does, but it also wrecks frame rates.

[Wille84FIN]

I'm getting a pretty much locked 138fps on a 4080 Super. I'm using High FPS Fix and most of the Baka mods, fast loading mods and other QOL mods. I'm playing on a VRR/Gsync screen with vsync enabled from Nvidia Control Panel only + Ultra low latency mode. I use beth.ini app ultra settings. Why 138fps? Because i use a 144Hz display with VRR/Gsync.

As to why you are getting low frames on a 4080, the post above might be worth a shot. The other is working around the games vsync (ipresentinterval) issues. Sadly that means using mods, or a display with refresh rate that divide nicely with 60fps (60/120/240Hz) and so on.

Would be great to be able to select a different display mode in-game, but that's just one issue among many others. I would prefer using 120Hz 10-bit mode myself with VRR/Gsync, but that seems like it's too much to ask.

[flayman]

Originally posted by Wille84FIN:

I'm getting a pretty much locked 138fps on a 4080 Super. I'm using High FPS Fix and most of the Baka mods, fast loading mods and other QOL mods. I'm playing on a VRR/Gsync screen with vsync enabled from Nvidia Control Panel only + Ultra low latency mode. I use beth.ini app ultra settings. Why 138fps? Because i use a 144Hz display with VRR/Gsync.

As to why you are getting low frames on a 4080, the post above might be worth a shot. The other is working around the games vsync (ipresentinterval) issues. Sadly that means using mods, or a display with refresh rate that divide nicely with 60fps (60/120/240Hz) and so on.

Would be great to be able to select a different display mode in-game, but that's just one issue among many others. I would prefer using 120Hz 10-bit mode myself with VRR/Gsync, but that seems like it's too much to ask.

Ah, the High FPS Physics Fix mod got updated a couple hours ago. Cool.

[kkitts]

Originally posted by sdack:

Originally posted by kkitts:

And the patch of the Next Gen Patch didn't do anything to fix the problem.

Actually they did. They changed iPresentInterval back to its old behaviour (sort of). It is useable again.

If you still cannot get your game to run at expected frame rates then the problem has to be on your end. One does not have to use mods and can completely disable VSync in the game just for a test. If it then still syncs then it is a tool, an extra layer, or the driver doing it.

https://steamcommunity.com/sharedfiles/filedetails/?id=3241230342

We've been through this before, maybe you've forgotten, or haven't been reading my posts.
The Next Gen Patch broke everything. I was getting 60 FPS before the patch, but lockpicking was too fast. After the patch, 60 FPS standing still with nothing moving around me (although lockpicking worked because the game was forced by Bethesda to run so slow). Same exact settings before and after. All drivers updated. Trying to force 60 FPS through video drivers resulted in CTDs within 3 minutes of starting to play, every time.

Bethesda broke it, they can fix it. If and when they ever get around to it.

[sdack]

Originally posted by kkitts:

We've been through this before, maybe you've forgotten, or haven't been reading my posts.
The Next Gen Patch broke everything. I was getting 60 FPS before the patch, but lockpicking was too fast. After the patch, 60 FPS standing still with nothing moving around me (although lockpicking worked because the game was forced by Bethesda to run so slow). Same exact settings before and after. All drivers updated. Trying to force 60 FPS through video drivers resulted in CTDs within 3 minutes of starting to play, every time.

Bethesda broke it, they can fix it. If and when they ever get around to it.

I know they broke it or rather made iPresentInterval obsolete with their first update, and forced it on for everyone to either full-, half- or third-refresh.

Hence I am saying to check again, because now they undid this with their second update!

Do check in all three .ini files under Documents\My Games\Fallout4\ for iPresentInterval and set it to 0. And if you have touched the .ini files in the game's folder then set it there to 0, too.

Then check in Windows Settings System->Display->Graphics->Fallout 4 if you have windowed optimisation turned off or on, and uncheck it, meaning, turn optimisations back on.

Then check Fallout4.exe in the Steam folder. Right-click and bring up Properties->Compatibility and if you have optimisations turned off there, too, then uncheck it and leave it turned on.

Then check your driver settings, but you will probably already have done this. And if you use any tools, like Rivatuner of MSI Afterburner or whatever, then also check that these do not turn vsync on.

[Crashed]

Originally posted by maestro:

Go to the Launcher and look at Graphics Settings.

If Borderless Window is enabled, disable it.
If Borderless Window is disabled, enable it.

Should get you an instant 60 FPS.

For some strange reason, some people are on one side of the camp, and other people are on the other side. It might depend on video drivers. Thankfully I'm in the "must run borderless" camp. I was getting 30 until I enabled it now it's 60.

If on Windows 11 and you have Optimizations for windowed games enabled, is there no difference between borderless and fullscreen because Windows overrides the DirectX present method?