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.

PeterU

Members
  • Joined

  • Last visited

Everything posted by PeterU

  1. There aren’t any ambient events in PeterUCallouts at the moment. It does have detection for certain things that might happen e.g. traffic collision will add questions you can ask the driver to the LSPDFR+ traffic stop questions, but doesn't generate any ambient events. Which callouts are having problems? Please post a RagePluginHook.log from when this happens so this can be investigated.
  2. Was this a whole game crash, or an LSPDFR crash?
  3. Can you provide RagePluginHook.log files from when these things happen? Can you provide a RagePluginHook.log from a session where this issue happens? Does this happen with all of my callouts, or just some? This looks like it might be an issue with custom vehicle as the crash occurs in Rage.Vehicle.HandleVehicleCreation.
  4. Please can you let me know in what circumstances the game crashes (does it always happen at a particular point?) and provide a RagePluginHook.log. This is for LSPDFR 0.4.4. I can't update the label to say designed for API 0.4.4, as this isn't an option. (The 0.4.4 API doesn't have any changes I don't think from the 0.4.2 API).
  5. I'm looking at this issue for the next release. It's not just you! The current version still works fine in LSPDFR 0.4.4. I'm working on an update with a new callout too.
  6. Do you have a RagePluginHook.log file from the session when this happened? There's definitely an issue here with this callout that is worse in some locations than others. I will look at fixing this in an upcoming release.
  7. The idea here is that such a concentration of high-value vehicles in one place where VINs have obviously been switched on different parts is likely plenty enough evidence to bring a strong case that those vehicles are stolen. Sometimes the boss will refuse to co-operate and you'll need to get evidence from a vehicle parked outside on public property, but it sounds like you already had pretty good evidence.
  8. You don't need to separately install "Street Name Addon", that's correct. Copy the files to your GTA V folder from the PeterUCallouts package and all should work.
  9. I don't think this was me! The check digit in the VIN is calculated through a process that adds up the other values in the VIN and divides them by 11: the check digit is the remainder. In the case where a VIN is transcribed incorrectly, for example, it is often possible to determine this without looking up in an external database. In our case, I'm assuming not all criminals are intelligent enough to realize they need to calculate a valid VIN check digit when they're falsifying them. You're spot on here. I have done the vehicles needed for the new callout and a good handful of other GTA vehicles. It is time consuming, however, to gather the coordinates of the different VIN positions on the vehicle to make the animations have some realism. I'll add to this over time. It will always be the case that add-on vehicles may not be supported, and will fall back to this method of resolving a VIN. Something's not rendering correctly there -- I did see this in testing when the VIN was too long and thought I caught all those cases I could find. Can you figure out if it's always the same motorcycle model that does this?
  10. There is a bug within LSPDFR affecting setting Personas and this should be fixed in the next version of LSPDFR. (The message says "if an update is available, apply it") So, there's nothing to do yet -- PeterUCallouts will work around it in the meantime. When LSPDFR 0.4.2 comes out, update to that.
  11. I have discovered a reproducible crash in LSPDFR itself that occurs when asking a ped for ID, where that ped has had their Persona replaced using the API. [6/10/2019 7:18:34 PM.180] LSPD First Response: ============================== [6/10/2019 7:18:34 PM.180] LSPD First Response: UNHANDLED EXCEPTION DURING GAME FIBER TICK [6/10/2019 7:18:34 PM.181] LSPD First Response: ------------------------------ [6/10/2019 7:18:34 PM.181] LSPD First Response: Origin: Game fiber "<UNNAMED THREAD>". [6/10/2019 7:18:34 PM.182] LSPD First Response: ------------------------------ [6/10/2019 7:18:34 PM.183] LSPD First Response: Exception type: System.NullReferenceException [6/10/2019 7:18:34 PM.184] LSPD First Response: Exception message: Object reference not set to an instance of an object. [6/10/2019 7:18:34 PM.184] LSPD First Response: ------------------------------ [6/10/2019 7:18:34 PM.185] LSPD First Response: Inner exceptions: [6/10/2019 7:18:34 PM.185] LSPD First Response: ------------------------------ [6/10/2019 7:18:34 PM.186] LSPD First Response: Stack trace: [6/10/2019 7:18:34 PM.187] LSPD First Response: at LSPD_First_Response.Engine.Scripting.Entities.Persona.CreatePed(Persona persona, Vector3 position) in E:\GTA V\LSPD First Response\LSPD First Response\Engine\Scripting\Entities\Persona.cs:line 447 [6/10/2019 7:18:34 PM.187] at ............................................................................................................................GetPedHeadshotTxd(Persona persona, Boolean bigHeadshot, Boolean noObscuredFace) in E:\GTA V\LSPD First Response\LSPD First Response\Engine\Scripting\Functions.cs:line 2095 [6/10/2019 7:18:34 PM.189] at .......................................................................................................................................................................................................................................................() in E:\GTA V\LSPD First Response\LSPD First Response\Mod\PedInteraction.cs:line 126 [6/10/2019 7:18:34 PM.190] at .......................................................................................................................................................................................................................................................() in E:\GTA V\LSPD First Response\LSPD First Response\Mod\PedInteraction.cs:line 108 [6/10/2019 7:18:34 PM.190] at .......................................................................................................................................................................................................................................................(........................................................................................................................... ) in E:\GTA V\LSPD First Response\LSPD First Response\Engine\Scripting\ThreadedScriptComponent.cs:line 86 [6/10/2019 7:18:34 PM.191] at .......................................................................................................................................................................................................................................................() in E:\GTA V\LSPD First Response\LSPD First Response\Engine\RecurringTask.cs:line 48 [6/10/2019 7:18:34 PM.192] at .......................................................................................................................................................................................................................................................() in E:\GTA V\LSPD First Response\LSPD First Response\Engine\Main.cs:line 54 [6/10/2019 7:18:34 PM.192] at .......................................................................................................................................................................................................................................................() in E:\GTA V\LSPD First Response\LSPD First Response\Mod\LSPDFR.cs:line 741 [6/10/2019 7:18:34 PM.193] at Rage.GameFiber.Main() [6/10/2019 7:18:34 PM.193] LSPD First Response: ============================== Proof of concept (in context of a PoC callout plugin😞 ped = new Ped(); ped.SetPositionWithSnap(Game.LocalPlayer.Character.GetOffsetPositionFront(3.0f)); Persona newPersona = new Persona("Testy", "McTestFace", LSPD_First_Response.Gender.Male); Functions.SetPersonaForPed(ped, newPersona); Game.DisplaySubtitle("Now cause the ped to be Stopped by Player by holding 'E' and ask for ID."); I've also built the DLL in case it's easier to throw this in plugins\LSPDFR, go on duty and reproduce the crash.
  12. Could you please provide the RagePluginHook.log file from your GTA V folder?
  13. For my use, having this evaluated when a chase begins would be enough... I am thinking that, for my purposes, I'd set this at ped creation time in pretty much all cases.
  14. Does this happen in every call? Just one of my calls? How frequently, compared to times you are able to complete the call successfully?
  15. I would welcome the ability to set chances on whether or not a suspect fleeing on foot will attempt to hijack a vehicle (or perform other actions that "raise the stakes" of the crimes they have thus far committed) -- it seems to me that not all fleeing suspects would want to escalate things as they do sometimes in 0.4.
  16. Which callout are you in at the time? This particular callout has integration with Coastal Callouts. I'm afraid there is no immediate solution for playing this callout but to wait for a public Coastal Callouts release or gain access to that mod through PNWParksFan's loyalty program.
  17. Has CheepCallouts been updated for 0.4? Maybe it isn't too clear -- you need to investigate the area until you think you've found all the evidence, then press the end callout key (End) to see how you did!
  18. The troubleshooter is not yet updated for LSPDFR 0.4 plugins. Please can you provide a RagePluginHook.log file from your GTA V directory from a playing session when you see the "disregard".
  19. Could you post a RagePluginHook.log from a session where you play this callout and arrest the suspect(s) before ending the call?
  20. Please provide a RagePluginHook.log from your GTA V folder. I believe this is a false positive, where only VBA32 anti-virus detects this. https://www.virustotal.com/#/file/d0a097eacd3c00b557b0164dea5fb7326f8f1f3c76b91afc9e789b0e7c10b0f1/detection The claimed infection name ends with "Heur", suggesting "heuristic", i.e. the anti-malware engine thinks the software behaves in a similar way to other software that has been seen which is malicious. I have no reason to believe this is anything other than a false positive. Indeed all the other 60 anti-malware engines on VirusTotal believe the file is clean. Please can you provide a RagePluginHook.log from your GTA V folder. I don't believe this crash was related to PeterUCallouts. GetPedHeadshotTxd is mentioned, which is a part of the new LSPDFR 0.4 features where pedshots have an image when you ask for ID. I'm afraid there is not much other information that suggests this is something I can track down. Is this happening repeatedly? None of the plugins are required for PeterUCallouts to function, but they are recommended to have the best experience. I have seen one other log like this -- the crash originates in GetPedHeadshotTxd, which I believe is a part of LSPDFR 0.4 relating to showing ped images when you ask for ID. I don't believe this is specific to PeterUCallouts. Have you updated Traffic Policer to its latest version?
  21. Things are on hold while I await LSPDFR 0.4 like everyone else (no point developing something that might not work!), but I will try and look at this with the Stop the Ped author after compatibility with 0.4 work is done.
  22. What other plugins do you have installed please? I have seen this in videos, but I believe it is related to how another plugin may be handling peds.
  23. I will not have access to LSPDFR 0.4 before anyone else, so I will only be able to begin work on compatibility with 0.4 when it is released publicly.
  24. I got to this too late, but the locations available for this callout currently are Grapeseed, Sandy Shores, Paleto Bay and Harmony. If you patrol in some areas you won't be close enough to have this be offered. I forgot to mention these locations in the release notes! The license screen is now displayed automatically the first time you start one of the callouts, so no keypress is needed.
  25. Can you please post a RagePluginHook.log file from when this happens?

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.