doublehook

¡Genial! Espero tus comentarios sobre las pruebas. ¡Saludos!

That would be great, and thank you so much for doing that. I hit you up at the email address you provided on my current form, so you can get my Gmail address from there.

Sorry for the trouble you're experiencing. Are you on the latest GTA version and RPH? If you could, can you hit up my Google form (link below) so I can reach out to you directly through email. Thanks in advance. https://forms.gle/YYqKcpBFsHSxuN5w5 I'm so glad you're enjoying it. Thanks for sharing the log snippet of your error. This all I needed. Appreciate you. Thanks for confirming this!

I'd really appreciate that. I'm so glad you don't have to rage about your new headset now! Glad you figured it out. Cheers!

Thanks. That's exactly what I was needing to know. I want to investigate this issue for any peeps who won't be able to use en-US as an alternative in the INI. Appreciate you!

I'm glad you got it working, but I'm concerned that didn't accept en-GB in the INI file. I need to investigate this further. At your convenience, I'd still appreciate you dropping me a bug report so I can get the exact errors from your rph log (in text). For the sound issue, no, there should definitely not be any crackle when you hit the keybind. You're the first person to report that issue. I would definitely check some other situations to see if you have any audio issues, and rage if you do! YES!!! I'm so glad to hear!! I can't wait for you to test it out later! I truly hope you enjoy it! Just curious, are you en-GB?

I'm sorry to hear it's not working for you. You mention "Grammar Police". Is that in the error? If you could do me a favor, can you hit up my Google form and leave your email address, so I can reach out to you directly through email? I'd like to get a copy of your rph log and examine the error. Thanks in advance. https://forms.gle/YYqKcpBFsHSxuN5w5

Thanks so much! I couldn't agree more with your approach. I'm glad you're having a good experience with tailoring the questions to match your style. You can definitely go down the rabbit hole customizing the questions, LOL. It's almost like trying to create scenes from a movie and coming up with dialog (including variations of the same questions) that will allow you to go back and forth fluidly, anticipating the onscreen responses, and having questions to fire back to keep it going. I can even see folks creating separate XML files and interchanging them based on the kind of interaction they want to have that day. I really appreciate your support and kind words. I look forward to your review!

I'd lke to add -- both files must be in the directory for the plugin to work properly, but the Responses.XML only has to have the unrecognized default phrases at the top in between the <DefaultUnrecognizedResponses> brackets, along with the <Command> and </Commands> closing brackets. I put an example of what this looks like in the XML section at the top of my page. You can delete all of the questions and responses if you don't want to use any of mine, but the <DefaultUnrecognizedResponses> portion has to stay in the "Responses.XML" file for the default responses to trigger.

Yes, it's the same way for the default Responses.XML. You can customize completely, but you have to maintain the tags/brackets for everything to work properly (just like you would for STP XMLs in the past). The UserResponses XML will always take priority, so if you have the same questions in both files, but different responses, the plugin will always show the ones from the UserResponses.XML over the default responses.xml. I wouldn't worry about messing it up. You can always just pull it from the download again and fix whatever you need to. I hope this helps!

Estoy subiendo una nueva versión que permite configurar el idioma en el archivo INI. Pruébala y avísame si funciona. Pronto estará disponible en el sitio para su descarga.

Si te animas, ¿podrías rellenar el formulario de soporte de Google que está en mi página principal de lcpdfr y dejar tu correo electrónico? No tengo ningún beta tester y me encantaría que me permitieras trabajar contigo sin conexión para probar algunas correcciones del idioma. Avísame y gracias. https://forms.gle/YYqKcpBFsHSxuN5w5

Lamento saber que estás recibiendo errores. ¿Los errores que recibes con la nueva versión se deben a la traducción del XML al español? ¿Te ocurren los mismos errores con el XML en inglés? Podría ser un problema de codificación, que intentaré resolver, espero que hoy mismo. Avísame. Gracias. ¡Muchas gracias por hacerlo! ¡Lo aprecio mucho! Estoy seguro de que la comunidad agradecería traducciones a otros idiomas. Estoy trabajando arduamente para que el plugin funcione con todos los idiomas, así que agradezco su paciencia ante cualquier problema que puedan tener. Hey there. I'm working on an update to try and address this issue. There's a few folks experiencing this error and I will do my best to get it resolved quickly. Just for bug tracking purposes, what language are you set up for? EN-US? Thanks in advance. That's a great suggestion! I will see about working that into the next update. I don't know if I'll be able to have it ready for the update coming out today, but I'll work hard to figure something out for an update early this coming week. LOL! I'm so glad you're up and running now! I hope you have a great time using it! Cheers!

I'm sorry for the issues you're experiencing. I'll definitely look into adding this option in my next update, which comes out tomorrow. I got you. Sorry for the issues you're experiencing. I'll definitely look into adding this option in my next update, which comes out tomorrow.

Now that you can modify everything through XML customization, you can create your own questions and responses in Spanish and it should work. The base coding is not language specific. If it doesn't work for you after customization, let me know and I'll make some changes.

I hear you!! I don't like them either. That's part of the reason why I didn't use the question the ped section. My plugin questions weren't that great either, lol, but I had fun creating and testing them nonetheless.

I just finished re-coding to add this ability into the XML customization. It's already good to go. I even coded it allow for multiple default responses if you want to use more than one. You'll be able to use whatever default response, or responses, that you want! I'll provide this feature in the next update tomorrow!

I just finished re-coding to add this ability into the XML customization. It's already good to go! I even coded it to allow for multiple default responses, if one chooses to use more than one. I'll provide this feature in the next update tomorrow!

Thanks man! Please do! I would love to see it. I just uploaded a video on YT asking people to post their own videos so I can finally see ones that are not my own, LOL.

Wise suggestion. I'll start working on that!

That's a great idea! I'm happy to replace the default response (which can be both actually and will it just randomly choose one of them) if the community would like that. Would you guys prefer this type of response for unrecognized questions? Let me know and I'll add it in! Maybe I can even upload different versions if some folks prefer "Yes sir" or some folks prefer both "Sorry" and "Pardon?". I'm open. Oh, I didn't even see that! Cool! It's been waiting for approval for a couple of hours. I'm glad it's live now! Let me know if the XML file gives you any trouble. I don't have any testers, so it's just been me testing the new version.

Thanks man! I've already uploaded the new version to the site, but it hasn't been approved yet. As soon as LCPDFR approves the updated files, it will be live!

Getting the default "yes sir" response tells me it's enabled properly, so that's a good thing. Another community member reported something similar and they ended up going into their speech recognition properties and changing it to US. Once he restarted his PC, it ended up working. I don't know if this helps, but it's worth a look. Also, check your in-game mic settings and make sure they're correct, and if so, maybe disable and re-enable your mic in GTA and try again. Report back and let me know if you had any success.

Hey there. Yes, I did do some research on the MSP (Microsoft Speech Platform). I had already fully coded NPCI using WSR when I first learned MS was discontinuing it. I did try a few re-code tests with MSP, but was unsuccessful in getting it to work. I didn't spend a lot of time on it though. I'll be revisiting it again. Since I decided to release the code as open source on GitHub, I'm confident it will make the transition with the community's help. There are some AMAZING coders in the LSPDFR community!