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 ScenarioManager Crashing

Featured Replies

So I've been having this issue ever since I updated to 0.4. Basically I can't play for more than 10 minutes without LSPDFR crashing constantly with this error message. I'm not sure what is causing the crash but I'm assuming it has something to do with random events? Any help is appreciated!

 

Spoiler

[3/8/2019 2:07:38 PM.664] LSPD First Response: ==============================
[3/8/2019 2:07:38 PM.664] LSPD First Response: UNHANDLED EXCEPTION DURING GAME FIBER TICK
[3/8/2019 2:07:38 PM.664] LSPD First Response: ------------------------------
[3/8/2019 2:07:38 PM.664] LSPD First Response: Origin: Game fiber "ScenarioManager".
[3/8/2019 2:07:38 PM.664] LSPD First Response: ------------------------------
[3/8/2019 2:07:38 PM.664] LSPD First Response: Exception type: System.NullReferenceException
[3/8/2019 2:07:38 PM.664] LSPD First Response: Exception message: Object reference not set to an instance of an object.
[3/8/2019 2:07:38 PM.664] LSPD First Response: ------------------------------
[3/8/2019 2:07:38 PM.664] LSPD First Response: Inner exceptions:
[3/8/2019 2:07:38 PM.664] LSPD First Response: ------------------------------
[3/8/2019 2:07:38 PM.664] LSPD First Response: Stack trace:
[3/8/2019 2:07:38 PM.664] LSPD First Response: at ?????????????????????????????????????????.?????????????????????????????????????????() in E:\GTA V\LSPD First Response\LSPD First Response\Mod\Scenarios\ScenarioFakeTrafficStop.cs:line 98
[3/8/2019 2:07:38 PM.664] at ?????????????????????????????????????????.?????????????????????????????????????????() in E:\GTA V\LSPD First Response\LSPD First Response\Mod\Scenarios\Scenario.cs:line 26
[3/8/2019 2:07:38 PM.664] at ?????????????????????????????????????????.?????????????????????????????????????????() in E:\GTA V\LSPD First Response\LSPD First Response\Mod\Scenarios\Scenario.cs:line 52
[3/8/2019 2:07:38 PM.664] at ????????????????????????????????????????.?????????????????????????????????????????() in E:\GTA V\LSPD First Response\LSPD First Response\Mod\Scenarios\ScenarioManager.cs:line 58
[3/8/2019 2:07:38 PM.664] at ?????????????????????????????????????????.?????????????????????????????????????????() in E:\GTA V\LSPD First Response\LSPD First Response\Engine\Scripting\ThreadedScriptComponent.cs:line 66
[3/8/2019 2:07:38 PM.664] at Rage.GameFiber.Main()
[3/8/2019 2:07:38 PM.664] LSPD First Response: ==============================
[3/8/2019 2:07:38 PM.664] LSPD First Response: 
[3/8/2019 2:07:38 PM.675] LSPD First Response: [FATAL] Forced termination
[3/8/2019 2:07:38 PM.676] LSPD First Response: [TRACE] Released 0 entities from DefaultContentManager
[3/8/2019 2:07:40 PM.810] LSPD First Response: [INFO] LSPDFR has shut down
[3/8/2019 2:07:41 PM.883] LSPD First Response: STP: Core Module is exited unexpectedly 
[3/8/2019 2:07:41 PM.905] LSPD First Response: ==============================

 

RagePluginHook.log

  • Author
1 hour ago, SGT.Dillehay said:

scenario oh hasnt been updated for 0.4 yet so you will have to wait until its updated i would suggest removing it until then

I'm not currently using scenario oh, never have. As far as I know everything I'm using is supposedly working with 0.4. Here is my plugins folder: 

 

98703290_download(1).thumb.png.22084dc395b8210ab35ca39d2777b7e4.png download.png.319982fc2a6fe49822be853d05353f3d.png85202541_download(2).png.f3262f01d18a9b2b5aba9e9b61df40d0.png

what is my officer in your plugins? that could be an issue try and remove that and see if it works

 

it also could be callout plugins causing it as well because most of the callouts are for 0.3 and havent been updated for 0.4 so your best bet is to stick with the callouts that use the 0.4 api. i would suggest getting rid otb callouts and agency callouts and see if that helps. they do have a thread on here with a list providing what is stable with 0.4 as well if you want to read that and get more info on what can be used.

  • Author
14 hours ago, SGT.Dillehay said:

what is my officer in your plugins? that could be an issue try and remove that and see if it works

 

it also could be callout plugins causing it as well because most of the callouts are for 0.3 and havent been updated for 0.4 so your best bet is to stick with the callouts that use the 0.4 api. i would suggest getting rid otb callouts and agency callouts and see if that helps. they do have a thread on here with a list providing what is stable with 0.4 as well if you want to read that and get more info on what can be used.

I think myofficer is part of agency callouts, it's just to specify a unit number. I tried removing myofficer, OTB and agency callouts; still crashing with the same error. 

I did a clean reinstall last night and added back mostly everything except callouts and its running smooth but whenever I put in a callout pack I'm getting that crash. Even with callouts that are supposed to be working like PeterU and assorted callouts.

This is a support topic.
Only reply here to offer help or assistance to MichaelDotJar. 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.