Fallout Performance Monitor

[]

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 Temperature

  [] 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:

    Requirements:

    • [] Windows 7 and above, 64-bit

      [] Microsoft . NET Framework v4. 5

      Installation:

      • [] To install, simply unzip the download to your Windows Desktop, and run the "FalloutPerformanceMonitor.exe" application.

        [] Windows 10 users may need to manually "unblock" the files in order for FPM to work correctly.

        [] You may also need to install the latest Microsoft . NET Framework (required):

        [] Microsoft . NET Framework v4. 5

        • []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 a