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.

GTAbear

Members
  • Joined

  • Last visited

Everything posted by GTAbear

  1. Its that part that is really odd. If all bikes was disabled, it would be more logical, but one works.. That is odd Have you some Mods installed? Some Mods allow themself to disable not only some weapons, but also vehicles. That is serious annoying! You could try and disable all installed Mods, and then see if a Vanilla LSPDFR installation allows you to ride all bicycles
  2. My guess is that you either have something that is not deleted or you deleted something that should not. The simplest way forward is to remove everything Get your GTAV game verified and updated, and then download a complete new LSPDFR pack incl. RPHook, and do a reinstall ( Simplest is the manual install, then just drag everything into GTAV-folder
  3. The part on pastebin shows nothing and is not complete Do this: In ..GTAV| Find file RagePluginHook.log Rename it OLDRagePluginHook.log (just to keep it, you can also just delete it) The open LSPDFR and play until you crash. The new RagePluginHook.log should be tiny. drag that file into this topic
  4. There are invalid props in loading pipe-line Do you have a folder named Mods? If so, try rename it _Mods, and retry LSPDFR
  5. At least AmbientAICallouts is reported as in need of updating. Try and disable it. The general method for troubleshooting is to disable all mods, and then add them in sequence each with a new test-run But if you know when the fail was introduced and also know you added a MOD just before, then testrun without that newly added mod
  6. At least AutomaticSirenCutout is reported as in need of updating. Try and disable it. The general method for troubleshooting is to disable all mods, and then add them in sequence each with a new test-run But if you know when the fail was introduced and also know you added a MOD just before, then testrun without that newly added mod
  7. Please drag this file ..GTAV| RagePluginHook.log Into this topic
  8. Have not seen that before. How do you start your game? Best is to follow: https://www.lcpdfr.com/forums/topic/125624-rph-does-not-open-game/
  9. What is the gameplay? Have you considered that? Gameplay is the most important angle to consider at all time, when you make a computer-game, and a call-out is a 'kind' of computer-game-Level. What is the difference between stealing gas and apprehending any Ped on any location? Are there any special gameplay in the situation stealing gas? If you can find new special or interesting gameplay in the situation, then you have a good chance to make a great call-out
  10. Its that part that is strange unless you did something to files or folders Yesterday, did you? Other options are tedious but should work.. Make a game-update with your game-site, (i only know how to in EPIC) Just look in Q&A on their site. Retest LSPDFR Not fixed? Verify your game. It takes HOURS 😕 Retest LSPDFR Not fixed? Reinstall LSPDFR completely Retest LSPDFR Not fixed? Then you have some pc-issue could be with activeX or ?? Lets hope we dont need to go there..
  11. Have you re-booted and not just restart, but complete-reboot * go to Power * press & hold SH then mouse-select Shut-down * After the prolonged full shutdown, pull the plug and wait 2 mins, before you restart the pc * Restart GTAV & initiate LSPDFR as normal
  12. At least UnitedCallouts is reported as in need of updating. Try and disable it. The general method for troubleshooting is to disable all mods, and then add them in sequence each with a new test-run But if you know when the fail was introduced and also know you added a MOD just before, then testrun without that newly added mod
  13. So you dragged 'something' into chatGPT ... ? Instead drag this file ..GTAV| RagePluginHook.log Into this topic
  14. The most plausible reason, but not the only one, is that You need to setup RPHook so LSPDFR is selected as load on activation. To do that open RagePluginHook and click the cogwheel-icon, then make sure you have selected LSPDFR in the load-plugin-section Like this: If its not that, its get more complicated..
  15. rsg.ms is R* homepage. You get an R* error if you have an non-updated main-game (GTAV for online gaming). The method for updating depends on where you bought your game. Basically you should just follow the instructions. If you have a pirated version, you are out of luck
  16. At least Emergency Callouts is reported as in need of updating. Try and disable it The general method for troubleshooting is to disable all mods, and then add them in sequence each with a new test-run But if you know when the fail was introduced and also know you added a MOD just before, then testrun without that newly added mod
  17. Yes that is 'normal' if you have found a plugin that acts up, then disable it, and retry. Only the author can fix program-errors. Your only action is to disable it. ( A civilized thing to do is to reach out to the programmer if there are any contact info in the readme-file
  18. Did you also get the newest RNUI from Alex? https://github.com/alexguirre/ I have no idea why that is not in the RPHook-pack
  19. At least ALPRPlus is reported as in need of updating. Try and disable it. The general method for troubleshooting is to disable all mods, and then add them in sequence each with a new test-run But if you know when the fail was introduced and also know you added a MOD just before, then testrun without that newly added mod
  20. Super! Have fun !

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.