0 of 0
Mod articles
-
Steps to post the Debug Information in FPM for troubleshooting purposes, please use the following steps.
Open FPM, and click on the "Launch Fallout 4" button to start Fallout.
If you're able to get Fallout 4 running from FPM, continue with step #3, otherwise go to step #4:
Once Fallout 4 launches, let it run for about one minute, and then exit the game. You should now be back in FPM.
In the FPM Menu, click Tools, then "System Information". This will display the System Information Window.
On the System Information Window, select the information type (typically DEBUG INFO) and click the "Copy to Notepad" button.
Copy the contents from Notepad to the "New Paste" textbox on Pastebin: http://pastebin.com
Click the "Create New Paste" button on... -
To get FPM to work with MO or F4SE, set Monitoring Mode to "Option 2". This will tell FPM to wait until it detects Fallout 4 running, and then being monitoring.
Steps:
Start FPM.
In the Tools menu, click "Setup Window...".
Click on the "Miscellaneous Settings" Tab.
Set the "Monitoring Mode" to "Option 2".
Click the "Save" button.
Back on the main FPM Window, click the "Monitor Fallout 4" button.
FPM will now begin waiting for Fallout 4 to be launched, and the Status Field should now read "Waiting for Fallout4.exe".
Launch Fallout 4 using Mod Organizer, F4SE, Steam, etc.
FPM should detect Fallout4.exe running, and begin monitoring.
... -
Fixing Windows Performance Counters
Some users have resolved FPM related performance counter issues by running this Microsoft Windows command as Administrator: "Lodctr /R" (the R is uppercase).
This will rebuild the Windows Performance Counters if they are corrupted somehow. See http://support.microsoft.com/kb/300956 for more details.
Steps to run the command "Lodctr /R":
========================================
You'll need a DOS prompt with elevated privileges (even above the normal Admin):
1) Start Menu/All Programs/Accessories, right click on "Command Prompt" and ** YOU MUST ** select "Run as administrator".
2) At the command prompt, type in "Lodctr /R" and hit Enter. (Please note that the R is uppercase)
-
.NET FRAMEWORK:
Please make sure that your Microsoft .NET Framework is updated. Some users have reported getting a runtime error message something like "Error: Unknown error code (-1073741502): The user defined managed entry point failed in the target process...". If you get this error, please try reinstalling the latest Microsoft .NET Framework to resolve this:
Microsoft .NET Framework v4.5 (Vista, Windows 7, Windows 8, Windows 10)
IN-GAME COUNTERS:
The in-game counters display currently has a compatibility issue with certain mods which employ dll hooking with a custom D3D11.dll file:
ENB Series
If you happen to use a mod like the ones mentioned here, the in-game counters in the monitor might not work....