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.

UnknownBastion

Community Team
  • Joined

  • Last visited

Everything posted by UnknownBastion

  1. That is correct. As per my first message, it is in the Main Directory.
  2. Hmmm...Im not sure about filename. You can just search for pack names.
  3. No, it's not related. However, some things do crash as a result of something else crashing first. In this case, I dont think that was what was happening. As for the crash, screenshot the ini for Riskier Traffic Stops.
  4. Are you saying that pressing F4 causes the game to crash?
  5. I'm pretty sure the error you got in relation to Riskier Traffic Stops is from incorrectly editing the ini file for it. The number you put in for the chance of an event happening was invalid. You must change it to a valid number. Additionally, Police Station Armory Loadouts Creator.exe also threw an error. Not sure if this was a result of Riskier Traffic Stops crashing or its own problem.
  6. There was no crash in the log. Could be from the mods folder.
  7. There is a search function in OpenIV for that. However, as long as the handling for the vehicles is relatively the same (unless you plan on editing some metas a bit), you can rename a downloaded car to policeold1 and place it in the designated replace path for replace vehicles.
  8. Please send the RPH Crash Log. It is a txt file in the Main Directory either called RagePluginHook or RagePluginHook.log. It is NOT in the Logs folder.
  9. Rename your mods folder to _mods and try again. Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.
  10. There was an issue with Callout Interface. Try re-installing the CalloutInterfaceAPI to the Main Directory and see if that helps. I saw that right before the actual crash it had an issue reading a callout pack (specifically Super Callouts).
  11. Glad to have assisted!
  12. Well everything is loaded and working. Could be a silent crash. Try going into the lspdfr.ini and changing the following to reflect below: Ambient.DisableEscapedSuspectEncounter = true
  13. Add your Main Directory to the exceptions list for the anti-virus. Then re-install manual LSPDFR and restart PC. Then try again.
  14. Re-install the Microsoft Speech Platform so you can get the correct speech engine. Reference this video for more information.
  15. Please ensure you have StopThePed installed to Plugins/LSPDFR and NOT to just Plugins. If you do, please resend the RPH Crash Log. The one you provided cannot be opened. Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.
  16. Try launching GTA V first. Then once fully in story mode, tab out and launch RPH.
  17. Please refrain from creating duplicate topics regarding the same issue. Thanks! As per your issue, please send the RPH Crash Log. It is a txt file in the Main Directory either called RagePluginHook or RagePluginHook.log. It is NOT in the Logs folder.
  18. I don't believe so. I believe those are hardcoded in.
  19. Go into the lspdfr.ini and change the following to reflect below: Main.DisableGameBlipHiding = true If still having issues, please send the log again. Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.
  20. Looks like an incorrectly edited xml for StopThePed. Either revert changes made to whichever xml you edited or reinstall StopThePed. Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

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.