Hello,

 

recently, lspdfr crashes all the time. unfortunately, i don't know what the problem is and how to fix it.

 

if needed i can also send my crashreport, but it was changed last month at the 05/14 for the last time.

 

thanks for any help!!

RagePluginHook.log

Your crash was caused by DeadlyWeapons, which is outdated and has to be removed.

You have many many callouts, some of them are outdated, time for the SUPER MEGA UPDATE OUTDATE SOFTWARE FROM @Charlie686🧚🏽‍♀️🥸🥳🤑💦

 

6 hours ago, NRS said:

Hello,

 

recently, lspdfr crashes all the time. unfortunately, i don't know what the problem is and how to fix it.

 

if needed i can also send my crashreport, but it was changed last month at the 05/14 for the last time.

 

thanks for any help!!

RagePluginHook.log 367.28 kB · 2 downloads

Remove the plugins in RED & YELLOW (they are outdated or cause issues)
DO NOT REMOVE DEADLY WEAPONS

1 hour ago, OfficerChris1 said:

Your crash was caused by DeadlyWeapons, which is outdated and has to be removed.

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.

Edited June 10, 20223 yr by Mrsuperx13

thanks for the help, if there are still problems i will write again

2 hours ago, Mrsuperx13 said:

I believe Interaction+ may have been the specific cause of this crash.

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. 🙂 

 

 

Edited June 10, 20223 yr by Charlie686

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.

@Mrsuperx13 - I’m not sure what or why you designate a plug-in as outdated, and although I can only speak for my own plug-in - I know for a fact that mine is not outdated! It shouldn’t cause issues (or at least, I’ve had no issues reported to me) 

 

I have to agree with the points made by @Charlie686.

 

Deadly Weapons was the plug-in that caused this crash. Therefore the issue should be reported to the developer of Deadly Weapons, and you can move on. Ultimately, the only way a plug-in can become outdated is if it flat out *does not work* due to an update of either LSPDFR, RPH, or GTA V. Even if a mod as been abandoned by its developer, it’s not outdated until game changes prevent it from working as it should.

 

Having a lot of callout packages installed is very unlikely to cause other plugins to crash. Of course, it’s not impossible - but properly written packs will behave in a way as to not interfere with entities and elements of other installed plugins. 

 

Ultimately, Deadly Weapons is the only plug-in with an issue here. Not anything else! 

 

Regardless, enjoy your day/night!

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.

It is not DeadlyWeapons.
 

4 minutes ago, A Stranger said:

It is not DeadlyWeapons.
 

Strictly speaking - it was. Sure, a ped was deleted - but there’s always the opportunity for some exception handling to prevent issues like this from crashing the plug-in.

 

That was more my point. I never said to delete any plugins, i’m not that draconian. My advice was simply to report the matter and move on, my post says just that. 🙂 

3 minutes ago, A Stranger said:

It is not DeadlyWeapons.
 

"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.

From what I know, it's not something that can be specifically fixed. It just is. 
If you want a more indepth explanation, I am more than happy to provide it. But I am sure you got your own explanations.

The important factor is that NRS is being helped and that his game runs smoothly & he is able to enjoy it. 

1 minute ago, A Stranger said:

From what I know, it's not something that can be specifically fixed. It just is. 

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.

4 hours ago, OfficerChris1 said:

Your crash was caused by DeadlyWeapons, which is outdated and has to be removed.

You have many many callouts, some of them are outdated, time for the SUPER MEGA UPDATE OUTDATE SOFTWARE FROM @Charlie686🧚🏽‍♀️🥸🥳🤑💦

 

Deadly Weapons is not "outdated" or "broken."

My plugin works fine with the latest versions of LSPDFR. Yes the crash was caused by it but there are many variables when it comes to monitoring peds, vehicles, traffic events, etc. Occasionally errors will happen causing a crash, that's just the joy of modding GTA. Please do not assume things if you do not know. 

 

 

 

As for the other plugins in the list, I cannot speak on their behalf. I know MrSuper and others have collected a list based off past reports and experience but ultimately the choice is yours and if you notice issues with any of them you can remove or disable them at your own will.

If you ever notice an issue with one of my plugins feel free to contact me here or via discord with a crash log. Again this crash looks like a 1 off.

19 minutes ago, thatmaxplayle said:

@Mrsuperx13 - I’m not sure what or why you designate a plug-in as outdated, and although I can only speak for my own plug-in - I know for a fact that mine is not outdated! It shouldn’t cause issues (or at least, I’ve had no issues reported to me) 

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. 

--------------------------------------

19 minutes ago, thatmaxplayle said:

Deadly Weapons was the plug-in that caused this crash. 

Here you concede my point. Yes deadly weapons crashed but it was not the cause.

-----------------------------------------

19 minutes ago, thatmaxplayle said:

Ultimately, the only way a plug-in can become outdated is if it flat out *does not work* due to an update of either LSPDFR, RPH, or GTA V. Even if a mod as been abandoned by its developer, it’s not outdated until game changes prevent it from working as it should.

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. 

-------------------------------

19 minutes ago, thatmaxplayle said:

Ultimately, Deadly Weapons is the only plug-in with an issue here. Not anything else! 

 

Again based on SuperPyroManiacs explanation of how this functionality works your statement is wrong. 

Edited June 10, 20223 yr by Mrsuperx13

5 minutes ago, Charlie686 said:

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.

 

I have error handling, on the very event where this crash happened. It is not a save all solution. GTA is just fun like that.

Try / catch statements work well, but not perfectly.

Edited June 10, 20223 yr by SuperPyroManiac

2 minutes ago, SuperPyroManiac said:

 

I have error handling, on the very event where this crash happened. It is not a save all solution. GTA is just fun like that.

 

I know that all too well 😂 

 

Members of the community have to accept that *stuff does crash sometimes*

 

No matter how much error handling you have (now to say that you had none was certainly not my intention - so I apologise if it came across that way) it will sometimes still fail, and that’s a byproduct of modding a game that wasn’t designed for modding, to put it simply.

 

With regards to your rather empty statement about my plugin, @mrsuperx13 - if you were that good at support, you’d either be sending people with issues with 136 my way, or sending the logs to me yourself. It’s that simple. Who better to support a product (not even specifically in the GTA community) than the person/people who made it? You are trying to fight a point that just isn’t there I’m afraid. 

14 minutes ago, A Stranger said:

From what I know, it's not something that can be specifically fixed. It just is. 
If you want a more indepth explanation, I am more than happy to provide it. But I am sure you got your own explanations.

The important factor is that NRS is being helped and that his game runs smoothly & he is able to enjoy it. 

 

I would agree with this statement. No error handling is perfect, and 💩 crashes sometimes. I do feel like there’s room in this community for that to become more acceptable.

 

After all, we’re playing or developing mods for a game that is definitely not supposed to be modded. Hey ho! 

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. 

Just now, Mrsuperx13 said:

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. 

 

That is a very naive and quite frankly lazy way of doing things. I would even argue that it isn’t proper support. Either way, the fact of the matter is, you should be advising people to report matters to developers. That quite honestly is the best way to make the experience better for everyone. I’m not going to argue with you because you think that just deleting anything that appears in a log fixes issues - but I would advise you to reflect on the way you do things, hopefully integrating some better practices in the future.

 

Anyways, I best get to fixing all those bugs I don’t know about with (no) thanks to lazy “support representatives.”

 

Enjoy your day.