Problems with VoiceAttack plugin

[hoksilato2]

EDDI version in which issue found

EDDI 3.3.4-rc3 VA 1.7.3

Steps to reproduce

1. Open VoiceAttack with configured profile
2. Execute the game

Expected

Event ((EDDI commander continued)) should be work at loading screen. Other events like music, docked, undocked should be work too.

Observed

When I use standalone EDDI and start it before game, Events work ok.

Investigation

I fixed the problem using a watcher system on VoiceAttack. Now I can deside if open EliteDangerous with voice command (and then VA switch the elite profile) or if I execute the game, VA switch the profile automatically. but, if I load the VA profile before open the game, all events not work. This is new, i don't know if its a bug.

[hoksilato2]

Log when I open VoiceAttack first than game:

[hoksilato2]

I allways start voiceattack first than game, but if I start voiceattack after game events work ok. the log with events ok:

[hoksilato2]

If I close VoiceAttack in the middle of the game and then open again, events not work again.

Here the log:

2019-02-01T18:16:53 [Info] EDDI:.ctor EDDI 3.3.4-rc3 starting 2019-02-01T18:16:55 [Info] EDDI:.ctor On live 2019-02-01T18:16:56 [Info] CargoMonitor:initializeCargoMonitor Initialised Cargo monitor 1.0.0 2019-02-01T18:16:56 [Info] MaterialMonitor:.ctor Initialised Material monitor 1.0.0 2019-02-01T18:16:56 [Info] MissionMonitor:initializeMissionMonitor Initialised Mission monitor 1.0.0 2019-02-01T18:16:57 [Info] ShipMonitor:.ctor Initialised Ship Monitor 1.0.0 2019-02-01T18:16:57 [Info] StatusMonitor:.ctor Initialised Status monitor 1.0.0 2019-02-01T18:16:57 [Info] EDDNResponder:.ctor Initialised EDDN responder 1.0.0 2019-02-01T18:16:57 [Info] EDSMResponder:.ctor Initialised EDSM responder 1.0.0 2019-02-01T18:16:57 [Info] SpeechResponder:.ctor Initialised Speech responder 1.0.0 2019-02-01T18:16:57 [Info] VoiceAttackResponder:.ctor Started VoiceAttack responder 2019-02-01T18:16:59 [Info] EDDI:.ctor EDDI access to the companion app is enabled 2019-02-01T18:16:59 [Info] StarMapService:.ctor EDDI access to EDSM is enabled 2019-02-01T18:16:59 [Info] EDDI:.ctor EDDI 3.3.4-rc3 initialised 2019-02-01T18:16:59 [Info] EDDI:Start Starting keepalive for EDDP monitor 2019-02-01T18:16:59 [Warning] EDDI:keepAlive EDDP monitor stopping after too many failures 2019-02-01T18:16:59 [Info] EDDI:Start Starting keepalive for Journal monitor 2019-02-01T18:16:59 [Warning] EDDI:keepAlive Journal monitor stopping after too many failures 2019-02-01T18:16:59 [Info] EDDI:Start Starting keepalive for Mission monitor 2019-02-01T18:16:59 [Warning] EDDI:keepAlive Mission monitor stopping after too many failures 2019-02-01T18:16:59 [Info] EDDI:Start Starting keepalive for Status monitor 2019-02-01T18:16:59 [Warning] EDDI:keepAlive Status monitor stopping after too many failures 2019-02-01T18:16:59 [Info] EDDI:Start Started EDDN responder 2019-02-01T18:16:59 [Info] StarMapService:.ctor EDDI access to EDSM is enabled 2019-02-01T18:16:59 [Info] EDDI:Start Started EDSM responder 2019-02-01T18:16:59 [Info] DataProviderService:syncFromStarMapService Syncing from EDSM 2019-02-01T18:16:59 [Info] EDDI:Start Started Speech responder 2019-02-01T18:16:59 [Info] EDDI:Start Started VoiceAttack responder 2019-02-01T18:17:02 [Info] DataProviderService:syncFromStarMapService EDSM sync completed 2019-02-01T18:17:17 [Info] VoiceAttackPlugin:VA_Init1 EDDI VoiceAttack plugin initialization complete 2019-02-01T18:20:55 [Info] StarMapService:.ctor EDDI access to EDSM is enabled 2019-02-01T18:20:55 [Info] StarMapService:.ctor EDDI access to EDSM is enabled

[Tkael]

Unfortunately, this isn't a problem with just VoiceAttack. It is a problem with EDDI versions RC1 and RC3 that can affect both VoiceAttack and stadalone installations. If this is a consistent problem, please downgrade to version 3.3.3 until the next release. I've submitted a PR to address this issue.

[hoksilato2]

I don't know why, but in 3.3.6 occurs again. No errors on EDDI's log, but EDDI's not work on 3.3.6 when I use VoiceAttack 1.7.3

Causes:

Events like ((EDDI music)), ((EDDI undocked)), ((EDDI docked)), ((EDDI location)), etc. not work Ship monitor causes freeze EDDI process. Any event on speech responder works. high CPU usage of VoiceAttack process.

If I wait a several minutes (maybe 15min) sometimes everything work again, but I need restart commander session.

If I use EDDI without VoiceAttack, everything works without any problem.

When everything works ok, If I try go to ship monitor again, the problem shows again. Only using VoiceAttack plugin.

[Tkael]

We're aware of the problem with accessing the ship monitor while VoiceAttack is running. The new alpha build that @richardbuckle shared for translators should be better, and even more changes are coming to improve this area further.