-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Voice Attack not using EDDI Plug-in #1613
Comments
There isn't enough information here for us to do anything or reach any conclusions about what is wrong.
|
Per #1612, you were having some problems with installing. Please also verify whether you were able to install correctly or whether errors were encountered during installation? |
EDDI is installed in the correct folder. I'm including the log file
you requested
Thanks for helping.
Mike
…On Sun, Dec 1, 2019 at 8:01 AM Brian Wilson ***@***.***> wrote:
Per #1612 <#1612>, you were having
some problems with installing. Please also verify whether you were able to
install correctly or whether errors were encountered during installation?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1613?email_source=notifications&email_token=AAPQQSVBZRIE5IZYZD6Z7ULQWOYQ3A5CNFSM4JTLJFQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFRIOXA#issuecomment-560105308>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPQQSUU4NL7RYJ4JGZLFLDQWOYQ3ANCNFSM4JTLJFQQ>
.
|
There is no log file attached yet? |
Attaching ...
…On Sun, Dec 1, 2019 at 3:39 PM Brian Wilson ***@***.***> wrote:
There is no log file attached yet?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1613?email_source=notifications&email_token=AAPQQSVJS42QNUEXEDRBDV3QWQOGTA5CNFSM4JTLJFQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFRU46A#issuecomment-560156280>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPQQSWPSIFNMGZTZN6FFOTQWQOGTANCNFSM4JTLJFQQ>
.
|
Not attached. |
Last attempt. Don't know why you're not getting it
Thanks
…On Sun, Dec 1, 2019 at 5:14 PM Brian Wilson ***@***.***> wrote:
Not attached.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1613?email_source=notifications&email_token=AAPQQSTVFD7J7PHSGYMJ5GTQWQZLXA5CNFSM4JTLJFQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFRXLWQ#issuecomment-560166362>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPQQSROYZDD3DMR2SGGER3QWQZLXANCNFSM4JTLJFQQ>
.
|
Still no. Please zip the file them drag it into the message box for your response. |
Sorry about the mess up. Was sending via my email... not here. Thanks |
Got it. This log appears to have originated from running EDDI in standalone mode. Please confirm whether this log was generated from VoiceAttack or from running EDDI in standalone mode? |
To be totally honest I didn't know there was a difference. My startup procedure is: EDDI (wait until loads), VoiceAttack (wait again), then Elite Dangerous. If I need to do something different please let me know. When you say Standalone I would assume I'm running it that way, yes. I don't know how to get VoiceAttack to initialize EDDI. |
Just run VA, don't run EDDI first. If EDDI is installed in the correct place, then it will load as a plugin for VA automatically. If you run EDDI first, and it's all installed correctly, then a warning should pop up when you run VA afterwards. I just tried it, and after the popup, VA still loads and has EDDI as a plugin in the plugin manager. |
If the plugin isn't being detected by VoiceAttack, there's a good chance that EDDI isn't installed in the correct directory to be run as a plugin. What directory is EDDI installed to? This would be the directory that contains EDDI.exe. (Feel free to replace your Windows user name if that is part of the path). It should be something like |
This is probably a dumb question, but you do have VoiceAttack actually installed in the \Program Files (x86)\VoiceAttack\ folder, don't you? I mean, EDDI looks installed in the correct place, but if VA is somewhere other than the above.... |
Is the HCS plugin (and profile) a recent update? |
@Hoodathunk all is current. I try to keep things updated as much as possible. |
How recent? As of last Saturday? |
Just so I'm clear on this: Are you saying that you had VoiceAttack installed under Steam, and not in the \Program Files (x86)\Voice Attack\ folder? Was it installed somewhere in your Steam folder then? Have you copied Voice Attack into the \Program Files (x86)\Voice Attack\ folder, or did you copy EDDI into the VA folder under Steam? |
Yes... under Steam. I copied the EDDI folder structure to the Steam\steamapps\common\VoiceAttack\Apps\ folder. EDDI 3.5.1 initializes when VA is executed and is now listed as a plugin in the Plugin Manager. |
Last question. Is there a way to adjust the volume output while using EDDI through VA? It seems VERY loud. |
The default EDDI VoiceAttack profile has a command '[Configure; Initialize; Minimize; Maximize; Restore; Close; Open] EDDI'. Use this to open the EDDI config, just as if you had run EDDI as standalone. Then, under the 'Text-to-Speech' tab, there is a volume slider to adjust. |
If you load the EDDI.vap profile, you'll be able to use the command "open EDDI" or the command "configure EDDI" to open EDDI's UI. Once you've done so, volume settings may be found in the Text-to-speech tab. |
Do I import EDDI.vap into Singularity? I just don't want to get it wrong and have to ask to help fix my screw-up :) Just preventative maintenance. |
Disregard my previous question. I've linked the EDDI.vap into Singularity. Everything is working as it should. Thanks to Everyone for their help. VERY much appreciated. |
Closing as resolved. |
EDDI version in which issue is found
3.5.1
VoiceAttack version in which issue is found (as applicable)
1.8.2
Steps to reproduce
Expected
Was hoping to see EDDI Plug-in Initialized... but this didn't happen.
Observed
[Describe what happened instead]
Investigation
[Any investigation you have done, regression tests against earlier versions, etc]
The text was updated successfully, but these errors were encountered: