Release EDDI Scripts and EDDI enabled VA Commands Thread

Also, for those of you who have been asking about VoiceAttack version 2...

EDDI is currently incompatible with VoiceAttack version 2. I have a copy of VoiceAttack version 2 and will begin to explore development on that updated platform. Support for VoiceAttack version 1 on new EDDI releases will likely sunset once that update is completed. In the meantime, EDDI is still compatible with legacy VoiceAttack version 1 so I don't feel like there is a need for a great rush to switch to version 2.

Notes: Switching to version 2 is likely to require a framework upgrade from .Net Framework 4.8 to .Net 8. It is also likely to cause EDDI to run in 64 bit mode by default, meaning that older 32 bit-only voices may stop working with EDDI. There may be software library dependency issues or isolation issues which could require significant code revisions.

Per VoiceAttack's developer:
VoiceAttack v1 can still be accessed - go to voiceattack.com/downloads.
If you are a VoiceAttack v2 user, you will be able to install v1.
For standalone (website) version users, your registration key will work with both versions.
For Steam users, make sure to download the 'Steam Legacy Edition' version (note that you will need to be logged into Steam to validate that version).

Data files are stored separately so you should be able to have both versions installed simultaneously without issue.
 
Thing seem much improved with 4.1.1; thank you.

For those of you who had trouble with the auto-upgrade to version 4.1.1, that issue should now be resolved. o7 commanders.

Ha, yes when I tried to update within EDDI it complained about it being a 16-bit application or something like that. o7
 
I don't know what problem you have with EDDI. The update worked for me. If the update does not work within EDDI
(@T'kael reported this on github), then uninstall it and reinstall it.
I've been using it since 2015 and there have always been issues that have been identified and fixed by the team.
 
I don't know what problem you have with EDDI. The update worked for me. If the update does not work within EDDI
(@T'kael reported this on github), then uninstall it and reinstall it.
I've been using it since 2015 and there have always been issues that have been identified and fixed by the team.
If that was directed at me, read more closely what I wrote. I clearly got it working since I thanked T'kael for the update and said it had improved things.

I encountered the issue that T'kael resolved before he resolved it. I did in fact work around that issue by using the full installer.

If your comment was directed at someone else, you have my apology.
 
I'm sorry, I've overlooked something.
I probably also misinterpreted your text. I thought you were making fun of EDDI. And since my mood wasn't exactly good either (everything is fine again now :) ),
my comment was way over the top. Sorry for that. 😟
 
Back
Top Bottom