EDCD / EDDI

Companion application for Elite Dangerous
Other
444 stars 81 forks source link

Never get "Plugin EDDI 3.4.2 initialized" in VA Startup #1691

Closed incryptx closed 4 years ago

incryptx commented 4 years ago

V3.5.2

First Question: I have EDDI running successfully and it gives me information in the game as well as responds to questions. I have EDDI configured correctly and in VA's "Enable Plugins", I see the EDDI plugin with a version number "EDDI 3.5.2 (v4EDDIVoiceAttackResponder.dll) with a check mark in the box.

But one thing I never see, according to your install instructions, is when VA starts up, I never get the "Plugin EDDI 3.4.1 initialized" dialog in VA's screen.

Now, I don't have VA installed at the default location, i.e. in "Program Files(x86)\VoiceAttack" as I use the Steam Version.

I have it installed at "D:\SteamLibrary\steamapps\common\VoiceAttack" with EDDI installed at "D:\SteamLibrary\steamapps\common\VoiceAttack\Apps\EDDI"

I get no errors, EDDI seems to run fine from there, but I don't get the "Plugin EDDI 3.4.2 initialized" dialog in VA startup, but I also get no errors in VA startup.

Second question: Do I need to "import" into VA as a profile, the EDDI.vap file, or is it sufficient to just enable the plugin for EDDI in VA's plugin manager?

Log File: 2020-01-21T04:32:16 [Info] VoiceAttackPlugin:VA_Init1 Initialising EDDI VoiceAttack plugin 2020-01-21T04:32:16 [Info] EDDI:.ctor EDDI 3.5.2 starting 2020-01-21T04:32:18 [Info] EDDI:.ctor On live 2020-01-21T04:32:18 [Info] InaraService:.ctor Configuring EDDI access to Inara profile data 2020-01-21T04:32:18 [Info] CargoMonitor:initializeCargoMonitor Initialized Cargo monitor 2020-01-21T04:32:18 [Info] CrimeMonitor:initializeCrimeMonitor Initialized Crime monitor 2020-01-21T04:32:18 [Info] StarSystemSqLiteRepository:CreateOrUpdateDatabase Starsystem repository schema is version 2 2020-01-21T04:32:18 [Info] EDDNResponder:.ctor Initialized EDDN responder 2020-01-21T04:32:18 [Info] EDSMResponder:.ctor Initialized EDSM responder 2020-01-21T04:32:18 [Info] InaraResponder:.ctor Initialized Inara Responder 2020-01-21T04:32:18 [Info] MaterialMonitor:.ctor Initialized Material monitor 2020-01-21T04:32:18 [Info] MissionMonitor:initializeMissionMonitor Initialized Mission monitor 2020-01-21T04:32:19 [Info] SpeechResponder:.ctor Initialized Speech responder 2020-01-21T04:32:19 [Info] VoiceAttackResponder:.ctor Started VoiceAttack responder 2020-01-21T04:32:19 [Info] ShipMonitor:.ctor Initialized Ship Monitor 2020-01-21T04:32:19 [Info] StatusMonitor:.ctor Initialized Status monitor 2020-01-21T04:32:20 [Info] EDDI:.ctor EDDI 3.5.2 initialised 2020-01-21T04:32:20 [Info] EDDI:Start Starting keepalive for EDDP monitor 2020-01-21T04:32:20 [Info] EDDI:Start Starting keepalive for Journal monitor 2020-01-21T04:32:20 [Info] EDDI:keepAlive Starting EDDP monitor (0) 2020-01-21T04:32:20 [Info] EDDI:keepAlive Starting Journal monitor (0) 2020-01-21T04:32:20 [Info] EDDI:Start Starting keepalive for Mission monitor 2020-01-21T04:32:20 [Info] EDDI:keepAlive Starting Mission monitor (0) 2020-01-21T04:32:20 [Info] EDDI:Start Starting keepalive for Status monitor 2020-01-21T04:32:20 [Info] EDDI:keepAlive Starting Status monitor (0) 2020-01-21T04:32:20 [Info] EDDI:Start Started EDDN responder 2020-01-21T04:32:20 [Info] EDDI:Start Started EDSM responder 2020-01-21T04:32:20 [Info] EDDI:Start Started Inara Responder 2020-01-21T04:32:20 [Info] EDDI:Start Started Speech responder 2020-01-21T04:32:20 [Info] EDDI:Start Started VoiceAttack responder 2020-01-21T04:32:20 [Info] EDDI:eventFileHeader On live 2020-01-21T04:32:20 [Info] VoiceAttackPlugin:VA_Init1 EDDI VoiceAttack plugin initialization complete 2020-01-21T04:32:21 [Info] EDDI:eventLocation Location StarSystem: Shinrarta Dezhra 2020-01-21T04:32:21 [Info] EDDI:.ctor EDDI access to the Frontier API is enabled. 2020-01-21T04:32:21 [Info] DataProviderService:syncFromStarMapService EDSM sync completed 2020-01-21T04:32:25 [Info] EDDI:Reload EDDI 3.5.2 module Inara responder reloaded 2020-01-21T04:40:37 [Info] VoiceAttackPlugin:VA_Exit1 EDDI VoiceAttack plugin exiting 2020-01-21T04:40:38 [Info] EDDI:Stop EDDI 3.5.2 stopped

Tkael commented 4 years ago

Odd, I see

Plugin 'EDDI 3.5.3-b1' initialized.
The EDDI plugin is fully operational.

The log file seems to show EDDI is running just fine.

Note that "Plugin 'EDDI 3.5.3-b1' initialized." is written by VoiceAttack while "The EDDI plugin is fully operational." is written by the EDDI plugin.

Loading EDDI.vap is not required for interacting with the plugin but it is recommended since it includes example plugin commands which are designed to help you interact with EDDI in VoiceAttack. What I like to do is to add EDDI.vap as a reference / child profile for whatever my primary profile is.

incryptx commented 4 years ago

I'm not clear on what your saying?

Where in the log does it refer to "EDDI 3.5.3-b1 initialized"?

I see in the logs references to EDDI 3.5.2

I agree EDDI is fully operational, but the install instructions state if it is done properly, I should see the "Plugin EDDI 3.4.2 initialized" dialog as VA starts up. I don't see this at all.

My EDDI plugin version is 3.5.2 and seems to be the EDDI version, not the one written by VA?

Am I missing the EDDI version of the plugin?

9:00:51.082 Ready, waiting for you to log into Elite... 9:00:46.157 Reading keybinds from Elite and checking for any missing... 9:00:46.153 Setting game to Elite: Dangerous 9:00:46.094 T-Pol has all stations covered 9:00:43.243 Detecting the crew... 9:00:42.710 Running diagnostic checks... 9:00:38.674 Loading customiser settings... 9:00:38.672 Initialising, please wait... 9:00:37.714 VoiceAttack profile - (c) 2017-2020 HCS VoicePacks Ltd 9:00:37.711 Singularity v2.3 - VoiceAttack v1.8.3

Tkael commented 4 years ago

You should see

Plugin 'EDDI 3.5.2' initialized.
The EDDI plugin is fully operational.

in the VoiceAttack event log (I see "EDDI 3.5.3-b1 initialized" on my development build). You might need to scroll the VoiceAttack event log a bit to get past the HCS text?

incryptx commented 4 years ago

This is all I see in my VA window. There is plenty of space in the window to display all dialog.

9:00:51.082 Ready, waiting for you to log into Elite... 9:00:46.157 Reading keybinds from Elite and checking for any missing... 9:00:46.153 Setting game to Elite: Dangerous 9:00:46.094 T-Pol has all stations covered 9:00:43.243 Detecting the crew... 9:00:42.710 Running diagnostic checks... 9:00:38.674 Loading customiser settings... 9:00:38.672 Initialising, please wait... 9:00:37.714 VoiceAttack profile - (c) 2017-2020 HCS VoicePacks Ltd 9:00:37.711 Singularity v2.3 - VoiceAttack v1.8.3 It should be right here.................

I don't get any of this: Plugin 'EDDI 3.5.2' initialized. The EDDI plugin is fully operational

Where is the VoiceAttack event log?

incryptx commented 4 years ago

Got it. I had to unckeck "enable log quiet mode" in VA Settings.

Now I get:

9:59:50.357 Ready, waiting for you to log into Elite... 9:59:44.122 Plugin 'EDDI 3.5.2' initialized. 9:59:44.038 The EDDI plugin is fully operational. 9:59:42.991 Reading keybinds from Elite and checking for any missing... 9:59:42.987 Setting game to Elite: Dangerous 9:59:42.910 T-Pol has all stations covered 9:59:41.479 Reading in Voice Triggers from template 'English Singularity - Custom - Custom'... 9:59:40.752 Detecting the crew... 9:59:40.460 Running diagnostic checks... 9:59:38.093 Loading customiser settings... 9:59:38.091 Initialising, please wait... 9:59:38.087 Listening suspended 9:59:37.083 VoiceAttack profile - (c) 2017-2020 HCS VoicePacks Ltd 9:59:37.081 Singularity v2.3 - VoiceAttack v1.8.3 9:59:35.310 Plugin 'HCS Plugin v3.3.7 - (c) 2016-2020 HCS VoicePacks Ltd' initialized. 9:59:34.350 Plugin support enabled.

Does this create a VA log file somewhere. That would be helpful in the future.

Close this, not a bug. Sorry.

Tkael commented 4 years ago

I don't believe that the event log is automatically recorded outside of the play session but I could be wrong.