Author Topic: VoiceAttack Log Reporting (Plugins, applications, profiles Initialized)  (Read 1507 times)

Incryptx

  • Newbie
  • *
  • Posts: 27
In looking at the option called "Enable Log Quiet Mode", when you enable this, some of the plugins and copyrighted profiles, as well as those with version numbers do not show up, but some basic ones do and the ones which have to report that they have "initialized" are not displayed, which are all important when troubleshooting which plugins have started and what versions they are.

Now, when you disable "Enable Log Quiet Mode" all the plugins and copyrighted profiles, as well as those with version numbers do show up, but with all of the other items of the logs being displayed, it becomes noisy and hard to see just what plugins, profiles and versions are there.

So, this is more of a troubleshooting benefit for the user to see all of the plugins, profiles and version information of what is being used, started or present with the "Enable Log Quiet Mode" check box enabled, as a minimum to be seen on the Voiceattack log presented at startup.

I would suggest a "check box" separate from "Enable Quiet Log Mode" called "Show Version Information" which could be checked or unchecked, so the user can decide if they want to see profiles, applications and plugin version information.

Marked in bold, is what should be seen with "Enable Log Quiet Mode" enabled or checked at a minimum.

Here is an example of what I mean. This is the result of "Enable Log Quiet Mode" enabled.

8:37:21.802 Ready, waiting for you to log into Elite...
8:37:16.930 Reading keybinds from Elite and checking for any missing...
8:37:16.926 Setting game to Elite: Dangerous
8:37:16.856 T-Pol has all stations covered
8:37:15.451 Reading in Voice Triggers from template 'English Singularity - Custom - Custom'...
8:37:14.698 Detecting the crew...
8:37:14.267 Running diagnostic checks...
8:37:09.356 Plugin 'EDDI 3.5.2' initialized.
8:37:09.296 The EDDI plugin is fully operational.
8:37:09.220 Loading customiser settings...
8:37:09.204 Initialising, please wait...
8:37:09.166 Listening suspended
8:37:07.662 VoiceAttack profile - (c) 2017-2020 HCS VoicePacks Ltd
8:37:07.646 Singularity v2.3 - VoiceAttack v1.8.3
8:37:05.309 Plugin 'HCS Plugin v3.3.7 - (c) 2016-2020 HCS VoicePacks Ltd' initialized.
8:37:04.380 Plugin support enabled.

Now, if you uncheck "Enable Log Quiet Mode", this is what you get and the difference, which does not show all of the plugins, profiles and version numbers of what is running, and for troubleshooting purposes, these items not shown, should be shown regardless of whether the "Enable Quiet Log Mode" is checked or unchecked, for the benefit of the user to see in any event. This is helpful to all users to see all of these as being started.

12:17:23.869 Ready, waiting for you to log into Elite...
12:17:16.399 Reading keybinds from Elite and checking for any missing...
12:17:16.395 Setting game to Elite: Dangerous
12:17:16.338 T-Pol has all stations covered
12:17:14.109 Detecting the crew...
12:17:13.823 Running diagnostic checks...
12:17:11.465 Loading customiser settings...
12:17:11.463 Initialising, please wait...
12:17:10.460 VoiceAttack profile - (c) 2017-2020 HCS VoicePacks Ltd
12:17:10.457 Singularity v2.3 - VoiceAttack v1.8.3

So, as you can see, only three items are shown to start with version information, two profiles, and VoiceAttack itself.

It would be better for consistency purposes, as well as troubleshooting purposes, if all profiles with version info, applications with version info and external plugins with version information were displayed regardless of the "Enable Log Quiet Mode" setting, whether it is checked (enabled) or unchecked (disabled)

Because I had "Enable Log Quiet Mode" checked and enabled, I spent hours digging around trying to find out whether EDDI was enabled and intitialized when the EDDI troubleshooting website stated you should see a dialog showing 1) Plugin 'EDDI 3.5.2' initialized. and 2)The EDDI plugin is fully operational. If these had been listed in VA's window log, regardless of the VA log mode setting, I would not have wasted so much time looking for them and my problem would have been immediately solved.

So, for consistency sake, troubleshooting sake, and general user information sake, any profile, application or plugin which starts, initializes or reports a version number should be shown regardless of whether the "Enable Log Quiet Mode" is checked or unchecked. 

I would suggest a "checkbox" separate from the "Enable Log Quiet Mode" called "Show Version Information" which when checked, would show version information for all profiles, applications and plugins which contain this information. This would allow the user to show that information without affecting what the "Enable Log Quiet Mode" currently does.



Gangrel

  • Caffeine Fulled Mod
  • Global Moderator
  • Full Member
  • *****
  • Posts: 216
  • BORK FNORK BORD
Re: VoiceAttack Log Reporting (Plugins, applications, profiles Initialized)
« Reply #1 on: January 21, 2020, 01:59:03 PM »
For the HCS profile, the lines

Code: [Select]
8:37:07.662 VoiceAttack profile - (c) 2017-2020 HCS VoicePacks Ltd
8:37:07.646 Singularity v2.3 - VoiceAttack v1.8.3

Those are written by a command in the profile itself. So that is why they appear when you have the Quiet mode enabled.

If you go for any other profile, it will not show those messages in the slightest, not even the VA version number if you had VA Quiet mode enabled/disabled. This is something that the HCS profiles do themselves.

Incryptx

  • Newbie
  • *
  • Posts: 27
Re: VoiceAttack Log Reporting (Plugins, applications, profiles Initialized)
« Reply #2 on: January 21, 2020, 02:07:29 PM »
Well, I know why it occurs, but that was not my point.

As a suggestion, why not give the user the ability to show all version information for profiles, applications and plugins that start up, regardless of the VA log setting. If for no other reason than to display it for troubleshooting and copyright purposes, regardless of VA's log settings.

I, for one would like to use the Quiet Log mode, but still see all the profiles, applications and plugins start and initialize.

 

Gary

  • Administrator
  • Hero Member
  • *****
  • Posts: 2832
Re: VoiceAttack Log Reporting (Plugins, applications, profiles Initialized)
« Reply #3 on: January 21, 2020, 02:18:27 PM »
If the, 'write to log' action is used, the user can opt to display those items.  That should be all that's needed, normally.  I'd have to check if that's allowed from the proxy, though.

Sorry that it cost you a lot of time - you can always check if plugins are loaded by going to Options > General and click on, 'Plugin Manager' to display what plugins are being loaded.  You can also see what profiles are being included with your current profile by going to Profile Options (from the profile edit screen) and looking at the, 'include commands from other profiles' option.  Also, if you ever find yourself spending hours trying to figure something out, swing on by the VA Discord server and get another set of eyes on it - http://voiceattack.com/discord

Pfeil

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4782
  • RTFM
Re: VoiceAttack Log Reporting (Plugins, applications, profiles Initialized)
« Reply #4 on: January 21, 2020, 02:21:13 PM »
I'd have to check if that's allowed from the proxy, though.
Can confirm that it is not.

Gary

  • Administrator
  • Hero Member
  • *****
  • Posts: 2832
Re: VoiceAttack Log Reporting (Plugins, applications, profiles Initialized)
« Reply #5 on: January 21, 2020, 03:07:59 PM »
I'll check it out

This has been fixed and will be in a later release (not the beta that's about to be released, but the next one).
« Last Edit: January 21, 2020, 05:08:50 PM by Gary »