UnknownBastion

The log you sent is not the correct one. 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.

If they are random game crashes, you can try renaming mods to _mods and try again.

Couple of things: 1. Open the CommandLine.txt in the Main Directory and remove the contents. Then add "-windowed" without the quotes and save and exit the document. 2. If you are still crashing, rename mods to _mods and try again.

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.

Just to confirm, you can launch the game normally just fine yeah?

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.

If you have a mods folder, rename it to _mods and try again.

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. Your topic has been moved to GTA V Support, this is not LSPDFR related. Please post in the correct location in the future.

You can find the 2010 Redist packages here. You will only want the vcredist_x86 and vcredist_x64.

Should be no reason to do a full re-install of the game when verifying exists. But for now, they don't need to do that. @Gavin10 Launch normal GTA V. See what happens.

You have the infamous SlimDX error. From the RPH Discord, here is what you can do to remedy the problem. 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.

No worries! Glad to help! Have a good one!

I believe your issue relates to Ultimate Backup. I believe you might be a version behind. Try updating from here. Make sure to use an adblocker on his site as there are a lot of weird ads.

The log you provided is not the correct one. 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.

This topic has been moved to the appropriate forum. Please post in the correct location in the future.

It may look the same but it is not the most recent one. As for what you said, you may simply have to do that. Sometimes RPH tends to do that hooking issue on a per user basis. You will simply just have to do that method from now on.

No worries!

That log you sent is not the correct one. 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. More so I am currently getting information given to me so that is why it may seem vague.

That question was answered here.

Yeah I understand what you are saying. I asked around and the response I got was that RPH is having issues hooking in general due to some form of permissions. Those would need to be fixed and RPH re-installed to test and see if the issue persists.

You can change it back to mods and then remove those weapons one by one and test after each removal to find the problem.

No worries!

I had to double check around because I was not entirely sure but I believe it could be a permissions issue. This is mainly due to it having the same error with all the plugins it tries to load. If you have added the Main Directory to the exceptions list already, re-install the plugins that threw errors in the log and see if the problem persists. I am still looking into this more.