Basically, rather than show the normal LSPDFR menu the stats of the story mode characters is shown. This happens every time I go on duty in LSPDFR, and when this bug occurs I can't accept callouts or blip and pull anyone over.

It's as if LSPDFR has stopped working but hasn't actually crashed. Regardless of what agency I go on-duty as or if I use ForceDuty or not, this bug keeps on occurring and basically make LSPDFR unplayable.

 

Here is my RAGEPluginHook.logRagePluginHook (2).log

Edited June 30, 20223 yr by Yan the Yam

3 hours ago, Yan the Yam said:

Basically, rather than show the normal LSPDFR menu the stats of the story mode characters is shown. This happens every time I go on duty in LSPDFR, and when this bug occurs I can't accept callouts or blip and pull anyone over.

It's as if LSPDFR has stopped working but hasn't actually crashed. Regardless of what agency I go on-duty as or if I use ForceDuty or not, this bug keeps on occurring and basically make LSPDFR unplayable.

 

Here is my RAGEPluginHook.logRagePluginHook (2).log

Hey,

That's a common bug, you can't really do anything about it except not opening the menu if you don't really need to.

1 hour ago, Bekobi said:

Hey,

That's a common bug, you can't really do anything about it except not opening the menu if you don't really need to.

To be honest, it doesn't matter if I open the menu or not. This bug happens every time, only a few minutes after I go on duty. I might be able to pull one person over or respond to one callout but soon after LSPDFR will break and I can no long pull people over or accept callouts. Rather than being the trigger of the bug, the menu showing the story mode stats is an indication that the bug is active

28 minutes ago, Yan the Yam said:

To be honest, it doesn't matter if I open the menu or not. This bug happens every time, only a few minutes after I go on duty. I might be able to pull one person over or respond to one callout but soon after LSPDFR will break and I can no long pull people over or accept callouts. Rather than being the trigger of the bug, the menu showing the story mode stats is an indication that the bug is active

Might you tell me which plugins you have installed at the moment ?

2 hours ago, Yan the Yam said:

an indication that the bug is active

   

15 hours ago, Mrsuperx13 said:

   

My RagePluginHook log is attached to my first post.

8 hours ago, Yan the Yam said:

My RagePluginHook log is attached to my first post.

Sorry I missed it.
I'd start with updating these two plugins (in yellow)  
There is nothing in your log indicating any sort of error - once you've updated those two plugins, go in game again and when it happens again upload the new log.
p.s. if this is happening after accepting a callout make sure you are completely dismissed from the callout once it is finished. Most callouts have the option to Press the END key to forcibly end them.

18 hours ago, Mrsuperx13 said:

Sorry I missed it.
I'd start with updating these two plugins (in yellow)  
There is nothing in your log indicating any sort of error - once you've updated those two plugins, go in game again and when it happens again upload the new log.
p.s. if this is happening after accepting a callout make sure you are completely dismissed from the callout once it is finished. Most callouts have the option to Press the END key to forcibly end them.

I noticed that if I disable my mods folder (i.e. rename it to _mods) the bug goes away meaning that something in my mods folder is what is causing this. Do you have any idea what in the mods folder could be causing this?

I figured it out! Setting the police radio action to chest was resulting in this bug. I set it back to shoulder and it seems to have gone away.

 

EDIT: I stand corrected, the bug is still there. I think I found some sort of a fix though—just don't access the pause menu at all.

Edited July 3, 20223 yr by Yan the Yam

Nevermind, the actual fix is to physically not patrol in Los Santos. I noticed that if I patrolled in Sandy Shores/Paleto Bay/Blaine County in general this bug would never occur, but patrols in Davis, for example, would lead to the bug occurring almost instantly.

 

Perhaps the bug could be related to frame rates?

On 7/2/2022 at 4:13 AM, Yan the Yam said:

I noticed that if I disable my mods folder (i.e. rename it to _mods) the bug goes away meaning that something in my mods folder is what is causing this. Do you have any idea what in the mods folder could be causing this?

If you've discovered disabling the mods folder fixes it then you have already found the solution...