The Fallout Performance Monitor is a utility used for tracking Fallout 4's Memory, VRAM, Disk I/O, CPU, GPU, GPU Temperature, and Threads system resource usage, plus FPS as they relate to the game engine, your system hardware, and installed mods. Please see the change log for details.
Permissions and credits
Credits and distribution permission
Other user's assetsAll the assets in this file belong to the author, or are from free-to-use modder's resources
Upload permissionYou are not allowed to upload this file to other sites under any circumstances
Modification permissionYou are not allowed to modify my files, including creating bug fixes or improving on features under any circumstances
Conversion permissionYou are not allowed to convert this file to work on other games under any circumstances
Asset use permissionYou are not allowed to use assets from this file under any circumstances
Asset use permission in mods/files that are being soldYou are not allowed to use assets from this file in any mods/files that are being sold, for money, on Steam Workshop or other platforms
Asset use permission in mods/files that earn donation pointsYou are not allowed to earn Donation Points for your mods if they use my assets
Console modding permissionThis mod will not be available on Bethesda.net for console users
Author notes
This author has not provided any additional notes regarding file permissions
File credits
This is solely my own creation, and initially was built for my own use.
However, this was heavily inspired by the Microsoft Dynamic Data Display Samples library: http://dynamicdatadisplay.codeplex.com/
Other resources =============== Pete Browns screen capture example: http://10rem.net/blog/2011/02/08/capturing-screen-images-in-wpf-using-gdi-win32-and-a-little-wpf-interop-help
Inspiration from Najam ul Hassan's chart example: http://www.codeproject.com/KB/cs/MonitoringProcess.aspx?msg=3135149
NVIDIA VRAM is from the Open Hardware Monitor Project: http://openhardwaremonitor.org/
The ATI Memory Load is from greywaters excellent source code example, which includes portions of code from: - "Managed DXGI" by WSairus: http://mdxgi.codeplex.com/ - "Process Hacker": http://processhacker.sourceforge.net/doc/d3dkmt_8h_source.html
The color selector feature is inspired by Seethapathi Purru's Color Picker ComoBox example at: http://wpf-4-0.blogspot.com/2013/01/color-picker-comobox-in-wpf-c_18.html
The key monitor process is inspired by Ciantic’s code example at: https://gist.github.com/Ciantic/471698
Donation Points system
Please log in to find out whether this mod is receiving Donation Points
Changelogs
Version 1.45
• Fixed a bug related to the "GPU Temperature" and "GPU Load" no longer working. Apparently the latest NVDIA 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.
Version 1.44
• Updated to the latest version of the Open Hardware Library, to hopefully resolve issues with newer hardware detection. (ag22)
• Miscellaneous internal code optimizations.
Version 1.43
• Mainly (hopefully) implemented several stability updates, related to error messages that have been posted on Nexus.
• Miscellaneous internal code optimizations.
Version 1.42
• Fixed a bug where the settings for the "Time" in-game counter were not being saved. (dark_wizzie)
• A few miscellaneous tweaks and fixes.
Version 1.41
• Fixed an issue with Total VRAM having an incorrect value for some cards.
• Added a "Percentage" display for the System RAM usage, and also GPU VRAM Usage.
• A few miscellaneous tweaks and fixes.
Version 1.4
• Re-implemented the InstallShield Lite installer, which is vastly superior to the Microsoft Installer that comes with Visual Studio. (diskdevl)
• Added a new option in the Setup Window for handling Survival Mode Exit Saves. When this option is enabled, FPM will attempt to rename the current "Exitsave.." file to "Autosave..". This is helpful if F4 crashes before you get a chance to "sleep" in Survival Mode, or before you get a chance to get a new Exit Save.
See http://fallout.wikia.com/wiki/Survival_mode for more details on Exit Save.
• Several miscellaneous tweaks and fixes.
I updated the installer details to be specific for the original, 32-bit version of Skyrim.
Version 1.3
• Upgraded to the latest version of Easyhook, which now supports SharpDX v4.0.1.
- In my own testing, so far, FPM seems to be able to support ENB.
- For this, ENB will load first, and the PFM overlay will load after a short delay.
• Upgraded to the latest version of the Open Hardware Monitor Library, which includes improved support for newer CPUs.
• Hopefully fixed the bug reported by user WolverineSix428. I was not able to reproduce this error myself, so I can't accurately report if it is resolved or not.
• Hopefully fixed the bug reported by user tfalcone31.
• Several miscellaneous tweaks and fixes.
Fallout Performance Monitor - By Sir Garnon
Description: The Fallout Performance Monitor is a utility used for tracking Fallout 4’s system resource usage as they relate to the game engine, your system hardware, and installed mods.
FPM Currently monitors the following resources:
Memory
VRAM
Disk I/O
CPU
CPU Temperature
GPU
GPU Temperature
Threads
FPS
Main Features:
Graphs and In-Game Display for Memory, VRAM, Disk I/O, CPU, CPU Temperature, GPU, GPU Temperature, and Threads resource usage, and also for FPS.
Ability to save and replay past performance runs for use in comparing different configurations.
Ability to Pause monitoring while Fallout 4 is running.
Ability to capture Screenshots, useful for posting.
In-Game Counter Configuration: Support for dynamically customizing the Graphs and In-Game Counter Colors, Font Size, and Display Order:
In-Game Font and Font size can be changed:
Keyboard mappings reference for the in-game counter hotkeys:
Run the Windows Uninstaller program in the Control Panel.
Directions:
Make sure Steam is already started and logged into.
Click the "Launch Fallout 4" button.
Fallout 4 should launch, and FPM should then being monitoring.
Important Notes: While I've thoroughly tested this and use it myself, it may contain bugs. If you encounter any problems though, please let me know by posting the issue in the FPM Nexus Site Comments section, and I'll get it fixed asap.
The Memory, CPU, Disk I/O, and Threads values are retrieved from the Windows Performance Counters, and are not always a perfect match for what is displayed in Task Manager.
