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 - InvalidHandleableException/SuspectTransportManager Error

Featured Replies

Hello LSPDFR Community,

 

I'm seeking assistance with some issues I've been encountering in LSPDFR. After returning from a lengthy hiatus, I've jumped back into playing LSPDFR and have faced a couple of persistent problems.

 

Issue 1: SuspectTransportManager Error 

The first issue I observed is AI arrests leading to an immediate crash of LSPDFR. The log shows an error related to "SuspectTransportManager." The log points to an unhandled exception occurring in the game fiber titled "SuspectTransportManager." This seems to be linked to a System.NullReferenceException, with the specific message being "Object reference not set to an instance of an object." It also lists out a drive location,  but I can not find this anywhere within. When I hear suspect transport manager I think of albo1125, but I haven't used any of those plugins in ages.

 

Steps Taken:

  • Updated LSPDFR and all associated plugins.
  • Checked and reconfigured game and mod settings.
  • Searched for and attempted to resolve mod conflicts by disabling other mods.

 

Issue 2: InvalidHandleableException


After that, I am now observing a new recurring crash, as indicated by my RPH log. The log repeatedly shows Rage.Exceptions.InvalidHandleableException, with the error message stating, "Operation is not valid because the specified Rage.Ped is invalid." Again, AI arrests cause an immediate crash of LSPDFR.

 

Steps Taken:

  • Reinstalled LSPDFR.


Despite these efforts, the issues persist.

 

I unfortunately didn't think to save the first log to my desktop to keep, so the RPH log I uploaded is the most recent.

 

Thank you in advance for your support and assistance. I'm looking forward to getting back into LSPDFR and would greatly appreciate any help in resolving these issues.

 

Best regards,
Ed

RagePluginHook.log

Solved by thota

Go to solution
  • Solution

Update:
HypersCallouts

LoreCallouts

UrbanCallouts(Install the 2.0.0.0) version

 

Remove:

SpecialCallouts

 

These do NOT belong in GTAV/plugins/LSPDFR reinstall them  in your main GTA folder.

CalloutInterfaceAPI

Newtonsoft.Json

Want live LSPDFR Support? Come and join the Unofficial LSPDFR Support Server! Stop on by and get your issue solved through one of our Public Support channels.
Link: https://dsc.gg/ulss
Reminder: This is a fan Discord, and is in no way an Official LSPDFR Discord Server, nor is it related to G17 Media or the LSPDFR Team as a whole.

  • Author

Thanks Thota, that worked. I knew I was missing something. I hadn't played in quite a number of years. 

 

Also, I think it's important to share a crucial tip for anyone who might come across this thread in the future. If you're updating the Lore Callouts mod, it's essential to delete the old files before installing the new ones. I noticed that directly installing the updated Lore Callouts without removing the old files first led to duplicate files in the GTAV/lspdfr/plugins directory. This caused instant LSPDFR crashes, and removing the duplicates fixed that issue.

 

Thanks again for the help.

 

Warm regards,

 

Ed

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