turbofandude

You need to send me the RagePluginHook.log file.

Just drop everything in the plugins\LSPDFR folder - we'll get that fixed.

Definitely a must have. It makes taking suspects to jail simple, whether you call for transport or take them yourself. The tow truck works well, but my favorite feature is the ability to force it to spawn nearby if it gets stuck somewhere or can't reach you (an issue just about ALL GTA V AI drivers have at one point or another). On the developer side, the API offered plugs in nice when needed.

The readme.pdf file included should answer your questions - is that file working for you? (I've had some reports of it being broken by default.)

Did you read the readme? It'll probably answer your question. :)

The Speech Recognition APIs are stupid when it comes to "cancelling". If I make it push to talk, you'd have to hold the button down until after you've completely finished talking and VocalDispatch responded (otherwise, it's detected as a "cancel" and I get nothing from the API, even though you said the whole sentence). That said, it shouldn't crashing for any reason. I'll look into it.

Very odd - this line: "System.InvalidOperationException: The real-time audio device stopped returning expected data". Do you have your default mic setup properly in Windows?

Yes, if you change the script to listen for German words, it will. You can also set the "Locale" in the ini file to "en-US" and install the English language pack for Windows, then speak in English (we'll be explaining this better in future versions).

Yes, for now, they all go in plugins\lspdfr. We'll be looking into why the PFD is broken sometimes.

The VocalDispatch folder goes in Plugins\LSPDFR\.

Sounds like a mic recognition issue @Snowmanizreal - is your mic the default mic?

The issue of translations is my fault for not explaining - if you're going to change the language, you'll need to edit the script.xml file to contain words in that language as well (there are no automatic translations). The "Locale" setting is there for those who are so inclined to translate the script. As well, I figured I'd say this, the default key is Right Alt - the readme says this. I've already had several questions asked that could be solved by properly reading the readme.pdf file included. PLEASE start there before asking questions or becoming upset.

I'm not seeing any attempt to actually speak in there (no keypress/joystick press detection). Are you hitting Right Alt before talking? Try changing that key to see if something else works better. As well, ensure your mic is set to the default recording device in Windows.

What does your log say now?

Are you pausing for a noticeable amount of time between words?

Awesome stuff! Very glad to hear it.

These are both things I'm working on. Rather than reducing keyword count, I'm trying to add in words it commonly mishears instead to help. For now, I don't know. The code is forcing it to English, so I have a feeling that, without that pack, it's not going to initialize.

It does this - it's something I'll have to fix with some AI logic.

Not yet, but I'm not against adding it in the future. :)

Everybody, I've uploaded 1.2.0.0 and added a few things, once of which is changing to the new key detection system. Please let me know how it's working! Thank you! I really appreciate you taking the time to help out here.

Whenever my Dropbox decides to unbreak itself, I'll be working on 1.1.1.0 - I'm thinking it'll likely fix this.

To everyone, I'm going to be using a different (hopefully better) function to detect key presses in the next version as well as adding controller support. So, to any of you having the issue where it's just ignoring you, please bare with me until the next version (1.1.1.0).