So, after talking to a few people who do LSPDFR and/or GTAV modding, and they suggested that I try to talk to someone who has a good understanding of LSPDFR further under the hood or someone from the dev team. I have done a lot of testing and troubleshooting, even unhashed a ton of audio file names in gtav/x64/police_scanner.rpf and then whatever .awc the wavs are in, and I cannot figure out what is going on, multiple gtav/lspdfr forums and support discords, someone who has been doing a ton of the audio file work for modders to use, and nothing. 
 

dispatch basically doesn’t work, especially with callout packs, every one I install, I will get mission dispatch audio errors for everything besides what is included in the lspdfr and callout pack audio. However, if I extract the .awc container and the hashed wav files within, find the right wav file, and rename it from, for example, the original unhashed file name from gtav police_scanner.rpf was 01_car_unit_type_adam (or very similar) to just ADAM (what the missing file name says in the RPH log) and toss it in the lspdfr/audio/scanner folder, no error, reads it just fine. If I leave the file name what it is within the GTAV police_scanner.rpf files (after unhashing the file name of course) and put it in the scanner folder, nothing, will still get an error. 
 

so it makes me think that there is some issue with lspdfr communicating back to the gtav dispatch audio files, but I don’t know very much about this stuff and the only answers I’ve gotten is people encouraging me to speak to devs or people who really understand under the hood. 

What function/API causes the errors? The LSPDFR scanner plays files from disk and does not interact with the GTA V scanner RPF files at all. It might also be helpful to include a log with a few of these errors.

2 minutes ago, LMS said:

What function/API causes the errors? The LSPDFR scanner plays files from disk and does not interact with the GTA V scanner RPF files at all. It might also be helpful to include a log with a few of these errors.

so this is what i will get from any callout pack, and the lspdfr callouts seem to have less variety. also, even with the lspdfr scanner audio, in the streets folder, i had to change the names of a bunch of them and remove the "01's" and change STREET to ST, its just so strange. And i believe the last time i set it up a couple years ago i had this same sort of situation but just didnt dig into it at all and wasnt playing anymore. already tried a completely fresh install, done the normal troubleshooting ive learned over the years with lspdfr, im just totally at a loss on this one. 

RagePluginHook136DispatchToAdd.log

I see what you mean regarding the weird audio errors. It seems that, at least according to your log, they mostly happen when playing callouts from "Section136Callouts" so perhaps reaching out to its developer might help. It is possible that the audio API is not being used properly.

this is across all callouts packs. I have tried like 8 of them, super recent ones, older ones, separately, only one at a time, etc. And even vanilla lspdfr, while it doesnt throw errors, seems much more simple and less diverse, like, only one "attention units" dispatch wav will play, even if i do different callouts over and over, it wont like, cycle between one of the 4. And i also had to edit the street names to not get errors. taking out 01's and changing STREET to ST. its just so strange, ive been around here for a little while and ive only seen this issue a handful of times over the years and never any solution 

 

6 minutes ago, LMS said:

I see what you mean regarding the weird audio errors. It seems that, at least according to your log, they mostly happen when playing callouts from "Section136Callouts" so perhaps reaching out to its developer might help. It is possible that the audio API is not being used properly.

like, ive gone as far as brute forcing hashed file names to make the process of manually adding files over from police_scanner.rpf lol, thats how much ive tried to fix this and look into it. Talked to the callout guy for this pack in the log, he said he had no idea what is going on and he hasnt heard of any similar issues, if it was a couple callout packs, ive been around long enough to know that sometimes things just dont play nice for some weird reason, but, its every pack, and its a problem ive seen here and there in my searches about it, but never any solution. 

Edited December 25, 20223 yr by StuckpigINC
more info

I cannot offer much help for third party callout packs as I cannot see how they call the API. However, if you can provide me with a log where LSPDFR audio errors before you fix the files (just rename your fixed audio folder and put in the old one), perhaps I can see something there.

12 minutes ago, LMS said:

I cannot offer much help for third party callout packs as I cannot see how they call the API. However, if you can provide me with a log where LSPDFR audio errors before you fix the files (just rename your fixed audio folder and put in the old one), perhaps I can see something there.

Sounds good, I appreciate your time. Basically I had call out guys telling me to go to devs so, I guess i can say that has happened now, and that they told me to go back to them lol. its just so strange, its like audio files are missing. and needing to rename the street names is really strange to me, changing STREET to ST and DRIVE to DR and so on. Its like every callout pack didnt come with audio files, but the ones that come with them are the only audio files that actually work with dispatch besides a couple words here and there. 

 

i guess at least i have unhashed police dispatch file names and it will make adding them to the lspdfr scanner folder a little easier lol. Thanks again for your insight, that lets me know to start looking in a direction other than there being some sort of "communication" issue with lspdfr calling back to the policescanner.rpf, resolving the hash, and then letting lspdfr "borrow" the wav or the .awc. or some weird process like that. At this point I just want to figure out the problem to be able to possibly help someone in the future, even though this isnt super common. Ill come back here and post a more useful log in terms of LSPDFR itself when i start testing that side again in the next day or two. 

 

thanks again and enjoy your holiday