StuckpigINC

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

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

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

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.

install heap adjuster and packfile limit adjuster. from the little i can see, it seems like it might not have enough memory to access for some reason possibly.

Unfortunatly my issue isn't an issue of forgetting to installing audio from call out packs or anything like that, the issue is that after a lot of testing it seems like for some reason, LSPDFR isn't able to access the audio files while using callouts, only audio provided. For example, a callout pack has a config file where you can specify a unit number and "call sign" which I left as default, 11 Adam. The callout will not be able to find any audio that is not within the lspdfr scanner audio folder, or within the callout packs own audio. However, if I go to POLICE_SCANNER.rpf in the GTAV audio folder, find the correct .wav container, and then find the correct audio file for say ADAM (the individual files in the wav container are almost all hashed, so I either have to manually check, or find the hashed value of the audio file via a document I found with a list of the containers, what each .wav says, and the hash. Then if I extract the wav file, rename it to what audio file is shown in the RPH log, and put it in a folder with the same name as the wav container folder (in this case 01_car_code_unit_type, put the wav file named ADAM in, and put that in lspdfr scanner audio folder, absolutely no problem. Ive also had to edit the names of a lot of the audio files in the lspdfr scanner audio in the streets folder, file names were not what callouts were calling for (like no "01" after this certain street, change STREET at the end of the file names to ST, etc.) I just have no idea what is causing this problem, and Im not exactly new with lspdfr and its...quirks, so I've done all the normal stuff already, and checked and done that stuff multiple times, so I'm just completely at a loss and trying to find anyone who understands at least a little about under the hood of lspdfr so to speak in terms of the process of calling back. Like, is there a communication problem between callouts and lspdfr, is there an issue with lspdfr for some reason not being able to unhash the file names in the GTAV police scanner folder, etc.

I’ve been trying to solve an issue with a lot of missing dispatch audio and I’m trying to find out if LSPDFR calls back to the original gtav POLICE_SCANNER.rpf files sometimes. Let’s say I get an error for the audio file that says ADAM, if I look at my master list, find the one that says ADAM in the police scanner folder, if I extract the wav container to the lspdfr/audio/scanner (in this case 01_car_unit_type.awc) and find the hashed file that says ADAM in said container, if I rename the hash file to whatever RPH threw an error for, then I no longer get an error for mission audio for the word adam from dispatch. I’ve looked all over for answers, talked to multiple people, and no one knows the problem. If someone knows whether lspdfr calls back to gtav for scanner audio sometimes, and has gtav decrypt the hash, then it might be easier for me to figure this out because at least I would have the cause sort of narrowed down

Attach a log, this likely is not a bug with lspdfr and more of an issue with conflicting mods, memory leak, etc.

So I just got back into LSPDFR after a year or two, pretty experienced with troubleshooting usually, but not much experience with the audio files, if callouts are calling for just files from the lspdfr scanner files or if they are also calling from the gtav police scanner files. Ill get like half of dispatch on calls, even things like 'ADAM" and some street names, (even after installing the street names mod,) shit, I even get an error for "11." Heres an example log, basically just switch out the call out pack and a phrase/word or two Anyone have any idea whats going on here and how to fix it? For some reason my brain is hyper focusing on trying to fix it and its driving me nuts lol Also, I'm looking at my POLICE_SCANNER.rpf file in GTAV root >x64>audio>sfx and it looks like that's probably all good if that matters, I have a doc that has all the file names and then what is actually said and spot checking it, it looked like its probably all there. Worried if I do a fresh install that I'll end up in the same boat because I have no idea whats going on. Granted full control to the GTAV root folder and checked to make sure the audio folder updated to full control RagePluginHook.log