Skip to content
View in the app

A better way to browse. Learn more.

LCPDFR.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
The latest updated version of RAGE Plugin Hook, required to play LSPDFR, can be found inside the LSPDFR download. It is not currently available on the RAGE Plugin Hook website.

lspdfr crashing on force duty, idk which plugin is causing it

Featured Replies

(FIXED!)



every time I go on duty the game will crash, I checked the ragehook log and I can't figure out what plugin is causing the crash, and at the end it says

WARNING! Plugin "LSPD First Response" was terminated because it caused the game to freeze (Freeze was caused by game fiber: Console Command Fiber For "ForceDuty").   


Can someone help me find out what is causing it?

RagePluginHook.log

Edited by JohnnyBeagle
FIXED

Johnny

24 minutes ago, JohnnyBeagle said:

nvm I found the issue, 686 callouts was causing the crash

Hey!

Just wanted to say that this crash was not caused 686Callouts! 

 

The following plugins are outdated. This means they are not updated for the latest LSPDFR version.
I'd suggest their removal for the smoothest experience as they may cause issues.
However, if you find this fixes the issue, you are welcome to try re-adding them.
Though if an issue does reappear, then the plugin(s) should not be kept.

Better EMS
Keep Calm

Developer of ChaosCallouts
unknown.png

28 minutes ago, JohnnyBeagle said:

nvm I found the issue, 686 callouts was causing the crash

Hi there,

First up, this is not an issue with me.

Just because removing 686 Callouts fixes it, does not mean 686 Callouts was at fault.

This could be due to a conflict, but most likely due to the old plugins you have, as mentioned by Dylan.

In fact, in the log provided 686 Callouts had actually finished, and therefore wasn't actually doing anything when it crashed because everything had been completed.

 

I would also like to mention that if you think there is an issue, any plugin developer appreciated you reaching out. 

Bug reports are one of the main ways to reduce bugs. 😄

 

All the best,

Charlie686

Prefer support on Discord? Want your log automatically read? Join my server to receive live support!

https://discord.gg/SJfxcAhjCF

 

Developer of Callout Pack 686 Callouts & Discord Bot 686 Utilities.

 

This is a support topic.
Only reply here to offer help or assistance to JohnnyBeagle. Off-topic or "me too" replies will be removed.

Need support yourself? Make a new topic instead.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.