Charlie686

This could be a mods folder issue; please rename your mods folder to _mods & retry.

Hi there, You are missing RAGENativeUI which can be found here. Hopefully this helpful. 😄

Rename your mods folder to _mods & retry.

Hiya - are you sure you don't have ENB?

Open the Vehicle.meta and find the vehicle in question and make sure it has the flags FLAG_LAW_ENFORCEMENT, FLAG_EMERGENCY_SERVICE and VehicleClass is VC_EMERGENCY

Oh of course you do! 😂Only kidding. I think we should both go to sleep (in your new apt.841 🤣) and hand this thread over to NRS who god forbid isn't overwhelmed with the notifications. As you rightfully said, I am glad some middle ground was met & the conversation remained constructive.

For me this entire conversation is nonsensical. Even if 9/10 people who you simply say "report this to the developer" don't bother, 1/10 people can report a bug. And just one report can stop thousands of users facing issues. Bug reporting is how you truly help user's experience more stable gameplay. Even if @thatmaxplayle must lose his ambient events despite all the hours gone into trying to make them work. 😂

It certainly isn't the be all to end all solution however, ultimately something was causing your plugin to crash - that's why reports are so useful. I'm glad you managed to fix it so quickly. This whole thing has drifted. My point is that you should make it clear when telling people to objectively remove plugins (that cause issues) that they aren't actually causing their crash in the log. If you don't have the "time" to say "You should report this to the developer" (literally - that's all that any developer asks for) the real question is do you have time to provide good support at all?

Nobody is saying that anyone can stop something becoming invalid, that's not a point anyone is making. If something is invalid a crash can be prevented. DeadlyWeapons had a ped which was deleted, this caused it to crash. That can be prevented through error handling as Max outlined.

"it caused a crash." - Pretty sure that's saying DeadlyWeapons crashed as the ped was deleted. Just because it crashed does not mean it warrants its removal, but equally that is not what we are discussing.

Max has hit the nail on the head here. Just like when you get an invalid ped, the developer should introduce some sort of error handling to prevent an LSPDFR crash coming about. The reason I commented was that "cause issues" is vague, and without an explanation seems to suggest that those plugins may've been at fault. That's why I think it should be made clear to the user they aren't related to the crash at hand, as demonstrated within the log.

Hiya, Increase your Plugin Timeout Threshold to 60,000 & retry.

Hiya, best bet is attaching your log in full. 😄

It is compatible.

Hiya, It's probably best if you try typing out what you specifically need help with. 😄

Out of curiousity why do you think that? Just keen to figure it out myself. As for the list provided I would have to disagree. These quote on quote broken plugins are not causing your crash as I am sure @thatmaxplayle would corroborate. I'm sure we could all have a discussion about why or why not a plugin may be "broken" however ultimately there is no indication that those plugins caused the crash - hence I don't believe you should objectively get users to "remove them"; instead if you really believe a plugin is "broken" maybe convey that the user may experience issues with the plugin, but also make it known it is in no way related to the actual crash log provided. Considering I was mentioned I just wanted to add my opinion on this, as I can interpret your comment to be misleading that all those plugins are causing issues, which they are not. I just feel that is something which should be conveyed to the user. 🙂

You'd want to go to /Plugins/LSPDFR and sort it out. Quite frankly, it's a bit of a mess with old plugins that are discontinued & cause issues, alongside installations which should not be there (RAGENativeUI does not belong there.) FayaCallouts is causing this specific crash, you should remove it.

Hiya, Please rename your mods folder to _mods & retry.

Make sure your RAGENativeUI is up-to-date.

Re-add vfs.dll to re-enable LML & diagnose the issue.

If it isn't looking right in OpenIV it sounds like something that should be raised with the developer.

This means your issue is with LML; make sure it is updated / check your installations with it. If you don't want to keep it, you can just remove LML.

This is incorrect, it does not check your mods folder. 🙂 Neither is verifying related to this error. @themanncub First, create an exception for the GTAV folder to your antivirus, then retry.

Uninstalling LSPDFR won't do anything. You are just removing then re-adding the same files, no? There are several steps you should do before uninstalling anything. Especially when you look at their log, there is nothing indicative of needing the user to reinstall LSPDFR. @brisbaneplanespotter737 First, confirm GTAV works without RAGE (i.e. you are able to enter story mode.)

No worries, let me know how it goes.