UnknownBastion

Locking this topic as it is not permitted to share files. For anyone else's information, the original file can be found in update/update.rpf/common/data. You then copy and paste that file from the above path into mods/update/update.rpf/common/data for a fresh copy in your mods folder. If you are missing files with the newest update, verify your game files to recover any missing files from the base game directory GTA V Steam Steam Library > Right click GTA V > Properties > Installed Files > Verify integrity of game files GTA V Retail Rockstar Games Launcher > Click GTA V > Click Settings > Verify GTA V Epic Games Go to your Epic Games Library > GTA V > click the three little dots > Manage > Verify

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.

This is a false positive and is due to Microsoft being dumb and flagging it. For a workaround, please see below: Your topic has been moved to GTA V Support, this is not LSPDFR related. Please post in the correct location in the future.

Add your GTA V Main Directory to the exceptions list for your anti-virus. Then restart your PC and try launching normal GTA V into story mode.

Have the game crash again and then send the ELS.log.

I kinda figured. No matter, add back the SHV.dll file and rename the lml folder to _lml and ModManager to _ModManager and try again.

Yeah...there is a lot going on with your log. So let's dive in: 1. Update: Basic Callouts 2. Callout Manager, Dangerous Callouts, and FBI Callouts are all known to cause issues. It is suggested to remove them, though not required. However, in terms of Callout Manager, there are more stable options out there like Callout Interface. 3. Go into the lspdfr.ini and change the following to reflect below: Main.DisableGameBlipHiding = true 4. One of the following XMLS had errors: DefaultRegions, CustomRegions, or SpecialUnits. Please revert any recent changes made to these or re-install the base files from Ultimate Backup. If they persists after making the changes, remove Menyoo.asi if you have it installed. 5. There are multiple errors relating to custom files. Rename mods to _mods and try again.

Right now that we are past that one part, we can get back to the ELS issue. I want you to rename the _ELS back to ELS. Then have it crash and then send the ELS.log.

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

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

Please do not create multiple topics regarding the same issue. I have trashed your other topic and you may continue here. Please send your RPH Crash Log. It's a txt file in the Main Directory either called RagePluginHook or RagePluginHook.log. It is NOT in your Logs folder.

Here is an excerpt from Cyan's post a few days ago that will help:

That I am not sure of. I know there are people that use it, but I can't say for certain how good it is.

Send a new log.

You should not be doing this nor is ForceDuty "unstable". @zspencerz While the issue does lie with Grammar Police, try renaming your mods folder to _mods and then running LSPDFR/using Grammar Police again. If it crashes, send a new log.

Remove ScriptHookV.dll and try again.

The following is a fix from the RPH Discord for this known issue:

No. If you really don't want to test each one individually, you can always clean your Directory by having it match like the image below and then verify your game files. Verifying Game Files: Clean Directory Examples:

Keep the ELS folder rename to _ELS. The issue you are having now is a known issue with RagePluginHook. The following workaround comes from the RPH Discord:

Glad to help!

The following VCFs are faulty and should be removed: 11cvpiint.xml 11cvpik9int.xml 11cvpilib.xml 13chgrk9.xml 18chgr.xml 18chgrk9.xml 20fpiuk9.xml 21durk9.xml 22silv.xml 22silvk9.xml 22tahk9.xml mpd21tahoe.xml opd1.xml

After the latest update, did you update your mods folder?

You might be able to find something here. Personally, I recommend keyboard and mouse as it allows for more flexibility with the amount of keybinds you will need.

Most likely the other scripts are older and as such do not work with SHV Nightly. So you will have to choose which ones you want. Like I said before, scripts are very picky about when they want to work.

It does not. You will have to recall that on your own. If you cannot remember, you will have to delete STP/UB if you have those plugins and re-install as well as do a fresh install of manual LSPDFR.