For anyone that's interested, I've just uploaded FPM v1.45:
Fixed a bug related to the "GPU Temperature" and "GPU Load" no longer working. Apparently the latest NVIDIA driver introduced a video card name change, resulting in the Open Hardware Library doubling up on the manufacture name. Example: "NVIDIA NVIDIA GeForce RTX 3080". (OldMansBeard)
A few miscellaneous tweaks and fixes.
Important Notes:
FPM requires Admin rights in order to access CPU metrics like Temperature.
Windows 10: Files downloaded on the Internet can get "blocked" by Windows 10. Some users have reported success with FPM by "unblocking files" using Windows Explorer. Right-click on the file > Properties > check the "unblock" checkbox. (dheir)
Please let me know what you think, endorse if you find it useful. Also please feel free to post a success story of how you found FPM to be helpful, and images of your systems performance.
I just learned that in settlements there is a limit of objects that can be built, so that means, i cannot build huge skyscrapers all over the Sanctuary. There is a way to increase this limit but, that would be at risk of dropping framerates or even crashing to desktop every time i enter my settlement. My settlement might become unusable.
I am very happy that i found this tool as it will help me understand better capabilities of my gpu/cpu to know how big of a settlement i can build and how much i can increase my object/settlement size without crashing or running around super laggy.
Question for the mod author. Would you considering adding a timescale option to the X axis of the graphs? I ask because I'd consider it a useful feature to have to measure average readings. Another useful feature, would be to show Temperature (In C or F) on the Y axis for CPU and GPU Temperature.
Also, How do I find average CPU temp from Core Temps? I'm trying to find the average CPU temp when playing Fallout 4. Do I take the average of all Core temps, add them together, and divide by the number of cores to find the CPU temp?
P.S: "show Temperature (In C or F) on the Y axis for CPU and GPU Temperature.", What I mean, is to show the Y-axis range in temperature units on the CPU and GPU Temperature Graphs, because I have spikes of CPU/GPU temp on the graph on occasion, but the rest of the time, it is quite flat. I need to know how large the spikes are relative to the baseline.
Hello, wanted to test your app but that say I use a custom d3d11. And not showing any counter. The problem is I renamed all my d3d11 dll in fallout 4 folder, normally I use the system one now. Do you compare version number for d3d11? I tested with the experimental option for d3d11 and no success. Thank.
Sorry this might be a dumb question, but is it normal for the cpu to only reach maximum 10-15% usage while the gpu/vram maxing all out? I'm tryna figure out why I'm lagging and this could be a potential suspect.
For my own personal experience with F4, it is very GPU dependent. Because of this, it is normal for the CPU to be low and the GPU/VRAM to be running high. However, high GPU/VRAM can also be impacted by a high screen resolution and also hi-res mods. My best recommendation is to first try to lower your game settings or use "vanilla graphics" to reduce lag. Unfortunately the other alternative is to upgrade to more powerful hardware (like a graphics card). For myself, I play F4 in 4K, maxed settings, and with several hi-res texture mods installed. Because of this I have an RTX 3090.
Thanks for the response! Yeah it's just last year I played the game with more mods than the current one, but somehow I experienced much more smoother gameplay. With the current one, in city area, almost every minute or two the game just stutter to load god knows what. I'M JUST SO STRESSED OUT like I know my rig is capable, I might reinstall the game to figure something out. Well tbf most of my games after updating from windows 10 to 11 suffered from fps lost.
Lastly, do you perhaps know a way to safely reinstall my fallout 4 without reinstalling all the mods all over again? Anyway, thanks for the great mod, much needed!
Lastly, do you perhaps know a way to safely reinstall my fallout 4 without reinstalling all the mods all over again? Anyway, thanks for the great mod, much needed!
Unfortunately I'm not sure if there's a way to do this. My guess is that your existing saves may be tied to the mods you have installed, so removing those mods might affect your saves (thereby by affecting your game-play and game stability).
Do you use a Mod Manager? I'd recommend it - especially if, like myself, you have a curious mind and you regularly fall into the "Fallout 4 optimization" hole, haha.
If you use MO2 (which I'd recommend), you can mess with your installed mods as much as you like because the game directory is virtualized (doesn't overwrite the actual game directory, just imposes it over the top when the game is launched) - just bearing in mind that if you do, your save game is done (it's over, it's never coming back) and you'll have to start a new game. This saves a lot of time and f--king around when you're testing out different configurations.
If you're manually installing, god knows what the issue is and good luck to you - if that is the case and you've been copying things in and out over any lengthy period of time, you are much better off just writing a list of the mods you currently have installed, backing up your INI files somewhere other than the game directory and then just destroying the whole thing and reinstalling it. I know that is the exact opposite of what you were asking is possible (not reinstalling everything) but if you want to have a game that isn't totally cooked, just get a Mod Organizer and start again.
Tips below
Spoiler:
Show
You can use this guide to inform your load order: https://docs.google.com/document/d/1aknl_ze1hHUCiTBgz55dSzBBsfvG7iGXlRNIGWObyME/edit#
It's written specifically for Xbox users and it appears to be a bit outdated, but it is a good general guide to ensure your load order isn't causing you issues.
Here's a shorter version: https://www.nexusmods.com/fallout4/articles/3993/
I'll just write some other stuff below that might help - maybe you are already aware of all of it but I'll write it out regardless in case you're not or for the sake of other users. Consider the advice given as though it is being given to someone who doesn't know much about modding FO4.
Fallout 4 specific things to check: 1) F4SE installation is current and none of your mods have overwritten F4SE's scripts with outdated ones (you can find information on this online and you can check each mod, usually an F4SE utility or a mod that utilizes F4SE specifically, for this issue when you download them - prior to installation).
2) Download FO4Edit and see what sort of conflicts you have - probably if you've run heaps of mods in the past and had no issue and now you're having issues, you'll have a few. If you've removed and installed new mods on the same save, your game has become unstable and it won't ever be fixed - you'll need to start over again if you want the game to start behaving "normally" (lol) again.
Graphics settings in-game: 1) Check your fallout4 and fallout4custom ini files for grass settings - i_Max_Grass_Types_Per_Texure=3 i_Min_Grass_Size=20
Without underscores, of course - it is written like that so that Nexus doesn't autoblock the code. Those figures are the default but if you've changed these figures and then installed other grass mods etc, your performance is possibly maxing right out without you being aware of it. Most grass mods have their own ini files that will add in their own versions of these figures - fallout4.ini and fallout4prefs.ini are overwritten by fallout4custom and then anything in fallout4custom is overwritten by a mod-specific ini file (loaded at the time the mod loads) so you'll want to check this also.
2) Shadow resolution - reduce both this and the draw distance, particularly if you're using any mods that add 5 million additional trees to the game as well as grass mods, etc - basically any significant increase in stuff in the world that there is a lot of
3) Godrays - I still can't figure out how to make these behave properly even with a 3070 and a 5600x and the Ultra Godrays fix on Nexus, so I just turn them off.
4) ENB settings - if you use an ENB, you can mess around with the Depth of Field, Skylighting, AO, Cloud Shadows settings to see what sort of difference in performance this will give you. Depth of Field in particular eats around 10-20 fps in the game if I have a heap of other texture / foliage / lighting mods.
5) As mentioned below, check your graphics driver settings and then check these against the game's settings and any ENB settings - if you've updated the OS and it's turned on its driver-based AO and AA and then both are also enabled in-game and then you also have it enabled in ENB settings, your GPU is going to be f**ked no matter what you do (haha). Some other tips if you've upgraded Windows from 10 to 11: 1) Check the BIOS again to see if your RAM is overclocked to its advertised limit - I used my last PC for like 5 years without doing this because I didn't know it was a thing you should do (lol) - RAM doesn't automatically set itself to the MHz that it's advertised at (ie: 3600 or whatever other figure) and will utilize the minimum amount unless you toggle this in your BIOS. Fallout 4 has a weird dependence on RAM so this may make a difference for you.
2) There's a Powershell script called Windows10debloater - I don't know if there's a Windows 11 equivalent but I'd recommend you have a look around as the Windows 10 equivalent is scripted to uninstall the 3 million, useless bloatware apps that Microsoft pre-installs on your computer when you re-install / install a new OS. Make a restore point prior to doing this in case you delete a bunch of things you didn't want to delete.
3) If you have an NVIDIA GPU, check your Control Panel settings again - I am not sure what the AMD equivalent is but just check that again if you use an AMD card as everything is likely to have been reset. As well as this (and again if you're using an NVIDIA card) ensure you go to the NVIDIA website and download the latest graphics driver manually (not through GeForce Experience for this purpose) - when you execute the update, it'll give you an option to do a clean install. This will remove all previous versions of anything graphics-driver related (as well as GeForce Experience and Control Panel etc. so be mindful that your settings will be reset) and install all the new ones fresh. Windows 10, at least, has an issue where-in it ships outdated graphics drivers via the automatic update process and installing the new ones straight over the top of these drivers tends to make the GPU behave in a strange manner in some instances.
4) If either your GPU or CPU can be OC'd, download the relevant manufacturer's software (Intel or AMD for CPU and then whoever manufactures the NVIDIA card ie: ASUS, Gigabyte etc) for OC - if you don't know how to manually OC (like myself) don't touch literally anything except for the automatic OC settings - you'll find guides for this online.
5) If you're not really sure what's going on with either your CPU or GPU, generally, use Cinebench to stress-test your CPU and use Heaven benchmark (or a similar program, whatever the preference is - Heaven is just one of the few that is free and works fine for casual use) to stress-test your GPU. Generally speaking, if both pass the stress-test with no issues but you're still experiencing issues with Fallout 4 itself, it'll be something you've done to the game or it'll be (just as likely, if not more) something that Microsoft has done to your PC during the OS install. The game runs atrociously by default on modern anything, of course, but if you've previously ran it fine with more mods and now it's stuffed, it'll probably be either of the latter two that you should investigate.
JayzTwoCents and other Youtube channels about PC building etc. are really good resources for general optimization outside of Fallout itself - if you're on a fresh install of any version of Windows your PC is pretty much automatically not-at-all-optimized despite the absolute BS that Microsoft will try and tell you so you agree to let them mine and sell your data. Spend some time looking in to this and a) give Microsoft the finger and b) drastically improve your PC's performance as a result.
Trying to optimize Fallout itself is an endless and nightmarish saga at the best of times so if it's doing your head in just breathe, go do something else for a while (I should take that advice looool) and come back to it with a clear head.
Hope some of that's helpful for you or someone else :)
Hello. It worked great until it didn't. It will not display in game. It seems to install ok. I tried to re=install to solve the problem but that didn't work.
Finally noticed the reference to the installation articles, followed them and it's working fine. What threw me off was that it did work initially then wouldn't..
A very helpful app. I have had issues with the game running hot and random crashes. This will help me see if temperatures are playing a role. Thanks for your work.
Thanks for your response! I wish I knew about this app when I first started gaming on Skyrim a year ago. Nice to know what is going on with my hardware when doing a lot of mods! Awesome!
How to activate in-game monitoring? In FPM I can see all the metrics, but in fallout 4 they do not appear I use F4SE and Vortex I already followed the steps to make it compatible.
====================================== ENVIRONMENT INFO START ====================================== FPM Version: v1.45 Windows Version: Microsoft Windows 10 Pro 64-bit, v6.2.9200.0 Windows Culture: en-US Is Administrator: True Microsoft .NET Runtime Version: v4.0.30319 Microsoft .NET Latest Installed Version: v4.8.04084 CPU Name: Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz - x6 Total System Memory: 16,326 MB ======================================= ENVIRONMENT INFO END ======================================= ========================================= FOUND DLLS START ========================================= Please Note: Some of these are included in Fallout 4, others are likely from mods. Searching folder: "D:/Archivos de programa (x86)/Fallout 4"... D:/Archivos de programa (x86)/Fallout 4/bink2w64.dll D:/Archivos de programa (x86)/Fallout 4/cudart64_75.dll D:/Archivos de programa (x86)/Fallout 4/d3d11.dll D:/Archivos de programa (x86)/Fallout 4/d3dcompiler_46e.dll D:/Archivos de programa (x86)/Fallout 4/dxgi.dll D:/Archivos de programa (x86)/Fallout 4/f4se_1_10_163.dll D:/Archivos de programa (x86)/Fallout 4/f4se_steam_loader.dll D:/Archivos de programa (x86)/Fallout 4/flexExtRelease_x64.dll D:/Archivos de programa (x86)/Fallout 4/flexRelease_x64.dll D:/Archivos de programa (x86)/Fallout 4/flowchartx32.dll D:/Archivos de programa (x86)/Fallout 4/flowchartx64.dll D:/Archivos de programa (x86)/Fallout 4/GFSDK_GodraysLib.x64.dll D:/Archivos de programa (x86)/Fallout 4/GFSDK_SSAO_D3D11.win64.dll D:/Archivos de programa (x86)/Fallout 4/msvcp110.dll D:/Archivos de programa (x86)/Fallout 4/msvcr110.dll D:/Archivos de programa (x86)/Fallout 4/nvToolsExt64_1.dll D:/Archivos de programa (x86)/Fallout 4/ssce5564.dll D:/Archivos de programa (x86)/Fallout 4/steam_api64.dll D:/Archivos de programa (x86)/Fallout 4/x3daudio1_7.dll D:/Archivos de programa (x86)/Fallout 4/Data/F4SE/Plugins/crafting_highlight_fix.dll D:/Archivos de programa (x86)/Fallout 4/Data/F4SE/Plugins/FallSouls.dll D:/Archivos de programa (x86)/Fallout 4/Data/F4SE/Plugins/HighFPSPhysicsFix.dll D:/Archivos de programa (x86)/Fallout 4/Data/F4SE/Plugins/mcm.dll D:/Archivos de programa (x86)/Fallout 4/Data/F4SE/Plugins/place.dll D:/Archivos de programa (x86)/Fallout 4/Papyrus Compiler/Antlr3.Runtime.dll D:/Archivos de programa (x86)/Fallout 4/Papyrus Compiler/Antlr3.StringTemplate.dll D:/Archivos de programa (x86)/Fallout 4/Papyrus Compiler/PCompiler.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Archive2/Archive2Interop.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Archive2/Microsoft.WindowsAPICodePack.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Archive2/Microsoft.WindowsAPICodePack.Shell.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/BSCore.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/BSGraphics.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/BSMain.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/BSResource.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/BSShader.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/BSSystem.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/DotNetMagic2005.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/ElricInterop.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/ElricUtilities.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/libcurl.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/NiAnimation.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/NiCollision.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/NiMain.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/NiOptimization.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/NiParticle.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/NiStripify.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/NiSystem.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/ToolLib.dll D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/xg.dll D:/Archivos de programa (x86)/Fallout 4/Tools/LipGen/GFSDK_GodraysLib.Win32.dll D:/Archivos de programa (x86)/Fallout 4/Tools/LipGen/ssce5532.dll ========================================== FOUND DLLS END ========================================== ================================= MISCELLANEOUS INI SETTINGS START ================================= Common Settings in INI: D:/Documents/My Games/Fallout4/Fallout4.ini iPreloadSizeLimit: uGridsToLoad: 5 uExterior Cell Buffer: 36 uInterior Cell Buffer: bFloatPointRenderTarget: bForceUpdateDiffuseOnly: iTextureUpgradeDistance1: iTextureUpgradeDistance0: iTextureDegradeDistance1: iTextureDegradeDistance0: ================================== MISCELLANEOUS INI SETTINGS END ================================== ==================================== RELATED GAME TITLES START ===================================== Looking for installed Titles containing "Fallout" Found Game Title: "Fallout 4 MULTi8 - ElAmigos versión 1.10.163", Path: D:/Archivos De Programa (X86)/Fallout 4/ Found Game Title: "Fallout Performance Monitor", Path: D:/Documents/Sir Garnon On Nexus/Fallout Performance Monitor/ ===================================== RELATED GAME TITLES END ====================================== ========================================= DEBUG INFO START ========================================= User Config Filepath: C:/Users/Chesini/AppData/Local/FalloutPerformanceMonitor/FalloutPerformanceMonitor_Url_sj3u0qfynb1tyrqzxyigrhglnfrnryc2/1.0.0.0/user.config LocalUtilities:FoundAllRequiredFiles()(): Application Run directory (assemblyFilePath): "D:/Documents/Sir Garnon on Nexus/Fallout Performance Monitor/" --------- MainWindow.xaml:InitializeAndBeginMonitoring(): Begin Initialization Process... ---------- MainWindow.xaml:InitializeAndBeginMonitoring(): Using Monitor Mode: WaitForFallout4. Bypassing Starting the Launcher Process: D:/Archivos de programa (x86)/Fallout 4/Fallout4Launcher.exe. InGameHotKeys:InitializeHotkeys(): Initializing Hotkeys. InGameHotKeys:InitializeHotkeys(): In-Game Hotkeys Disabled: False MainWindow.xaml:BeginMonitoringMain(): Entering Monitoring Process for Main Program: D:/Archivos de programa (x86)/Fallout 4/Fallout4.exe. MainWindow.xaml:BeginMonitoringMain(): Begin Initializing Windows PerformanceCounters. MainWindow.xaml:BeginMonitoringMain(): End Initializing Windows PerformanceCounters. MainWindow.xaml:BeginMonitoringMain(): Begin Initializing Main Counters. MainWindow.xaml:BeginMonitoringMain(): End Initializing Main Counters. Debug: MemoryCounterControl.xaml:BeginMonitoringMemory() - Memory (MB): Entering Monitoring for: Fallout4.exe. Debug: CPUCounterControl.xaml:BeginMonitoringCPU() - CPU %: Entering Monitoring for: Fallout4.exe. Debug: VRAMCounterControl.xaml:BeginMonitoringVRAM() - VRAM (MB): Entering Monitoring for: Fallout4.exe. MainWindow.xaml:SetStartTime(): Setting Start Time to: 7:20:20 PM. Called from: "BeginMonitoringMain()". Debug: CPUTemperatureCounterControl.xaml:BeginMonitoringCPUTemperature() - CPU °: Entering Monitoring for: Fallout4.exe. Debug: GPUCounterControl.xaml:BeginMonitoringGPU() - GPU %: Entering Monitoring for: Fallout4.exe. Debug: GPUTemperatureCounterControl.xaml:BeginMonitoringGPUTemperature() - GPU °: Entering Monitoring for: Fallout4.exe. Debug: ThreadsCounterControl.xaml:BeginMonitoringThreads() - Threads: Entering Monitoring for: Fallout4.exe. Debug: DiskCounterControl.xaml:BeginMonitoringDisk() - Disk IO: Entering Monitoring for: Fallout4.exe. ========================================== DEBUG INFO END ==========================================
Thanks for taking the time to post the debug info.
Looking at this line from the debug info: MainWindow.xaml:InitializeAndBeginMonitoring(): Using Monitor Mode: WaitForFallout4. Bypassing Starting the Launcher Process: D:/Archivos de programa (x86)/Fallout 4/Fallout4Launcher.exe. it looks like FPM is still waiting for Fallout 4 to be running. Since Fallout 4 is not running yet, the monitoring cannot correctly happen. Please run the FPM again, but be sure to then also start Fallout 4.
Thanks for taking the time to post the screenshot.
This may be a limitation in the Open Hardware Library which FPM is using. Since the 5900x is a newer CPU, it might not be supported unfortunately. I'm personally in the same situation -- just upgraded to a 11900KF, and no CPU temps for me either.
Unfortunately, there's not much I can do at the moment. I will need to wait for the next release of the OHL -- hopefully soon.
Give Feedback
441 comments
Latest News:
For anyone that's interested, I've just uploaded FPM v1.45:
- Fixed a bug related to the "GPU Temperature" and "GPU Load" no longer working. Apparently the latest NVIDIA driver introduced a video card name change, resulting in the Open Hardware Library doubling up on the manufacture name. Example: "NVIDIA NVIDIA GeForce RTX 3080". (OldMansBeard)
- A few miscellaneous tweaks and fixes.
Important Notes:Please let me know what you think, endorse if you find it useful. Also please feel free to post a success story of how you found FPM to be helpful, and images of your systems performance.
I am very happy that i found this tool as it will help me understand better capabilities of my gpu/cpu to know how big of a settlement i can build and how much i can increase my object/settlement size without crashing or running around super laggy.
Thank you!
Also, please feel free add some screenshots of your FPM to show how it helped your troubleshooting.
Best Regards!
Also, How do I find average CPU temp from Core Temps? I'm trying to find the average CPU temp when playing Fallout 4. Do I take the average of all Core temps, add them together, and divide by the number of cores to find the CPU temp?
I have an i7 1195G7 @ 2.90 GhZ.
These are good ideas. Can you clarify what you're looking for on this please:
I will need to determine if they're possible to do, and will add them to the new features list. However, no ETA as this point.
Best Regards!
P.S: "show Temperature (In C or F) on the Y axis for CPU and GPU Temperature.", What I mean, is to show the Y-axis range in temperature units on the CPU and GPU Temperature Graphs, because I have spikes of CPU/GPU temp on the graph on occasion, but the rest of the time, it is quite flat. I need to know how large the spikes are relative to the baseline.
I can take a close look if you post the troubleshooting information per these instructions.
Posting the FPM Debug Info
Best Regards!
For my own personal experience with F4, it is very GPU dependent. Because of this, it is normal for the CPU to be low and the GPU/VRAM to be running high. However, high GPU/VRAM can also be impacted by a high screen resolution and also hi-res mods. My best recommendation is to first try to lower your game settings or use "vanilla graphics" to reduce lag. Unfortunately the other alternative is to upgrade to more powerful hardware (like a graphics card). For myself, I play F4 in 4K, maxed settings, and with several hi-res texture mods installed. Because of this I have an RTX 3090.
Best Regards!
Lastly, do you perhaps know a way to safely reinstall my fallout 4 without reinstalling all the mods all over again? Anyway, thanks for the great mod, much needed!
If you use MO2 (which I'd recommend), you can mess with your installed mods as much as you like because the game directory is virtualized (doesn't overwrite the actual game directory, just imposes it over the top when the game is launched) - just bearing in mind that if you do, your save game is done (it's over, it's never coming back) and you'll have to start a new game. This saves a lot of time and f--king around when you're testing out different configurations.
If you're manually installing, god knows what the issue is and good luck to you - if that is the case and you've been copying things in and out over any lengthy period of time, you are much better off just writing a list of the mods you currently have installed, backing up your INI files somewhere other than the game directory and then just destroying the whole thing and reinstalling it. I know that is the exact opposite of what you were asking is possible (not reinstalling everything) but if you want to have a game that isn't totally cooked, just get a Mod Organizer and start again.
Tips below
You can use this guide to inform your load order:
https://docs.google.com/document/d/1aknl_ze1hHUCiTBgz55dSzBBsfvG7iGXlRNIGWObyME/edit#
It's written specifically for Xbox users and it appears to be a bit outdated, but it is a good general guide to ensure your load order isn't causing you issues.
Here's a shorter version:
https://www.nexusmods.com/fallout4/articles/3993/
I'll just write some other stuff below that might help - maybe you are already aware of all of it but I'll write it out regardless in case you're not or for the sake of other users. Consider the advice given as though it is being given to someone who doesn't know much about modding FO4.
Fallout 4 specific things to check:
1) F4SE installation is current and none of your mods have overwritten F4SE's scripts with outdated ones (you can find information on this online and you can check each mod, usually an F4SE utility or a mod that utilizes F4SE specifically, for this issue when you download them - prior to installation).
2) Download FO4Edit and see what sort of conflicts you have - probably if you've run heaps of mods in the past and had no issue and now you're having issues, you'll have a few. If you've removed and installed new mods on the same save, your game has become unstable and it won't ever be fixed - you'll need to start over again if you want the game to start behaving "normally" (lol) again.
Graphics settings in-game:
1) Check your fallout4 and fallout4custom ini files for grass settings -
i_Max_Grass_Types_Per_Texure=3
i_Min_Grass_Size=20
Without underscores, of course - it is written like that so that Nexus doesn't autoblock the code.
Those figures are the default but if you've changed these figures and then installed other grass mods etc, your performance is possibly maxing right out without you being aware of it. Most grass mods have their own ini files that will add in their own versions of these figures - fallout4.ini and fallout4prefs.ini are overwritten by fallout4custom and then anything in fallout4custom is overwritten by a mod-specific ini file (loaded at the time the mod loads) so you'll want to check this also.
2) Shadow resolution - reduce both this and the draw distance, particularly if you're using any mods that add 5 million additional trees to the game as well as grass mods, etc - basically any significant increase in stuff in the world that there is a lot of
3) Godrays - I still can't figure out how to make these behave properly even with a 3070 and a 5600x and the Ultra Godrays fix on Nexus, so I just turn them off.
4) ENB settings - if you use an ENB, you can mess around with the Depth of Field, Skylighting, AO, Cloud Shadows settings to see what sort of difference in performance this will give you. Depth of Field in particular eats around 10-20 fps in the game if I have a heap of other texture / foliage / lighting mods.
5) As mentioned below, check your graphics driver settings and then check these against the game's settings and any ENB settings - if you've updated the OS and it's turned on its driver-based AO and AA and then both are also enabled in-game and then you also have it enabled in ENB settings, your GPU is going to be f**ked no matter what you do (haha).
Some other tips if you've upgraded Windows from 10 to 11:
1) Check the BIOS again to see if your RAM is overclocked to its advertised limit - I used my last PC for like 5 years without doing this because I didn't know it was a thing you should do (lol) - RAM doesn't automatically set itself to the MHz that it's advertised at (ie: 3600 or whatever other figure) and will utilize the minimum amount unless you toggle this in your BIOS. Fallout 4 has a weird dependence on RAM so this may make a difference for you.
2) There's a Powershell script called Windows10debloater - I don't know if there's a Windows 11 equivalent but I'd recommend you have a look around as the Windows 10 equivalent is scripted to uninstall the 3 million, useless bloatware apps that Microsoft pre-installs on your computer when you re-install / install a new OS. Make a restore point prior to doing this in case you delete a bunch of things you didn't want to delete.
3) If you have an NVIDIA GPU, check your Control Panel settings again - I am not sure what the AMD equivalent is but just check that again if you use an AMD card as everything is likely to have been reset. As well as this (and again if you're using an NVIDIA card) ensure you go to the NVIDIA website and download the latest graphics driver manually (not through GeForce Experience for this purpose) - when you execute the update, it'll give you an option to do a clean install. This will remove all previous versions of anything graphics-driver related (as well as GeForce Experience and Control Panel etc. so be mindful that your settings will be reset) and install all the new ones fresh. Windows 10, at least, has an issue where-in it ships outdated graphics drivers via the automatic update process and installing the new ones straight over the top of these drivers tends to make the GPU behave in a strange manner in some instances.
4) If either your GPU or CPU can be OC'd, download the relevant manufacturer's software (Intel or AMD for CPU and then whoever manufactures the NVIDIA card ie: ASUS, Gigabyte etc) for OC - if you don't know how to manually OC (like myself) don't touch literally anything except for the automatic OC settings - you'll find guides for this online.
5) If you're not really sure what's going on with either your CPU or GPU, generally, use Cinebench to stress-test your CPU and use Heaven benchmark (or a similar program, whatever the preference is - Heaven is just one of the few that is free and works fine for casual use) to stress-test your GPU. Generally speaking, if both pass the stress-test with no issues but you're still experiencing issues with Fallout 4 itself, it'll be something you've done to the game or it'll be (just as likely, if not more) something that Microsoft has done to your PC during the OS install. The game runs atrociously by default on modern anything, of course, but if you've previously ran it fine with more mods and now it's stuffed, it'll probably be either of the latter two that you should investigate.
JayzTwoCents and other Youtube channels about PC building etc. are really good resources for general optimization outside of Fallout itself - if you're on a fresh install of any version of Windows your PC is pretty much automatically not-at-all-optimized despite the absolute BS that Microsoft will try and tell you so you agree to let them mine and sell your data. Spend some time looking in to this and a) give Microsoft the finger and b) drastically improve your PC's performance as a result.
Trying to optimize Fallout itself is an endless and nightmarish saga at the best of times so if it's doing your head in just breathe, go do something else for a while (I should take that advice looool) and come back to it with a clear head.
Hope some of that's helpful for you or someone else :)
Please post the debug info per these steps:
Posting the FPM Debug Info
Best Regards!
Finally noticed the reference to the installation articles, followed them and it's working fine. What threw me off was that it did work initially then wouldn't..
A very helpful app. I have had issues with the game running hot and random crashes. This will help me see if temperatures are playing a role. Thanks for your work.
Please post per these instructions, and I will take a look:
https://www.nexusmods.com/fallout4/articles/2
Best Regards!
I didn't change anything in the meantime and it's one of only three mods.
Anything special I need to look for?
Edit. Never mind. Dumbass me forgot to start the monitoring.
Please post the debug details per these steps, it will really help with the troubleshooting:
Posting the FPM Debug Info
Best Regards!
====================================== ENVIRONMENT INFO START ======================================
FPM Version: v1.45
Windows Version: Microsoft Windows 10 Pro 64-bit, v6.2.9200.0
Windows Culture: en-US
Is Administrator: True
Microsoft .NET Runtime Version: v4.0.30319
Microsoft .NET Latest Installed Version: v4.8.04084
CPU Name: Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz - x6
Total System Memory: 16,326 MB
======================================= ENVIRONMENT INFO END =======================================
========================================= FOUND DLLS START =========================================
Please Note: Some of these are included in Fallout 4, others are likely from mods.
Searching folder: "D:/Archivos de programa (x86)/Fallout 4"...
D:/Archivos de programa (x86)/Fallout 4/bink2w64.dll
D:/Archivos de programa (x86)/Fallout 4/cudart64_75.dll
D:/Archivos de programa (x86)/Fallout 4/d3d11.dll
D:/Archivos de programa (x86)/Fallout 4/d3dcompiler_46e.dll
D:/Archivos de programa (x86)/Fallout 4/dxgi.dll
D:/Archivos de programa (x86)/Fallout 4/f4se_1_10_163.dll
D:/Archivos de programa (x86)/Fallout 4/f4se_steam_loader.dll
D:/Archivos de programa (x86)/Fallout 4/flexExtRelease_x64.dll
D:/Archivos de programa (x86)/Fallout 4/flexRelease_x64.dll
D:/Archivos de programa (x86)/Fallout 4/flowchartx32.dll
D:/Archivos de programa (x86)/Fallout 4/flowchartx64.dll
D:/Archivos de programa (x86)/Fallout 4/GFSDK_GodraysLib.x64.dll
D:/Archivos de programa (x86)/Fallout 4/GFSDK_SSAO_D3D11.win64.dll
D:/Archivos de programa (x86)/Fallout 4/msvcp110.dll
D:/Archivos de programa (x86)/Fallout 4/msvcr110.dll
D:/Archivos de programa (x86)/Fallout 4/nvToolsExt64_1.dll
D:/Archivos de programa (x86)/Fallout 4/ssce5564.dll
D:/Archivos de programa (x86)/Fallout 4/steam_api64.dll
D:/Archivos de programa (x86)/Fallout 4/x3daudio1_7.dll
D:/Archivos de programa (x86)/Fallout 4/Data/F4SE/Plugins/crafting_highlight_fix.dll
D:/Archivos de programa (x86)/Fallout 4/Data/F4SE/Plugins/FallSouls.dll
D:/Archivos de programa (x86)/Fallout 4/Data/F4SE/Plugins/HighFPSPhysicsFix.dll
D:/Archivos de programa (x86)/Fallout 4/Data/F4SE/Plugins/mcm.dll
D:/Archivos de programa (x86)/Fallout 4/Data/F4SE/Plugins/place.dll
D:/Archivos de programa (x86)/Fallout 4/Papyrus Compiler/Antlr3.Runtime.dll
D:/Archivos de programa (x86)/Fallout 4/Papyrus Compiler/Antlr3.StringTemplate.dll
D:/Archivos de programa (x86)/Fallout 4/Papyrus Compiler/PCompiler.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Archive2/Archive2Interop.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Archive2/Microsoft.WindowsAPICodePack.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Archive2/Microsoft.WindowsAPICodePack.Shell.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/BSCore.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/BSGraphics.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/BSMain.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/BSResource.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/BSShader.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/BSSystem.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/DotNetMagic2005.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/ElricInterop.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/ElricUtilities.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/libcurl.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/NiAnimation.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/NiCollision.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/NiMain.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/NiOptimization.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/NiParticle.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/NiStripify.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/NiSystem.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/ToolLib.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/Elric/xg.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/LipGen/GFSDK_GodraysLib.Win32.dll
D:/Archivos de programa (x86)/Fallout 4/Tools/LipGen/ssce5532.dll
========================================== FOUND DLLS END ==========================================
================================= MISCELLANEOUS INI SETTINGS START =================================
Common Settings in INI: D:/Documents/My Games/Fallout4/Fallout4.ini
iPreloadSizeLimit:
uGridsToLoad: 5
uExterior Cell Buffer: 36
uInterior Cell Buffer:
bFloatPointRenderTarget:
bForceUpdateDiffuseOnly:
iTextureUpgradeDistance1:
iTextureUpgradeDistance0:
iTextureDegradeDistance1:
iTextureDegradeDistance0:
================================== MISCELLANEOUS INI SETTINGS END ==================================
==================================== RELATED GAME TITLES START =====================================
Looking for installed Titles containing "Fallout"
Found Game Title: "Fallout 4 MULTi8 - ElAmigos versión 1.10.163", Path: D:/Archivos De Programa (X86)/Fallout 4/
Found Game Title: "Fallout Performance Monitor", Path: D:/Documents/Sir Garnon On Nexus/Fallout Performance Monitor/
===================================== RELATED GAME TITLES END ======================================
========================================= DEBUG INFO START =========================================
User Config Filepath: C:/Users/Chesini/AppData/Local/FalloutPerformanceMonitor/FalloutPerformanceMonitor_Url_sj3u0qfynb1tyrqzxyigrhglnfrnryc2/1.0.0.0/user.config
LocalUtilities:FoundAllRequiredFiles()(): Application Run directory (assemblyFilePath): "D:/Documents/Sir Garnon on Nexus/Fallout Performance Monitor/"
--------- MainWindow.xaml:InitializeAndBeginMonitoring(): Begin Initialization Process... ----------
MainWindow.xaml:InitializeAndBeginMonitoring(): Using Monitor Mode: WaitForFallout4. Bypassing Starting the Launcher Process: D:/Archivos de programa (x86)/Fallout 4/Fallout4Launcher.exe.
InGameHotKeys:InitializeHotkeys(): Initializing Hotkeys.
InGameHotKeys:InitializeHotkeys(): In-Game Hotkeys Disabled: False
MainWindow.xaml:BeginMonitoringMain(): Entering Monitoring Process for Main Program: D:/Archivos de programa (x86)/Fallout 4/Fallout4.exe.
MainWindow.xaml:BeginMonitoringMain(): Begin Initializing Windows PerformanceCounters.
MainWindow.xaml:BeginMonitoringMain(): End Initializing Windows PerformanceCounters.
MainWindow.xaml:BeginMonitoringMain(): Begin Initializing Main Counters.
MainWindow.xaml:BeginMonitoringMain(): End Initializing Main Counters.
Debug: MemoryCounterControl.xaml:BeginMonitoringMemory() - Memory (MB): Entering Monitoring for: Fallout4.exe.
Debug: CPUCounterControl.xaml:BeginMonitoringCPU() - CPU %: Entering Monitoring for: Fallout4.exe.
Debug: VRAMCounterControl.xaml:BeginMonitoringVRAM() - VRAM (MB): Entering Monitoring for: Fallout4.exe.
MainWindow.xaml:SetStartTime(): Setting Start Time to: 7:20:20 PM. Called from: "BeginMonitoringMain()".
Debug: CPUTemperatureCounterControl.xaml:BeginMonitoringCPUTemperature() - CPU °: Entering Monitoring for: Fallout4.exe.
Debug: GPUCounterControl.xaml:BeginMonitoringGPU() - GPU %: Entering Monitoring for: Fallout4.exe.
Debug: GPUTemperatureCounterControl.xaml:BeginMonitoringGPUTemperature() - GPU °: Entering Monitoring for: Fallout4.exe.
Debug: ThreadsCounterControl.xaml:BeginMonitoringThreads() - Threads: Entering Monitoring for: Fallout4.exe.
Debug: DiskCounterControl.xaml:BeginMonitoringDisk() - Disk IO: Entering Monitoring for: Fallout4.exe.
========================================== DEBUG INFO END ==========================================
Looking at this line from the debug info:
MainWindow.xaml:InitializeAndBeginMonitoring(): Using Monitor Mode: WaitForFallout4. Bypassing Starting the Launcher Process: D:/Archivos de programa (x86)/Fallout 4/Fallout4Launcher.exe.it looks like FPM is still waiting for Fallout 4 to be running. Since Fallout 4 is not running yet, the monitoring cannot correctly happen. Please run the FPM again, but be sure to then also start Fallout 4.
Best Regards!
Cheers
The CPU temps may require running FPW with Admin (Open Hardware Library needs this). Please try that and let me know if the problem gets resolved.
Best Regards!
Cheers
This may be a limitation in the Open Hardware Library which FPM is using. Since the 5900x is a newer CPU, it might not be supported unfortunately. I'm personally in the same situation -- just upgraded to a 11900KF, and no CPU temps for me either.
Unfortunately, there's not much I can do at the moment. I will need to wait for the next release of the OHL -- hopefully soon.
Best Regards!