UnknownBastion

This does not have anything to do with their error. If they still had the args.txt installed, they would be experiencing crashes on startup.

Rename mods to _mods and see if you crash at all.

You are having a new issue now. You need to increase the Plugin Timeout Threshold to 60,000 in the RagePluginHook Settings. How to Access the RagePluginHook Settings: As per the PyroCommon issue, maybe @SuperPyroManiac can weigh in on a potential solution.

Unfortunately no. It is near impossible to know exactly what is wrong when it's a mods folder issue. Im pretty sure if you have the 2025 one, it doesn't require LSPDFR+, as they removed that connection. Double check that you do.

You appear to be missing RageNativeUI. Please ensure that you install the .dll and .xml into the Main Directory.

The first crash appears to be related to a customized ped or vehicle. The "Object reference not set to an instance of an object." is usually mods folder related. The second crash is related to Traffic Policer looking for LSPDFR+ to be installed which you either don't have or have installed incorrectly. I recommend using either Traffic Policer 2025 or Aschtar's Traffic Policer. Traffic Police 2025 is the newest one. The last crash appears to be related to an issue with an xml file. Usually with these, you can just reload LSPDFR and keep playing. They sometimes happen.

Please send the RPH Crash Log. It is a txt file in the Main Directory either called RagePluginHook or RagePluginHook.log. It is NOT in the Logs folder.

You can try installing Resource Adjuster and see if that helps. Your topic has been moved to GTA V Support, this is not LSPDFR related. Please post in the correct location in the future.

Try adding your Main Directory to the exceptions list for your anti-virus. Then re-install the manual version of LSPDFR and restart your PC. See if that helps.

@rhykan76In the future, please create one thread per issue. I have merged your unanswered one with this one as they contain the same problem. As per your issue, keep mods to _mods. Remove ScriptHookV.dll and try again. For future reference, you have sent the wrong log. You will need to send the RPH Crash Log. It is a txt file in the Main Directory either called RagePluginHook or RagePluginHook.log. It is NOT in the Logs folder.

Rename mods to _mods and try again. For future reference, you have sent the wrong log. Please send the RPH Crash Log. It is a txt file in the Main Directory either called RagePluginHook or RagePluginHook.log. It is NOT in the Logs folder.

Rename mods to _mods and try again. Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

Try launching GTA V normally first. Then once fully in story mode, tab out and launch RPH.

To my knowledge, it is supported for Windows only. I know individuals have managed to get it to run on other OS's, but I don't believe it is publicly available for other OS's.

That is not the correct log. Please send the RPH Crash Log. It is a txt file in the Main Directory either called RagePluginHook or RagePluginHook.log. It is NOT in the Logs folder.

Try it one more time. Delete the GTAV.exe and then verify game files. Just for safe measure, re-install manual LSPDFR and test again.

This was an issue with StopThePed xml. You can simply reload and keep playing. These are bound to happen. Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

There was an issue with XScanner. Re-install it. Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

Please send the ELS.log. Your topic has been moved to GTA V Support, this is not LSPDFR related. Please post in the correct location in the future.

Please send the RPH Crash Log. It is a txt file in the Main Directory either called RagePluginHook or RagePluginHook.log. It is NOT in the Logs folder.

That is not the correct log. Please send the RPH Crash Log. It is a txt file in the Main Directory either called RagePluginHook or RagePluginHook.log. It is NOT in the Logs folder.

There was an issue with XScanner. You can attempt a re-install to see if the issue persists. Also make sure that you have the PyroCommon file in the Main Directory and NOT in Plugins/LSPDFR.

Well yeah, because they would not be loaded if they are removed from the dlclist.xml. The core of your issue lies with Menyoo though. If you wish to use those vehicles, you may have to look at using another trainer.

Can you screenshot the whole window of where you have the vehicles installed to.

Nothing has even loaded yet. Rename mods to _mods and try again. If you do not have a mods folder, screenshot the Main Directory as it currently is. This topic has been moved to the appropriate forum. Please post in the correct location in the future.