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.

Stealth22

Friends of LSPDFR
  • Joined

  • Last visited

Everything posted by Stealth22

    The car is very appealing to the eye, and your efforts are very much appreciated. Unfortunately, the collision issues have forced me to stop using it. Like jukeboxknox said in his review, just driving by a pothole makes the car go flying through the air. In pursuits, it is very frustrating. Not being able to close the doors is annoying too.
  1. Shameless plug alert... I've done this in Code 3 Callouts. Only two events to start off with, more to be added later.
  2. Either it's Traffic Policer, as posted above, or, I had this happen to me once. The simple trainer has a keyboard shortcut to spawn attacking peds. I hit it by accident once, and I had like 4 red Ferrari's spawn next to me, and each one had two Italian mobster type guys with assault rifles in their hands. Let's just say that every flipping Sheriff's Deputy in the entire state responded to that backup call. I don't remember which keybind it is, but I just went into the ini and disabled most of the keyboard shortcuts, lol. Most likely, it's traffic policer you're talking about tho.
  3. Mods, feel free to delete this post if I am breaking any rules. I have posted this in the comments section for Keep Calm, as well as it's forum thread in the Script Mods subforum. But I wanted to ensure that the message reached as many people as possible. And also, the reason I posted it again in this subforum was to try and eliminate any unnecessary support requests in the LSPDFR section. If you have v0.7.0 of Keep Calm installed, I recommend that you rollback to v0.5.1. I take full responsibility for the bug, and I sincerely apologize for it. I am working to find a fix as quickly as possible. Thanks!
  4. You've turned into quite the developer, my friend!! Stupid question, for the "NoSweat" feature...does that only activate during a traffic stop? I'd hate to have vehicles ignore me when I'm going Code 3 to a shots fired call!
  5. IMPORTANT NOTICE: VERSION 0.7.0 HAS BEEN REMOVED! Due to a massive oversight on my part, Keep Calm v0.7.0 has a strange bug where suspects in a pursuit are "calmed", and thus, drive away from the police like they are on a Sunday picnic. While somewhat hilarious, this bug obviously takes away from the realism of LSPDFR. I would like to offer my sincere apologies for this error...I never felt the need to test pursuits, because I never thought they would be affected! I have decided, therefore, to remove the download file for v0.7.0 until this issue can be fixed. I have tried a couple of things already, but this bug is proving to be a difficult one to nail down. Please stand by for a further update. In the meantime, Keep Calm has now been rolled back to v0.5.1. For now, please ignore the parts of the file description that say you require Stealth.Common.dll and RPH v0.24. These are NOT required for Keep Calm 0.5.1.
  6. EDIT: v0.7.1 has been released, and it includes a fix for the 'slow pursuit' bug in v0.7.0!
  7. I have never been a fan of the Chevrolet Impala as a vehicle, @Bxbugs123. But your model makes me want to drive it!! Seriously, this is some amazing work. I'm really tempted to drive this on a patrol of the highways.
  8. Oh ok, I didn't know that. It makes sense, when you think about the area that those guys have to patrol, haha. Just to clarify, I wasn't trying to be rude or anything. I meant no disrespect, I hope I didn't offend you. I was just saying that they look out of place for a city department like the LAPD, for example. My apologies, I should have been more clear. A department out in the middle of nowhere like the Alaska State Troopers definitely need something a little more powerful than Dodge's OEM lights, haha. So it should be an optional extra for sure. I just wouldn't want it to be a permanently attached part.
  9. I definitely understand the purpose for them. But those particular lights just look so out of place, and almost too big in that location. Why not just use the OEM fog lights from Dodge? Well in any case, its an optional extra, so, to each their own. Sweet! Can't wait to drive it!!
  10. Looks amazing, man! I can't wait to drive it! And yeah, I agree. Take out the lights on the front by the license plate, and its good to go. That's going in my FBI Buffalo slot for sure!!
  11. You can check ID's the same way that you always do, by holding E. That's a native function of LSPDFR.
  12. Actually, he provided useful feedback to me by verifying that a bug existed.
  13. Huh...that never came up in my testing. But then again, I never got into any pursuits. I'm working on a fix for that, but having some difficulty so far. Hope to have it fixed soon. Thanks for pointing that out, guys!
  14. Right, I forgot RPH implemented those. I wrote those extension methods before those properties were brought in, so I've just kept them in there, lol.
  15. One of the mods is probably going to move this to the Support forum, but anyway... Chances are you're using a version of Rage Plugin Hook that is not compatible with the versions of Police Radio and Code 3 Callouts that you have installed. Can you copy-and-paste the contents of your RagePluginHook.log file (it can be opened with Notepad) to www.pastebin.com and post the pastebin link here? We need to see the contents of your log file in order to see what's wrong.
  16. This is something that I never imagined would come up. But it has, to some extent, so I'd like to address it. I received a private message from @Albo1125 earlier. It contained the following excerpt: Albo1125, of course, does not at all feel like I stole the idea of ambient events from him. In fact, in my changelog above, I made a reference to his traffic events, and how he did such a great job on them. To be honest, I was surprised that people in this community have been saying things like that. Ambient events have been around since LCPDFR; just like callouts, they are not 'copyrighted' by any individual. If I had created a set of ambient events that were completely identical to Albo1125's, sure, that wouldn't be ethical at all. But we both thought of the idea at the same time; he was just quicker to implement it. This update has been in development for a few weeks now, and because it involves so many changes, it required a lot of testing. So if I create a separate set of unrelated ambient events that have nothing to do with traffic enforcement, and I'm slower to develop them, does that make me a thief? My apologies if I am offside with this post, but to be blunt, those sorts of baseless arguments are completely uncalled for. I don't wish for there to be any further discussion on this, as I'd like to keep this comments section focused on support issues, and well...comments regarding Code 3 Callouts. If anyone has any comments or questions regarding what I have just talked about, please keep it out of the public domain, and feel free to send me a private message. I just wanted to set the record straight, if there is anyone out there who has any doubts, that's all. Again, I was hesitant about addressing this, but felt I should at least say something about it. Thanks, everyone. I appreciate the support and kind words that everyone has offered, and I hope to continue developing quality scripts for LSPDFR. Now, back to your regularly scheduled comments... At this time, no, unfortunately not. It has been requested by myself and other developers for a future version of the LSPDFR API. If and when it is ever implemented, I can take another look at this.
  17. Unfortunately, I don't know of a way to add police parts/extras to a civilian vehicle via script. I didn't want to give the suspect an actual police vehicle, because when you run the plates, it would come back as being registered to the City of Los Santos, and once people start installing more modded vehicles, it would have all of the "real" police equipment on it. I know it sucks, but we just sort of have to roleplay that the suspect bought some lights off eBay or something and fitted them to his vehicle illegally.
  18. No worries, glad I could help! Let me know if you have any more questions. Looking at the code again, you may want to change the flag to, ConsiderGroundVehicles, I think it's called. Not that there's going to be an aircraft or boat near your ped, but if you're OCD about it like me....lol
  19. List<Entity> entities = World.GetEntities(myPed.Position, 10f, GetEntitiesFlags.ConsiderAllVehicles).ToList(); List<Vehicle> vehList = (from x in entities where x.Exists() && x.IsVehicle() select (Vehicle)x).ToList(); vehList = (from x in vehList where x.IsPlayersVehicle() == false select x).ToList();That will get you a list of vehicles within 10 meters of the ped. If you want the nearest vehicle, you could do: Vehicle v = (from x in vehList where x.IsPlayersVehicle() == false orderby x.Position.DistanceTo(myPed.Position) select x).FirstOrDefault();That would sort the list by distance to the ped, and then get the first Vehicle in the list, or if the list is empty (no vehicles found), it would return null. Is that what you're looking for? EDIT: Damn it, I forgot that Entity.IsVehicle() and Vehicle.IsPlayersVehicle() are extension methods that I wrote. They are relatively simple to implement though. IsVehicle() is just calls a native called IS_ENTITY_A_VEHICLE or something like that. IsPlayersVehicle just checks if the vehicle is the player's CurrentVehicle or LastVehicle. (With null checks and .Exists() checks in between, of course lol)
  20. Oh ok. That's probably not a huge issue for now, haha. Let's make sure its 100% working first. Can you give me contributor access on the second repo? (And where are we making changes for now, until we decide where to keep it?)
  21. Just to be clear, by "custom banner", you mean being able to replace that "RageNative UI" header at the top of the menu?
  22. If thats the case, we should pick one place to keep it, and have it only live in that repo. We certainly do not want multiple copies of the code living in different places. Don't delete anything yet, though. I think we should have a collective discussion/decision about it. @LMS, what do you think? My thoughts on the matter, personally, are maybe it should be in it's own dedicated repository. Simply because of potential issues that would be reported, and so on. Alex can take ownership of it, since he took the lead on getting the original author's permission and such. Whoever contributed to the code (myself, LtFlash, etc) can be added as collaborators on that Git repo, and be credited in the releases. I don't mind having it in the LSPDFR repo, but it's starting to spin into it's own project, rather than being under the LSPDFR umbrella. It doesn't reference any LSPDFR classes, and I don't see why it ever would. We can keep a RAGENativeUI example in the LSPDFR repo, but my main concern (if you can even call it a concern) with keeping the entire project in the LSPDFR repo is that the repo may get flooded with issues/documentation for RAGENativeUI. Thoughts? And just a side note @alexguirre, is the native UI library working now, or are there still issues with it? What needs to be fixed, if anything? EDIT: If there is anything outstanding, start creating issues for them in your repo. Otherwise we'll start forgetting what needs to be done.
  23. VERSION 0.7.0 HAS BEEN RELEASED! The mechanics of Keep Calm have been re-built from the ground upKeep Calm v0.7.0 requires RPH v0.24!Peds driving a vehicle will still scream and be somewhat affected by gunfire, but they drive off in a controlled mannerPeds on foot are still ignored by Keep Calm; I hope to improve on this in a future update, but I wanted to focus on drivers firstNOTE: Keep Calm now relies on the Stealth.Common DLL included with Traffic Control and Code 3 CalloutsKeep Calm 0.7.0 is packaged with v1.3.0 of the Stealth.Common DLLThis version is NOT compatible with Code 3 Callouts v0.3.0 or earlier; Code 3 Callouts must be upgraded to v0.4.0, which was just released today (Sept 9, 2015)Traffic Control v0.5.0 is compatible with v1.3.0 of the Stealth.Common DLL
  24. VERSION 0.7.0 HAS BEEN RELEASED! The mechanics of Keep Calm have been re-built from the ground upKeep Calm v0.7.0 requires RPH v0.24!Peds driving a vehicle will still scream and be somewhat affected by gunfire, but they drive off in a controlled mannerPeds on foot are still ignored by Keep Calm; I hope to improve on this in a future update, but I wanted to focus on drivers firstNOTE: Keep Calm now relies on the Stealth.Common DLL included with Traffic Control and Code 3 CalloutsKeep Calm 0.7.0 is packaged with v1.3.0 of the Stealth.Common DLLThis version is NOT compatible with Code 3 Callouts v0.3.0 or earlier; Code 3 Callouts must be upgraded to v0.4.0, which was just released today (Sept 9, 2015)Traffic Control v0.5.0 is compatible with v1.3.0 of the Stealth.Common DLL

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.