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.
Due to overzealous filtering on Microsoft’s side, some emails to Outlook and Hotmail addresses may not be delivered. If you’re affected, please use a different email address or try again later.

[REL] LPCallouts [EOL]

You're viewing a summary of the most helpful posts in this topic — about 9 minutes of reading instead of 57 minutes for all 100 posts.

Featured Replies

I wished that I have more time to develop the callouts further, but its simply not possible. Therefore I make my callouts public for everybody who wants to enhance their callout experience

If you use code from my Repo or Clone it for further dev, please keep the credits.

 

 

https://github.com/CK-Paradox/LPCallouts

 

Currently released version: 0.3.0.0

 

Features:

Custom Model Support

 

ChangeLog:

Spoiler

Version 0.3.0.0
- Updated to LSPFR 0.4.9.0
- Updated to Rage 1.86.1288.16169
- Updated to RageNativeUI 1.7
- Changed to .NET 4.7.2
- Changed name of user from ini to LSPDFR Character
- Changed smoking ped from animation to world scenario
- Removed support for ComputerPlus (Plugin no longer supported), was introduced in 0.2.7.0
- Removed support for Realism Dispatch Enhanced, was introduced in 0.2.6.2
- Removed LPC Editor, direct editing of values in ini are now required
- Added possiblity to set individual backup unit names in ini file
- Added animation when dispatch is called
- Fixed a memory leak that could crash the game client

 

Version 0.2.7.1

- Fixed Issue with callout crashing if not accepted

 

Version 0.2.7.0

- Update to Rage 0.51
- Added support for ComputerPlus
- Added possibility to set callout probability 
- Added notification for player when scene is left before finishing conversations
- Fixed issue with multiple spawns of peds at scene
- Fixed issue with missing peds at scene
- Fixed crashes at Assist Drifter scene
- Various stability improvements

 

Version 0.2.6.5

- Fixed Issue with RDE removing police peds/vehicles from already loaded scene

 

Version 0.2.6.2
- Added the possibility to set custom model definitions (New Editor included) -> Support of RDE
- Fixed an issue with modifier key set to NONE was showing an error
- Fixed Issues with missing entities.
- Various improvements

 

Version 0.2.5.1
- Added Modifier Key for Menu

 

Version 0.2.5.0
- Removed LPC Editor
- Added Ini file
- Added LPC Editor for Ini File
- Added Headlight on/off depending on daytime of scenery vehicles
- Added Ped animations to all scenes
- Added Jurisdiction selection menu
- Added Maximum Spawn radius added to ini file ( possible to view in in game menu )
- Added new scene locations in Los Santos County and Blaine County for all Callout types
- Added Suspect Dialogs for Beach scene
- Recoding off all Assistant callout (lots of improvements)
- New Freeway Assist Callout added
- Peds that in conversation now always face player, independent from viewing angle
- Changed Backup audio to LPC, to support Better Dispatch Audio

 

Version 0.2.0.1
- Added Noise Complaint Callout
- Added Maximum Callout spawn radius
- Added LPC Config Editor instead of ini
- Fixed Helicopter explosions or missing at cyclist scene (this time really)
- Fixed Wait Position of police cars in sidewalk scene
- Fixed a bug at Vespucci Beach Callout when arriving at suspect 

 

Version 0.1.1.0

- New Random function ( Suspects now less flee )
- GameEngine specifc checks added
- Spelling errors corrected
- Recoded Cop assistant function. Should work now as it was intended to be 
- Fixed a bug where sometimes data of suspect vehicle was not loaded and caused callout to crash.
- Fixed a bug at Bike Scene where helicopter sometimes was not loaded or exploded
- Fixed a bug where the blip of the witness in surfer scene was not deleted after conversation was finished
- Fixed a bug on SideWalk scene where a wrong Dispatch notification was send even if suspect already identifed
- Fixed a bug where assistant cars didn´t start driving to the assigned area.
- Fixed that suspect boat was outside of searcharea
- Fixed aborting Callout cause of wrong eventhandler
- Fixed a bug where peds on scene sometimes went crazy
- Fixed a bug that interaction input key was always set to default
- Changed position of objects in El Burro Heights scene
- Changed livery of helicopter always to ambulance version
- Changed location naming on Beach Scene from street to area
- Added Icon to Dispatch message
- Added Light Damage to suspect vehicle 

 

This Callouts feature its own editor for user values. There is no ini file to edit.

 

Currently featured callouts:
Assistance required: (Hit and Run)

  • Arrive on scene and assist the first responders in finding a hit and run suspect. Talk to other officers, the victim, and witnesses in order to get the information needed to make a proper arrest.

 

Distrubance (Noise Complaint)

  • An citizen has reported loud noise/a party in their neighbourhood. Get to the caller and gain information. Afterwards solve the conflict

 

What is currently in developing stage:

  • Improvments of code
  • New Callout Type
  • More Locations

 

 

 

At this point i want to thank my testers of helping me find bugs...

Edited by LowRid3R
Changelog v0.3.0.0

  • 3 weeks later...
  • Replies 99
  • Views 19.2k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • thx for the reports, i will check the issue with the AssistCyclist Scene....

  • @Yard1 this is how the editor will look like. I'm using xml serializsation for the strings.. therefore the editor is more usefull than directly editing the xml file... hope this is what

  • @BeastyBill88 You're right, the editor allows you to set the models to anything you like.. ( so RDE is not a must , but it uses the same function/interface ). After the next release, plans are to inte

Posted Images

On 9/28/2016 at 5:58 AM, LowRid3R said:

... yes :) ... but as you are requested as assistance i named it like that... then afterwards you find out that it´s a hit and run :)

First off, he'll never see this because you didn't quote him.

 

Second, I don't know if that's how a hit&run works. A hit&run is anytime a car flees the scene of an automobile accident without getting information or taking proper "protocol"

As suggested in your comment: the individual runs away, you chase him, then later find out that "OH! HE HIT SOMEONE AND RAN?!?! I had no Idea it was a hit and run. Thanks for telling me"

18 minutes ago, Narobic said:

A cool idea would be to have a suspect give only a partial plate and you have to go to all of the addresses that match the partial. You take the witnesses/suspect and they identify the person.

Play around a bit in the del perro/hawick area. ;)

Please, call me Crazy.

I try to make youtube videos. Check them out here: https://www.youtube.com/channel/UC7rzz2IoI4lW1Bdc70yZEIA

  • 1 month later...
  • 1 month later...

Hi @LowRid3RI just downloaded your update and tried it out. I got the hit and run call in Braddock Pass (near the tunnel in Sandy) and I loved it. The scene is amazing. There are however a lot of text mistakes while talking to the witnesses, some phrases don't make sense, almost feels like you started writing something, then changed your mind but didn't delete the beginning of the sentence. 
#1: (victim)
Player says: How do you know. Have you already talked to involved people?
Should be: How do you know? Have you already talked to the people involved?
Cop answers: Unfortunately not. I took care about getting EMS and the fire team here.
Should be: Unfortunately not. I called it in to EMS and Fire department first.

#2 (witness 1)
Witness says: I was driving on the second lane at suddenly the guy on the first one pulled over.I reacted and flipped the car.
Should Be: I was driving in the right lane and suddenly, the guy on my left swerved into my lane. I tried to avoid him but overcorrected and flipped the car.
Officer says: Did the person set the indicator, or did he just pull to your side?
Should be: Did he use his indicator? Or did he just merge into your lane?
Witness says: No. He just pulled to my lane without any notice.
Should be: No, He just merged into my lane without notice.
Witness says: Thanks for your info. Maybe San Andreas Highway Patrol will contact you again.
Should be the Officer who says that, and should be: Thanks for the information, we will contact you again if we need anything else.

#3 (witness 2)
Officer says: Hi SAHP. Are you the second involved person of this crash?
Question doesn't really make sense, she wouldn't know if she's second, third or what ever, should be: Hi SAHP, Where you involved in this crash?
Witness says: Hi yes, I was driving behind the car that flipped. (that line is fine)
Officer says: So can you describe the situation that caused this accident?
Should be: Can you tell me what you saw?
Witness says: Sure, A vehicle pulled into the guys car with any notice.. One happened to the other and BAAM.
Should be: Sure, A vehicle swerved and hit the guy's car without notice. They hit each other and that guy lost control and his car flipped.
The rest is fine, except at the end, you switched witness for officer again, like in #2, Witness says: Thanks for your time, if you need anything then contact SAHP.
Should be Officer that says: Thanks for your time, if you remember anything else, please contact the SAHP.

Also, the text disappears really fast. I don't know if you have a way to make it visible on screen longer? Give people time to read it.

Hope this helps 🙂







 

Edited by GabLeGamer

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...

Similar Content

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.