My LSPDR keeps crashing when trying to go on duty. I have updadted everything for the new update but can not figure out why its crashing

RagePluginHook.log

53 minutes ago, Kyle234 said:

My LSPDR keeps crashing when trying to go on duty. I have updadted everything for the new update but can not figure out why its crashing

RagePluginHook.log 154.21 kB · 0 downloads

Open RAGEPluginHook.exe, then immediately hold shift while it loads up. Change "Plugin Timeout Threshold" in the window to 60000. Click Save and Launch. Let me know if this works.

Edited July 30, 20223 yr by DarkVypr

On 7/30/2022 at 3:53 PM, DarkVypr said:

Open RAGEPluginHook.exe, then immediately hold shift while it loads up. Change "Plugin Timeout Threshold" in the window to 60000. Click Save and Launch. Let me know if this works.

This hasn't worked unfourtanly. I have attached the new rage log below

RagePluginHook.log

30 minutes ago, Kyle234 said:

This hasn't worked unfourtanly. I have attached the new rage log below

RagePluginHook.log 104.56 kB · 0 downloads

Just wondering why you are using Albo's mods? I'm not sure if they are working with current versions of the game.

Edited August 2, 20223 yr by DarkVypr
clarification

2 minutes ago, DarkVypr said:

Try disabling 686 Callouts.

 

Hiya,

Wanting to provide some clarification here. 🙂

 

Just because I decided to write something to the RagePluginHook log within 686 Callouts does not mean there is an issue with 686 Callouts.

Looking at the last line of a log tends to be very unreliable; let me give an example.

A user's game crashes with LSPDFR logging being the last thing occurring. You wouldn't tell the user to remove LSPDFR - that principle is best extended to other things as well. 😄

 

Equally - other things may be occurring at the time of the crash. Plugins should not be penalised for simply logging while going about their business.

I would pay attention to the plugins that are for an older version of the LSPDFR API as well as the errors within the log, not my informational logging. 

 

All the best.

 

 

18 minutes ago, Charlie686 said:

Hiya,

Wanting to provide some clarification here. 🙂

 

Just because I decided to write something to the RagePluginHook log within 686 Callouts does not mean there is an issue with 686 Callouts.

Looking at the last line of a log tends to be very unreliable; let me give an example.

A user's game crashes with LSPDFR logging being the last thing occurring. You wouldn't tell the user to remove LSPDFR - that principle is best extended to other things as well. 😄

 

Equally - other things may be occurring at the time of the crash. Plugins should not be penalised for simply logging while going about their business.

I would pay attention to the plugins that are for an older version of the LSPDFR API as well as the errors within the log, not my informational logging. 

 

All the best.

 

 

Yea I guess I worded it pretty poorly lol. I think I was trying to say disable it (to see if it would cause a difference) but said remove instead.

 

Changed the reply.

 

My bad 😅

Edited August 2, 20223 yr by DarkVypr

3 minutes ago, DarkVypr said:

Yea I guess I worded it pretty poorly lol. I think I was trying to say disable it (to see if it would cause a difference) but said remove instead.

 

My bad 😅

Not at all.

Always feel free to mention me if something looks up with 686 Callouts and if something is up with any plugin, always tell the user to report it to the developer!

That's all I had to say, thank you. Enjoy your evening / day.

Edited August 2, 20223 yr by Charlie686