ziipzaaapM16A4

That is correct. Age does not determine a plugins up-to-date status.
 
I have no reports of AAIC features that broke since the last few lspdfr updates therefore i did not release any fix updates for the currently public version of AAIC. 
 
I looked at your code and it seems like the crash has been initiated due to the "SuspectTransportManager" which is from lspdfr. Of course i can't tell you if that was lspdfr's fault or another plugin tampering with objects from this lspdfr fiber.
but the AAIC log at the bottom is basically just AAIC complaining that it cannot work without LSPDFR therefore ist shutting down.
 
What really caused the crash stays in this case unclear.
 
 
 
 
 
 

That is correct. Age does not determine a plugins up-to-date status.
 
I have no reports of AAIC features that broke since the last few lspdfr updates therefore i did not release any fix updates for the currently public version of AAIC. 
 
I looked at your code and it seems like the crash has been initiated due to the "SuspectTransportManager" which is from lspdfr. Of course i can't tell you if that was lspdfr's fault or another plugin tampering with objects from this lspdfr fiber.
but the AAIC log at the bottom is basically just AAIC complaining that it cannot work without LSPDFR therefore ist shutting down.
 
What really caused the crash stays in this case unclear.
 
 
 
 
 
 

Hey Alfie, long time no see!
 
To provide some clarification: AmbientAI Callouts is not outdated. Age does not determine if a plugin becomes outdated, code does.
Developers can't always be expected to re-build their plugins on a new version if there's no need to, so pretty much all plugins on 0.4.8 will work just fine on 0.4.9.
 
@ziipzaaapM16A4 I am sure will be happy to clarify whether his plugin is outdated. 🙂 
 
 

They are set up for my Modpack so i believe this won't help you
i use for all areas Pol,pol2,pol3,sherriff2 
and all of them use as livery pattern 0 = LSPD, 1 = LS County, 2 = Blaine county

It's probably LSPDFR's AmbientSpawn.
That and other things are the reason why i have UB and LSPDFR configured for correct liverys.
But you can decrease the amount of vehicles for ambient spawn in the LSPDFR settings.

The only thing that comes to my mind is RDE. Unless someone else knows of another mod. 

@JBuzz826
I looked though the files of RDE 3.1.6 and found a script called LiveryChanger.dll for ScriptHook and a XML file where i can enter my values. 

Thank you.

The crime system is part of LSPDFR and we have a list of events that we consider crimes. These are picked up from events happening in the game, such as someone stealing a car or firing a gun. Each event has an assigned priority so that when you a ped commits multiple crimes you are calling in their most severe crime. You can not manually trigger these events. A (possible incomplete) list of events that we process internally:
 
Murder
BrandishingWeapon (Usually when player is harassed by gangs)
DisturbingThePeace (Usually when player is shoved)
AssaultPeaceOfficer
GrandTheftAuto
HitAndRun
Assault

Thanks to some community efforts and continued interest in keeping LCPDFR alive, we are happy to announce that LCPDFR, the mod which started it all, is now on GitHub. If you ever wanted to see how things worked back in the IV days (or just trash-talk the work of a few 14-year-old kids writing code), you have come to the right place.
 
Please find the repo below: https://github.com/LMSDev/lcpdfr_public

We've released a minor compatibility update for LSPDFR 0.49 (Build 8242) which adds compatibility for the new version of GTA V (v2699) - "The Criminal Enterprises".
 
This includes a fix in RAGE Plugin Hook for a long standing issue where if you used the NVIDIA GeForce Experience overlay (which is enabled by default on some installations), RAGE Plugin Hook may fail to hook. It also includes a feature which allows developers to load dependencies from other folders, hopefully leading to more tidy game folders in the future.
 
Although by the time of this post we have already fixed two major issues, the first being an issue with non-Steam versions of the game and the other being a change in behaviour of a fairly crucial native method, please report any issues or bugs with LSPDFR on the new game version, if you find any, on the support forums.  If you do think you've found an issue, please make sure you're on the latest patch (your RPH log should mention you are on version 1.96) and you've tested the issue is not your mods folder needing an update.
 
Note that the new version of the RAGE Plugin Hook which is required for LSPDFR to work on the new GTA V update is included with the new LSPDFR download.  The RAGE Plugin Hook website has not yet been updated, so you should not download the RAGE Plugin Hook from there but instead use the included version with LSPDFR.
 
Please ensure that you now update your game to the latest version of GTA V before playing this new version of LSPDFR 0.4.9, which you can find as normal on the main LSPDFR page.

as you showed us
 
 
PursuitinProgrss.cs is located in Callouts.
so youre code cannot find PursuitinProgrss.cs.
 
private static void RegisterCallouts() { Functions.RegisterCallout(typeof(PursuitinProgress)); } because of the missing information that PursuitinProgrss.cs is located in Callouts.
so your code should look like this.
private static void RegisterCallouts() { Functions.RegisterCallout(typeof(Callouts.PursuitinProgress)); }  
that fixes my error. i hope it fixes yours

Sadly i don't have the pictures anymore but thos not too bad.
 
It was basically showing the unarmed aiming animation (your character prepares for a fist fight)
 
And the second shows the intimidating animation in front of an suspect. 

Hi everyone,
 
I just thought I would spin up a new forum thread to show off what myself and @Rich have been working on over the past couple of weeks. To help out with developers who would like to get their foot in the door when it comes to writing new LSPDFR callouts, we thought it would be a good idea to write some code for you to cross-reference when writing your own callouts. 
 
Requirements 
You will need the following to get started:
 
Visual Studio (or another IDE) installed. Basic knowledge of the C# language - remember, an LSPDFR callout plugin should not be your first C# project. You should learn C# beforehand.  
Source:
You can view and download the source code: https://github.com/thatmaxplayle/LSPDFRBasePlugin
 
Contributions:
If you're a more experienced developer, please feel free to chip in and drop me a message on Discord (@thatmaxplayle#8811) or via LCPDFR.com to be added to the contributors list. Alternatively, you can just fork the project and submit a PR with your changes. 🙂
 
License:
Make sure to follow the terms of the MIT license which is outlined on the GitHub page. 
 
 
You can use this topic if you're having trouble, of it you have any questions.

Putting some requests here at the request of LMS:
Regarding investigative mode: Add a parameter (or make it a separate function) to Mod.API.Functions.SetPursuitInvestigativeMode to disable the suspect wandering tasks. An example of when this would be useful: I have scenarios where peds are playing animations(working on cars), however investigative mode forces them to stop playing their animations and begin wandering. I attempted to get around this by disabling pursuit AI, however this seems to break investigative mode (the cops confront the suspects, endlessly. LSPD is very persistent!). A function such as Functions.IsPedBeingConfronted(Ped) or Functions.IsPedAboutToBeConfronted(Ped) would also be helpful if the above won't be added, because we could re-enable pursuit AI for that ped when that returns true Maybe add a function to force the outcome of a confrontation with a given suspect? So we could, for example, make it so that whenever the ped is confronted, it will for certain result in them being arrested. Something like Functions.SetConfrontationOutcome(Ped) I love this mode and think it has a lot of potential. It'll allow us to add a lot of realism to our events/callouts!

LSPDFR 0.4.9 introduces very minor API additions.
 
Functions
SetPursuitvestigativeMode GetIlluminatedClothingStyle SetPedArrestIgnoreGroup  
Documentation
LSPD First Response.XML
 
Check the bottom of this thread for new functions introduced in build 8151 (April 27, 2022).

The police partner was a feature back in LCPDFR.
Since then there are mods for LSPDFR like UltimateBackup and others to achiev that.
I don't believe the Management will include this.
 
Not that the Idea is bad but it takes more and complex algorithms to handle the ped properly in different situations.
There is no real motivation to copy existing features of mods in case they work reliable.

I installed some plugins and removed it when my game usually crashes. But it seems the game continuing crash when accept the callout. I also change " Callouts.Multiplier = 250 to 300 " then i change to 250 again, it still crashes. Maybe I will re-install the game, it's been a long time to update everything
 

Okay, I'll re-install your plugin to remove anything that is not original from yours. Thanks for your help

Change the plugin timeout threshold from 10000 to 60000 in the RagePluginHook.ini file and disable Main.PreloadAllModel in GTAV/LSPDFR -> LSPDFR.ini.

A note about the two other API functions in 0.4.9 as well:
 
Calling SetPedArrestIgnoreGroup with true will set the specific Ped to be ingored when LSPDFR checks if they can be stopped by the player when pressing and holding E.  This theoretically should allow for normally restricted peds like firefighters to be stopped (and potentially arrested, ticketed, etc. too).  Note that it only applies to on-foot stops at the moment and not traffic stops or gunpoint arrest takedowns.
 
GetIlluminatedClothingStyle simply retrieves the currently set Illuminted Clothing Style from the Interaction Menu.  We added this to keep consistency of most current settings in the Interaction Menu being gettable through the API, and this can be either:
Off On Pulse Flash  

Expanding a bit on how investigative mode will work from a developer perspective:
 
We expect you to call SetPursuitInvestigativeMode right after creating a chase. You can technically call it while a chase is already running, but that behavior is currently undefined, you have been warned. What this does internally is make all cops use the less aggressive response and approach behavior where they will walk up to a suspect hands on holster and then confront the suspect. The suspect can then surrender or flee. The latter then turns the chase into a traditional pursuit. During investigative mode, the suspect will wander around normally, but can react to the player or other cops and might surrender or flee on sight. Chances here are influenced by whether the player/cop is armed and how heavily currently.
 
Should the suspect get involved into combat or enter a vehicle during investigative mode, the chase will automatically be turned into a traditional pursuit. We have many more plans for this concept including the ability for AI officers to ticket and warn suspects and it is certainly not fully fledged out yet. I thought to throw in the API call anyway to at least familiarize yourself a bit better with the experience and do a few tests here and there. If you have any questions or comments, let me know here.

i know this is probably just me but I kind of want a plugin or script that when you get shot of close to death you fall over and ems and back is call so that the ems can come in revive you and the backup could help in a shoot out. I don't know if this is already a thing or not but it would add  realistic to it all, like i have a mod that when you get shot it wounds you and makes you slow and tells you where you hurt, you can bleed out it would be cool to get the ems involved 

AmbientAICallouts.zip

Yup. Build 7874 now also includes a fix for NPCs not shooting their weapons. So just download the update and you're good to go!

I could not think of a worse way to manage mod updates and downloads than a Discord. It is ultimately a short-lived chat and everything gets lost. The search is terrible. It creates a "silo" similar to Facebook and others where it cannot be indexed via search engines, holding all your data hostage. It cannot be crawled, no one can find anything inside it without being part of it (and even then you cannot find anything due to terrible search). It's almost like an antithesis to the idea of the internet or any community.
 
Would it make sense to supplement an existing community? Perhaps. But keep in mind that the vast majority of users will go there for support, thinking they have this one unique problem no one else has ever had and which is totally a problem with mod X. I understand that people like the fast access, but that is usually at the expense of spam and bugging others, answers the same two questions every five minutes. You are just shifting the burden of research (i.e. a google search for your problem) by posting it in a chat room waiting for someone else to google it for you or answer it. We have tinkered with it for our RDR community and struck a fair balance, I believe. However, our GTA V community is a lot bigger and as already been pointed out would require a ton more moderation work, especially due to how fast paced Discord is. So for the time being, we do not have any immediate plans to create an official public Discord server.