Bad Fps even after the midnight ride

[Dr. Sex]

I've had issues with the fps for a while now, and no matter what i do, its still super choppy. as the title reads, even after following the midnight ride, the fps is still awful. the whole point of the midnight ride is better fps, yet it doesn't fix the bad fps for me. i even have a computer with 32 gigs of ram and it still has bad fps. I've even tried disabling Vsync and that did nothing. What do i do? do i just give up, or is there something that will fix it?

[Zekiran]

Just because you're using an extremely large popular set of mods doesn't mean they actually work, dude.

If you're having issues you should look at first, owning the game properly if you're here on steam asking for help. Second, just because your rig has a massive amount of ram doesn't make the game magically know how to use any of your hardware.

You don't say what fps you are GETTING, what do you expect from a 10 year old game on 15 year old engine? The game's math is entirely tied to the fps - so you MUST limit the fps to 60. disabling vsych might not do what you think it does, with this engine.

Adding a massive mod to the mix, does not help this, it hinders troubleshooting. Also jesus the arrogance of their site owner's writing style makes me want to block their site from my memory.

"don't use anything but our thing that might be broken but it's your fault not ours" is what I get from even glancing over their website. I personally would fix the fact that you don't own the game first.

[matt]

You need a reasonably good CPU and GPU if you want to avoid stutter. The Previsibines Repair Pack (PRP) will probably help a lot, but it's not some magical cure for having a potato PC.

I think that guide is pointlessly opinionated in some areas, but that's not entirely unexpected. The community is full of that. If you follow it, go all the way and follow all the instructions.

[hawkeye]

If you want best performance there is no substitute for knowing how the game engine works and how your pc works. 32 gig of ram has nothing to do with fps.

Plus if you are using the collection on nexus there are 2 pointers on the home page that it probably won't work. 1-calling the collection a mod and 2-the 42% installation success rate.

[Ceredh]

If you have low fps, usually your system cannot process the data fast enough. If that is for vanilla Fallout 4, there seem to be some very bad system settings or components not playing together well. What resolution do you use, what's your processing chip?

I ran Fallout 4 for years on a better i7 and a 970 with a modest ENB and had 45 to 60 fps ususally, even in Boston. I ran it on an i9-11900 and a RTX 2070 with HD textures and a more demanding ENB for mostly 45 to 55 fps, 60 fps in interiors. Both with a 1920 x 1080 screen. I'm currently on an i9-14900 with a 4080 Super with True Grass, Another Pine Forest and all 4k to 8k textures (if available) on static structures, clothes, armor, robots etc., on a 3840 x 2160 screen, and never drop below 60 fps anywhere, without any optimising (I use Buffout 4 of course) or using PRP mod.

We need more info related to your problem.

[The Inept European]

OP have you asked these questions on the Midnight Ride collection page on Nexus?

[Dr. Sex]

oh yeah i forgot to mention, i had like 37 fps, more than that in some areas depending on camera angle, and even less in some areas as well.

[major tom]

google "draw call" and "draw call bottleneck" to understand the basics why openworld games suffer from fps drops.

try also to understand the fallout 4 previs/precombine optimization to reduce the amount of "draw calls" in an open world scenario.

dx11 and especially fo4 is not greatly optimised to work with multithreaded graphics tasks thrown at a multi-core cpu. you need a cpu with high single core ipc to be able to feed the gpu with "draw call" tasks in time.
but fo4 contains a "draw call" optimization that is good for performance as long as the game is "vanilla".

if you change the game with the wrong mods, if you scrap outside settlements or you change some ini-settings you can easily and unintentionally destroy this performance optimisation.

the used creation engine by bethesda is still gambryo engine bound. that means that the "draw call" handling in the fo4 openworld operates at its limits even with capable hardware.

https://thegamedev.guru/unity-cpu-performance/draw-call-bound/

https://github.com/PistonDevelopers/graphics/issues/1026