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 Keybinds don't work after a while and problems with plugin reloading

Featured Replies

Hello,

 

I encounter no issues in terms of being able to pull people over and accept callouts at the beginning of a patrol. However, after playing for some time (say around 20-30 minutes), these key binds suddenly stop working. I use the "ForceDuty" command in LSPDFR in order to begin patrols most of the time. This is a constantly recurring issue that has been happening for the last week now. I believe much of the time, this happens after I perform traffic stops but this is not always the case. If there is a solution that does not involve me having to completely reinstall LSPDFR, that would be quite handy. My callouts are all for LSPDFR 0.4, but I do have many callouts and LSPDFR plugins. I also do have quite a lot of add-on vehicles, but I have a modified gameconfig.xml for the latest version of GTA V.

 

Also, just a side tangent, I am unable to reload all plugins or go off duty without RPH crashing outright. This is infuriating because relaunching every time for a minor issue is a pain in the neck. If anyone could offer any insight into this problem, that would also be fantastic. The LSPDFR version I am using is 0.4.9. My plugin threshold is set to 60000 milliseconds. I am willing to rename my mods folder to _mods as a last resort to see if that helps with this issue, but I would prefer other options. 

 

The only commandline arguments are -disableCustomLoadingScreen and -DX11.

 

Attached is my RagePluginHook.log file. If necessary, I can also provide exactly what callouts and such I have, as well as any other details that are needed for troubleshooting.

 

Follow up: Ok, so the first problem seems to take place after a traffic stop exclusively.

RagePluginHook.log

Edited by policeenthusiast155
Additional details for the first crash

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