VocalDispatch not working

Officer Revez · January 11, 2019

Hey officers,

I have a problem with VocalDispatch. When I try to say something after pressing R Alt (or D-Pad up) it comes with the message "Didn't copy, please say again".

I have looked in the read me and tried all the voice commands there is, but none of them seem to work. I don't know if it's an issue with my microphone but I don't think so since I did a mic test prior to launching GTA V.

I have also installed the right language pack for windows (en-US).

I'm pretty sure I have tried everything to make it work, but here is my RPH log if it's any help.

RagePluginHook.log

Hisel · January 11, 2019

I won't be much help with this post as I'm struggling with the same issue myself, but I just wanted to let you know that you're not alone. Myself and several others I've talked to, even after having verified our language packs, speech training and microphone testing, simply can't get VocalDispatch to work. It says "didn't copy" before a transmission ever has time to go through, and after three attempts or so just stops responding altogether.

The frustrating thing is I've had VD working on several computers/installs and now, just nothing.

Officer Revez · January 11, 2019

4 hours ago, Will Zoftrak said:

I won't be much help with this post as I'm struggling with the same issue myself, but I just wanted to let you know that you're not alone. Myself and several others I've talked to, even after having verified our language packs, speech training and microphone testing, simply can't get VocalDispatch to work. It says "didn't copy" before a transmission ever has time to go through, and after three attempts or so just stops responding altogether.

The frustrating thing is I've had VD working on several computers/installs and now, just nothing.

Damn, that sucks. Well, good to know i'm not the only one having this issue i guess haha

EntryxTV · February 13, 2019

On 1/11/2019 at 11:51 AM, Officer Revez said:

Hey officers,

I have a problem with VocalDispatch. When I try to say something after pressing R Alt (or D-Pad up) it comes with the message "Didn't copy, please say again".

I have looked in the read me and tried all the voice commands there is, but none of them seem to work. I don't know if it's an issue with my microphone but I don't think so since I did a mic test prior to launching GTA V.

I have also installed the right language pack for windows (en-US).

I'm pretty sure I have tried everything to make it work, but here is my RPH log if it's any help.

RagePluginHook.log

On 1/11/2019 at 1:29 PM, Will Zoftrak said:

I won't be much help with this post as I'm struggling with the same issue myself, but I just wanted to let you know that you're not alone. Myself and several others I've talked to, even after having verified our language packs, speech training and microphone testing, simply can't get VocalDispatch to work. It says "didn't copy" before a transmission ever has time to go through, and after three attempts or so just stops responding altogether.

The frustrating thing is I've had VD working on several computers/installs and now, just nothing.

On 1/11/2019 at 6:15 PM, Officer Revez said:

Damn, that sucks. Well, good to know i'm not the only one having this issue i guess haha

PROBLEM SOLVED; if you guys are still looking for a fix give it another try! Set up your voice recognition with windows and run the voice training, you can set it up by looking up voice recognition on your pc, should have 5 options there including set up voice recognition and train the recognition. Fixed it for me! After searching for a fix, turns out it was right in the readme.txt the whole time... lol!

Hisel · February 13, 2019

10 hours ago, EntryxTV said:

PROBLEM SOLVED; if you guys are still looking for a fix give it another try! Set up your voice recognition with windows and run the voice training, you can set it up by looking up voice recognition on your pc, should have 5 options there including set up voice recognition and train the recognition. Fixed it for me! After searching for a fix, turns out it was right in the readme.txt the whole time... lol!

I tried that so many times it's not funny. Unfortunately that just wasn't a fix for me.