Mrsuperx13

You have RPH installed in the wrong place (as the error message says). It needs to be installed and run from the same folder as your GTA installation (not the Rockstar games folder in your documents). It should be installed in the same folder that you have the gta5.exe

That is not the latest log. We need the log from your main game folder not your `logs` folder. If there are any numbers after `RagePluginHook` then that is the wrong log.

no I don't need you to do that I think your save game might be corrupted. before we do that I just want to confirm though so Do you have a vfs.dll file in your main game directory? if you do Rename the vfs.dll file to _vfs.dll. Then try start your game again. If that doesn't work or you don't have a vfs.dll file Please upload your Asiloader.log and ELS.log (they can be found in your main GTA directory)

is there any chance you saved the game whilst RPH was loaded?

that is not where you are supposed to install ELS XMLs you need to install the XMLs in `Grand Theft Auto V\ELS\pack_default`

Try renaming your mods folder to _mods Then try start your game again.

Try launch regular GTA first, then once you've loaded in story mode and can move your character around tab-out and launch RagePH.

can you send a screenshot of where you installed the XML please

Do you have a vfs.dll file in your main game directory? if you do Rename the vfs.dll file to _vfs.dll. Then try start your game again. If that doesn't work or you don't have a vfs.dll file Please upload your Asiloader.log and ELS.log (they can be found in your main GTA directory)

Delete your gta5.exe then verify the game.

Remove the plugins in RED & YELLOW (they are outdated or cause issues) ------ In the future please check if the plugins you are downloading are up to date... Any plugin on this site has a section on the right for "minimum LSPDFR version" if it says anything lower than 0.4.7 do not download it. And for the coroner service one you downloaded it was last updated over 5 years ago...

Try renaming your mods folder to _mods Then try start your regular game again.

In the future I will try and ping you if I see specific crashes related to your plugin. It is possible that your plugin is in a lot better state then when I added it to my list a few months ago and I would be happy to remove it now and see if issues pop up again. I think you can understand I am trying to help users. It does not matter to me the plugin or the developer my main objective when I help people is to allow them to enjoy the game I have enjoyed for the past 10 years. If that meant at that time telling them to remove your plugin, then I said so with no guilt. As I said I would be happy to stop doing so temporarily to see if the state of your plugin has changed since I put it on my list - but I will not apologize for doing it in the first place as it was the right thing to do then as my first and foremost responsibility is to ensure the user I am helping will be able to play and enjoy their game with the minimalist of interruption.

While I understand you don't want to derail the thread - the horse has already left the barn and I would prefer any further discussion happens either in public or not at all. I am not in any way dismissing the concept of bug reporting. I am saying that you are failing to understand what it's actually like giving support. Most of my time is spent explaining to people how to do even the most basic of things like uploading a log or even how to take a screenshot. These things take time - a lot of time. so I have to be efficient. I am trying to help everyone and one of those ways is prophylactically, so when I see a user with a large amount of outdated and issue causing plugins - I feel absolutely no regret telling them to remove them.

k I am obviously not just telling people to remove a plugin the second it causes a crash. I always try to find solutions but for some plugins for one reason or another (whether bad coding practice or incompatibility with a large amount of other popular plugins) it is the correct thing to tell the user to remove it. I respond to dozens of people a day (mostly not on this site) most of which can barely understand how to upload their log. So I am not being hyperbolic in anyway when I say that I don't have the time or energy to direct and explain to people how to report issues for buggy plugins. I understand this is a personal issue for you - after all we are talking about your plugin. But resorting to name calling it uncalled for. I am simply stating as a matter of fact that your plugin causes issues. Enough issues that over the past few months I have come to the conclusion that it is currently better for people to remove it (I am not the only one in this community that feels this way however I can only speak for myself).

I'm afraid I am not your tech support nor do I have time to direct logs or people to error report. I help people solve their problems that is it. Often removing your plugin is a solution to their problem. this is not the case with so many other plugins - meaning crashes causes by your plugin are not just random.

I very clearly said meaning plugins either are outdated or cause issues. So your point about your plugin being up to date is irrelevant. In regards to issues from your plugin you may not want to hear this but it undoubtedly causes issues. I deal with dozens of people every day and section136 callouts again and again causes issues. I do not have any specific logs for because as I said I deal with a lot of people. -------------------------------------- Here you concede my point. Yes deadly weapons crashed but it was not the cause. ----------------------------------------- If you are trying to say that plugins made for extremally old versions of LSPDFR (any one of which could have caused this DeadlyWeapons crash) last updated years ago are not out of date... then I don't even feel like I need to justify that with a response that is outdated by definition. ------------------------------- Again based on SuperPyroManiacs explanation of how this functionality works your statement is wrong.

1. In regards to the general list of plugins at no point did I say they caused this specific issue. I said specifically... Besides the vast majority of plugins are on that list because they are outdated not related to any specific issues they might cause. 2. In regards to the specific cause of the crash technically deadly weapons crashed. But not because its broken or outdated. it was not the cause of the crash. I may be wrong about interaction+ causing the crash it may have been LSPDFR+ or something else but basically something removed an entity (could be a car, ped or something else (anything that exists in 3D space in the game)) and didn't properly update its status so when DeadlyWeapons tried to access that entity it was no longer there and that caused the crash. The issue is with whatever removed the entity not with DeadlyWeapons. But I may be wrong since I'm not a developer I cannot say I understand 100% what happened.

Remove the plugins in RED & YELLOW (they are outdated or cause issues) DO NOT REMOVE DEADLY WEAPONS Deadly weapons is neither outdated nor the cause of this crash. Just because an error message contains the name of a specific plugin doesn't mean the plugin was the cause. I believe Interaction+ may have been the specific cause of this crash.

The problem is you have scripts installed where they shouldn't be. Scripts and plugins are not the same and are not installed in the same place... go to Grand Theft Auto V\plugins\lspdfr and move the following BloodV, CrawlInjury, Stop Reversing While Braking, to Grand Theft Auto V\scripts in the future read the description and install instructions of things you download. Once you are done that reinstall grammar police.

1. if you are using Simple trainer make sure the everyone ignore player and police ignore player options are disabled 2. have you tried a bunch of your police cars...?

check you ELS.ini in your main game folder. Is ElsTrafCtrlOn set to true?

can you send a screenshot please of the issue