I have implemented an alternative to the default "apprehend wanted suspect" callout, in native lspd.
The implementation is in a plugin, not a callout, it is a substitude-callout!
I need to emulate the default feature of not getting new callouts during the substitude-callout-action, and i have found information about blocking dispatch with:
NativeFunction.Natives.SetAudioFlag<bool>("PoliceScannerDisabled", true);
But that is ignored. Dispatch continue to make callouts and the mini-map toggles up/down accordingly. especially the map-toggling from detailed to oversight is very disturbing for the substitude-callout
Am i using SetAudioFlag wrong, or is there a better way to stop dispatch to make new callout untill it again is wanted?

 

----Solution:---------------------------------
Today i was reading up on a subject and incidently this came up:
Functions.SetPlayerAvailableForCalls(boolean);
That function works exactly like i need it to.
As long as the flag is false there are no callouts from dispatch
 

 

Edited November 17, 20232 yr by GTAbear
solution

The callouts are dispatched by LSPDFR, not by the game. Hence calling any natives will not affect them. The native you are using is also only related to game audio. Can you describe a bit more what you are trying to achieve and why you are doing it outside of the LSPDFR callout manager?

2 hours ago, LMS said:

The callouts are dispatched by LSPDFR, not by the game

Ohh- That explains it

 

2 hours ago, LMS said:

Can you describe a bit more what you are trying to achieve

I dislike the default Apprehend wanted suspect-callout. It is predictable, and the gameplay is low. So in my utility-plugin, i added a highly randomized 'replacement' that i then would start when dispatch made that Apprehend wanted suspect -Expressed shorter: I attempted to make something that is unsuitable for a plugin.
The way to do this would be to make a proper call-out, and not what i have done. In that process i also managed to misunderstand the functionality of SetAudioFlag
Thank you for that information! It looks like dispatching cant be disabled, in a utility plugin.