exortion

Good evening. I came across an unexpected crash after attending a Protest callout. Recreation Respond to Callout > On Scene to Dispatch > Call in backup > Check IDs and vehicles of cars around protest > Found individual with items of interest > Went to Car to open Computer > Long Press Q > Crash RagePluginHook.log

Couldn't find a solution after searching through everything, I believe all plugins are up to date.

Hi again everyone, I experienced another crash, unlike my previous post this is a bit different. The issue from the log: Unhandled Exception: The log indicates an unhandled exception for the type System.Exception with the message "Processing cache while it's still in use - one or more subcalls may have caused the thread to yield". Possibly trying to process or modify a cache (likely related to an entity or ped management in the game) while it was still being accessed or used by another part of the code. Location of Error: The error occurred in the file CPedCache.cs at line 45, being a part of the scripting of entities for managing peds. I think the issue is related to how peds or entities are being handled or cached within the mod. I feel like the mods were likely trying to manage or update entities (like peds or vehicles) in a way that conflicted with the game's or mod's internal state management. I think 3-5 things were happening at the same time which may have caused a sort of overload, is there any way to fix this other than removing half of my callout mods? I also attached a video of what was going on 20 seconds before LSPDFR crashed, forgive the low quality due to heavy compression. RagePluginHook.log Untitled video - Made with Clipchamp (2).mp4

Thanks, I updated it from 1.4.0 to 1.5.0, I also removed Forestry Callouts yesterday, LSPDFR seems to be okay now.

Hi. I experienced an issue regarding a potential Callout Manager issue after ForrestryCallout2 and United Callout activated in sequitur. I am not sure if I should go ahead and remove Forestry Callouts or not. From what I currently understand in the log: • The game was running normally, processing police-related events and callouts. • A new callout was created from the ForestryCallouts2 mod but was ended due to being out of the maximum distance range. • A new second callout attempted to start from United Callouts mod "[UC] Apartment Burglary", leading to an unhandled exception in the CalloutManager. • The error caused LSPDFR to shut down, causing the game to crash. • The null reference exception suggests the mod was trying to access or use an uninitialized object. I think as a solution I should delete Forestry Callouts however it is a shame because it is good, unless I am wrong. Does anyone have ideas? RagePluginHook.log

Thank you. Also, do you happen to know about a solution to an issue where backup called via UltimateBackup/LCPDFR, none of the Cops/allies show up in the Map as blue blips, they respond but aren't visible on the map. Is there a reason why?

Hey everyone. I experienced an issue while on patrol when I attempted to initiate a pursuit after the game prompted the message only for the client to crash - I attempted to restart the mod on the Rage console which froze the gameplay as a whole but kept the menu/map functional. I attached the log, I would appreciate help in getting to the bottom of this. The exact moment of the crash would be this section here: [8/21/2024 10:01:52 PM.224] LSPD First Response: [Section136Callouts] Stat change request received... [8/21/2024 10:01:52 PM.224] LSPD First Response: [Section136Callouts] Callout: NULL Stat: STAT_PURSUIT Change: STAT_INCREMENT [8/21/2024 10:01:52 PM.224] LSPD First Response: [TRACE] Removing ped from Chase #2 (GameplayMandatory) [8/21/2024 10:01:52 PM.224] LSPD First Response: [TRACE] Released 0 entities from Chase #2 Content Manager [8/21/2024 10:01:52 PM.224] LSPD First Response: [TRACE] Instance cleaned (Chase #2) [8/21/2024 10:01:53 PM.582] LSPD First Response: [INFO] LSPDFR has shut down And anything before that in the crashlog, whereas anything afterwards is when I attempted to restart the Mod on the Rage console. Thank you for your help. RagePluginHook.log