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 Crash when accepting a callout due to SlimDX

Featured Replies

I'm back trying out LSPDFR after a long time and everything was fine until today after trying to install ScriptHookVDotNet and this continues to happen after removing it.

 

Spoiler

[7/30/2024 9:44:49 AM.005] LSPD First Response: [TRACE] Callout created:  #1
[7/30/2024 9:44:49 AM.013] LSPD First Response: GetAudioFileForAction: No file found for: STREET_HAWICK_AVE
[7/30/2024 9:44:49 AM.014] LSPD First Response: CalloutInterface: [DEBUG] Detected CalloutEvent.Before, creating new incident
[7/30/2024 9:44:49 AM.015] LSPD First Response: CalloutInterface: [DEBUG] Adding new incident to the model, FriendlyName = PedestrianHit  Status = New
[7/30/2024 9:44:49 AM.016] LSPD First Response: CalloutInterface: [DEBUG] simulating incident response for PedestrianHit
[7/30/2024 9:44:49 AM.027] LSPD First Response: CalloutInterface: [DEBUG] IncidentWidget detected a new callout
[7/30/2024 9:44:49 AM.027] LSPD First Response: CalloutInterface: [DEBUG] IncidentWidget resetting
[7/30/2024 9:44:49 AM.028] LSPD First Response: CalloutInterface: [DEBUG] IncidentWidget received an UpdateItem event for  PedestrianHit
[7/30/2024 9:44:49 AM.028] LSPD First Response: CalloutInterface: [DEBUG] IncidentWidget updated item matches our current item
[7/30/2024 9:44:49 AM.028] LSPD First Response: CalloutInterface: [DEBUG] IncidentWidget updating the details for PedestrianHit
[7/30/2024 9:44:49 AM.055] LSPD First Response: CalloutInterface: [DEBUG] start time: 7/30/2024 9:05:01 PM for PedestrianHit
[7/30/2024 9:44:49 AM.055] LSPD First Response: CalloutInterface: [DEBUG] waiting 42 in-game minutes for PedestrianHit
[7/30/2024 9:44:49 AM.406] 
[7/30/2024 9:44:49 AM.406] ==============================
[7/30/2024 9:44:49 AM.406] UNHANDLED EXCEPTION OCCURRED
[7/30/2024 9:44:49 AM.406] ------------------------------
[7/30/2024 9:44:49 AM.406] Origin: HOOK
[7/30/2024 9:44:49 AM.406] ------------------------------
[7/30/2024 9:44:49 AM.406] Exception type: System.Runtime.Serialization.SerializationException
[7/30/2024 9:44:49 AM.406] Exception message: Type 'SlimDX.Result' in Assembly 'SlimDX, Version=4.0.13.43, Culture=neutral, PublicKeyToken=b1b0c32fd1ffe4f9' is not marked as serializable.
[7/30/2024 9:44:49 AM.406] ------------------------------
[7/30/2024 9:44:49 AM.406] Inner exceptions:
[7/30/2024 9:44:49 AM.406] ------------------------------
[7/30/2024 9:44:49 AM.406] Stack trace:
[7/30/2024 9:44:49 AM.406] at System.Runtime.Serialization.FormatterServices.InternalGetSerializableMembers(RuntimeType type)
[7/30/2024 9:44:49 AM.406] at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
[7/30/2024 9:44:49 AM.406] at System.Runtime.Serialization.FormatterServices.GetSerializableMembers(Type type, StreamingContext context)
[7/30/2024 9:44:49 AM.406] at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitMemberInfo()
[7/30/2024 9:44:49 AM.406] at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter, SerializationBinder binder)
[7/30/2024 9:44:49 AM.406] at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Write(WriteObjectInfo objectInfo, NameInfo memberNameInfo, NameInfo typeNameInfo)
[7/30/2024 9:44:49 AM.406] at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck)
[7/30/2024 9:44:49 AM.406] at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph, Header[] headers, Boolean fCheck)
[7/30/2024 9:44:49 AM.406] at System.Runtime.Remoting.Channels.CrossAppDomainSerializer.SerializeObject(Object obj, MemoryStream stm)
[7/30/2024 9:44:49 AM.406] at System.AppDomain.Serialize(Object o)
[7/30/2024 9:44:49 AM.406] at System.AppDomain.MarshalObject(Object o)
[7/30/2024 9:44:49 AM.406] ==============================
[7/30/2024 9:44:49 AM.406] 
[7/30/2024 9:44:52 AM.153] LSPD First Response: CalloutInterface: [DEBUG] finished waiting for timeout for PedestrianHit
[7/30/2024 9:44:52 AM.153] LSPD First Response: CalloutInterface: [DEBUG] call no longer open, ending simulation for PedestrianHit

 

Any help is very appreciated

               

Solved by trocapalot

Go to solution
  • Author
  • Solution

This seems to only be happening when receiving any callouts from Kuchera Callouts which is odd as it was working completely fine earlier.

 

I fixed it by replacing the scanner audio files, for whatever reason the old ones we're causing crashes

Edited by trocapalot

               

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