Jump to content

VaicomPro Problem importing F10 Menu


Turbine 205

Recommended Posts

Hello fellow VaicomPro users.  I've recently started having issues with Vaicom not executing commands in the F10 menu.  Below is a copy of the VA log.   Any help is greatly appreciated.  For reference this is happening on multiple servers I play on.  I've not tried it out yet on single player missions.  I also have my dcs path manually set in the config options as I've seen not having set causes the memu to keep popping up randomly in DCS.

12:00:21.769 There was a problem importing the F10 menu.
12:00:15.851 There was a problem importing the F10 menu.
12:00:09.768 There was a problem importing the F10 menu.
12:00:03.741 There was a problem importing the F10 menu.
11:59:57.959 There was a problem importing the F10 menu.
11:59:57.931 Chatter theme init: Object reference not set to an instance of an object.
11:59:57.929 Adding themepack collections
11:59:57.888 Nearest ATC: Anapa-Vityazevo.
11:59:57.887 Player CSG-3 | Turbine | 205 entered module FA-18C Hornet, unit callsign Colt11
11:59:57.886 Resetting selected units.
11:59:57.882 DCS mission | Ca_DTE Night v7.2
11:59:57.881 ------------------------------------------
11:55:27.536 Plugin 'VAICOM PRO for DCS World' initialized.
11:55:27.524 Ready for commands.
11:55:27.523 Startup finished.
11:55:27.487 Listening suspended
11:55:27.407 Chatter theme init: Object reference not set to an instance of an object.
11:55:27.405 Adding themepack collections
11:55:27.395 No new DCS modules to import.
11:55:27.393 Success.
11:55:27.393 Building master labels table...
11:55:27.388 Object reference not set to an instance of an object./n   at VAICOM.Database.Aliases.BuildKneeboardAliasList()
11:55:27.382 Building kneeboard tables...
11:55:27.378 Building master keywords table...
11:55:27.377 Adding 0 imported menu commands.
11:55:27.375 Adding 0 imported ATC aliases.
11:55:27.372 Done.
11:55:27.371 Updating aliases..
11:55:27.369 Success.
11:55:27.362 Loading F10 menu items...
11:55:27.360 Success.
11:55:27.115 Loading keywords database...
11:55:27.093 Done.
11:55:27.063 Initializing database tables...
11:55:27.060 Done.
11:55:27.058 Importing RIO extension pack...
11:55:27.006 Checking VA profile.
11:55:26.885 DCS World version STEAM not found.
11:55:26.855    6/7 DCS-side files were updated.
11:55:26.842    Reset: gameMessages.lua
11:55:26.839    Reset: TabSheetBar.lua
11:55:26.837    Reset: common.lua
11:55:26.834    Reset: speech.lua
11:55:26.832    Reset: RadioCommandDialogsPanel.lua
11:55:26.830    Reset: VAICOMPRO.export.lua
11:55:26.827    Unchanged: Export.lua
11:55:26.826    Saved Games folder = D:\Users\Roger J Howland\Saved Games\DCS.openbeta
11:55:26.822    Install path = C:\Program Files\Eagle Dynamics\DCS World OpenBeta
11:55:26.822    Using custom install path for 2.5 OpenBeta
11:55:26.821 DCS World version 2.5 not found.
11:55:26.797 Executing automatic lua code installation.
11:55:26.560 License: PRO
11:55:26.559 Plugin version 2.5.27.3 (release)
11:55:26.174 Initializing..
11:55:26.174 Press LCtrl+LAlt+C for config.
11:55:26.174 VAICOM PRO for DCS World. License: PRO
11:55:25.652 Plugin support enabled.
 


Edited by Turbine 205
Link to comment
Share on other sites

8 hours ago, Turbine 205 said:

Hello fellow VaicomPro users.  I've recently started having issues with Vaicom not executing commands in the F10 menu.  Below is a copy of the VA log.   Any help is greatly appreciated.  For reference this is happening on multiple servers I play on.  I've not tried it out yet on single player missions.  I also have my dcs path manually set in the config options as I've seen not having set causes the memu to keep popping up randomly in DCS.

12:00:21.769 There was a problem importing the F10 menu.
12:00:15.851 There was a problem importing the F10 menu.
12:00:09.768 There was a problem importing the F10 menu.
12:00:03.741 There was a problem importing the F10 menu.
11:59:57.959 There was a problem importing the F10 menu.

 

 

From the manual:

MP Server Special Menus

Through the ‘Import F10 Menus’ function it is possible to add server-specific commands to the voice commands set. Imported F10 menu items get ‘Action’ in front of the phrase: for example an imported menu item ‘Push to Waypoint 2’ would become ‘Action Push to Waypoint 2‘ on import. This can then become anything you like in the keywords editor. This import will only work if the server has implemented the F10 menu in the standard compatible manner (which is the case for most servers).

MP limitations

Multiplayer mission designers can take great liberties in mission design, e.g. by introducing custom callsigns, custom menus and all kinds of other tweaks outside of the default spectrum. VAICOM PRO cannot support these by default. Where the mission design makes use of the standard features, VAICOM PRO will support them. But some limitations may apply on some specific servers.

Regarding the issue with manually setting the DCS path, have you tried using the "fix registry" option? Generally you can turn off the manual setting of the path once you fix the registry. Be sure to restart VoiceAttack and then DCS after making the change.

  • Like 1

I'm Softball on Multiplayer. NZXT Player Three Prime, i9-13900K@3.00GHz, 64GB DDR5, Win 11 Home, Nvidia GeForce RTX 4090 24GB, TrackIR 5, VKB Gunfighter III with MCG Ultimate grip, VKB STECS Standard Throttle, CH Pro pedals

Link to comment
Share on other sites

@sthompson
Yes I've used the fix registry before for the constant popping up/off of the comms menu issue.  That is not the source of my problem.

For some clarity,  we are using the standard F10 menu for our missions.  I can pertest that there are others within my squadron that use VoiceAttack and they have no issues on the server I fly on.

Link to comment
Share on other sites

On 5/9/2022 at 11:45 PM, Turbine 205 said:

@sthompson
Yes I've used the fix registry before for the constant popping up/off of the comms menu issue.  That is not the source of my problem.

For some clarity,  we are using the standard F10 menu for our missions.  I can pertest that there are others within my squadron that use VoiceAttack and they have no issues on the server I fly on.

You seem to have two issues and I was trying to be helpful on both. I didn't mean to imply that they were connected, although your original post seemed to suggest that you thought they might be connected. You now seem to think otherwise.

Problem one: Errors importing the F10 menu. If others are doing this successfully from the same mission then it must be an issue in your setup. Unfortunately, this feature of VAICOM is pretty opaque and the error messages obviously aren't very helpful. I have a few thoughts about what the problem might be, but I'm speculating. First, if you use the Import F10 menu a lot then it's possible that you have added a lot of commands to the VAICOM database and possibly there is a limit that you have exceeded. Second, it's possible that the commands you are trying to import conflict somehow with ones already in the database. Third, the database might be corrupted. Either way, I would try a reset of your keyword database and your VAICOM profile to see if the problem goes away.

BTW, when you say that "others have no problem" do they have the same settings for VAICOM?

Problem two: You have flashing comms menu unless you specify a custom DCS path. Typically this means that your registry entry for the corresponding DCS version has a problem so that VAICOM cannot find that version of DCS using the registry. I would recommend that you use the "fix registry" solution again, being sure to put the version slider in the right place first. After that, and upon restarting VAICOM you should be able to turn the custom path off. Note that changes in these settings take effect the next time you restart VAICOM, so always restart after making a change to the custom path options.

I hope this helps!

 

  • Like 1

I'm Softball on Multiplayer. NZXT Player Three Prime, i9-13900K@3.00GHz, 64GB DDR5, Win 11 Home, Nvidia GeForce RTX 4090 24GB, TrackIR 5, VKB Gunfighter III with MCG Ultimate grip, VKB STECS Standard Throttle, CH Pro pedals

Link to comment
Share on other sites

1 hour ago, sthompson said:

You seem to have two issues and I was trying to be helpful on both. I didn't mean to imply that they were connected, although your original post seemed to suggest that you thought they might be connected. You now seem to think otherwise.

Problem one: Errors importing the F10 menu. If others are doing this successfully from the same mission then it must be an issue in your setup. Unfortunately, this feature of VAICOM is pretty opaque and the error messages obviously aren't very helpful. I have a few thoughts about what the problem might be, but I'm speculating. First, if you use the Import F10 menu a lot then it's possible that you have added a lot of commands to the VAICOM database and possibly there is a limit that you have exceeded. Second, it's possible that the commands you are trying to import conflict somehow with ones already in the database. Third, the database might be corrupted. Either way, I would try a reset of your keyword database and your VAICOM profile to see if the problem goes away.

BTW, when you say that "others have no problem" do they have the same settings for VAICOM?

Problem two: You have flashing comms menu unless you specify a custom DCS path. Typically this means that your registry entry for the corresponding DCS version has a problem so that VAICOM cannot find that version of DCS using the registry. I would recommend that you use the "fix registry" solution again, being sure to put the version slider in the right place first. After that, and upon restarting VAICOM you should be able to turn the custom path off. Note that changes in these settings take effect the next time you restart VAICOM, so always restart after making a change to the custom path options.

I hope this helps!

 

Hi again.
No its just this single issue I'm having.  I'm not currently experiencing the problem two that you describe.  That I know how to fix with the registry.   I've only called it out because others have said to use that which clearly is not the issues.

In terms of the actual problem, yes I'm using the same profile as others within my squadron.  In fact I wrote some of the additional command scripts to add some additional features to control non Viacom specific tasks, like setting up DDI's the way I want them, configuring for different A/A and A/G modes.  All of which I checked against the keywords in the keywords command of the VA profile to ensure that I wasn't stepping over.

Link to comment
Share on other sites

As an update, I imported into VA the original ViacomPro profile without any edits by me.  I am still seeing the exact same issue on this profile, so its definitely something location to Viacom.  I'm going to play around with resetting the keyword data base and retry.  Below is the log to confirm.

12:41:20.681 There was a problem importing the F10 menu.
12:41:14.741 There was a problem importing the F10 menu.
12:41:08.699 There was a problem importing the F10 menu.
12:41:02.680 There was a problem importing the F10 menu.
12:40:56.685 There was a problem importing the F10 menu.
12:40:50.647 There was a problem importing the F10 menu.
12:40:44.857 There was a problem importing the F10 menu.
12:40:44.833 Chatter theme init: Object reference not set to an instance of an object.
12:40:44.831 Adding themepack collections
12:40:44.818 Nearest ATC: CVN-71 Theodore Roosevelt.
12:40:44.817 Player CSG-3 | Turbine | 202 entered module FA-18C Hornet, unit callsign Springfield11
12:40:44.816 Resetting selected units.
12:40:44.816 DCS mission | VFA-14 Public Syria Day v1.19
12:40:44.814 ------------------------------------------
12:38:56.585 There was a problem importing the F10 menu.
12:38:50.566 There was a problem importing the F10 menu.
12:38:44.735 There was a problem importing the F10 menu.
12:38:44.713 Chatter theme init: Object reference not set to an instance of an object.
12:38:44.711 Adding themepack collections
12:38:44.656 Nearest ATC: Paphos.
12:38:44.656 Player CSG-3 | Turbine | 202 entered module TF-51D Mustang, unit callsign Enfield11
12:38:44.655 Resetting selected units.
12:38:44.652 DCS mission | VFA-14 Construct v1.6
12:38:44.650 ------------------------------------------
12:35:47.083 Opening Configuration window
12:35:46.860 Shortcut : 'Configuration'
12:34:56.410 Plugin 'VAICOM PRO for DCS World' initialized.
12:34:56.394 Ready for commands.
12:34:56.393 Startup finished.
12:34:56.355 Listening suspended
12:34:56.258 Chatter theme init: Object reference not set to an instance of an object.
12:34:56.257 Adding themepack collections
12:34:56.234 No new DCS modules to import.
12:34:56.232 Success.
12:34:56.231 Building master labels table...
12:34:56.230 Object reference not set to an instance of an object./n   at VAICOM.Database.Aliases.BuildKneeboardAliasList()
12:34:56.220 Building kneeboard tables...
12:34:56.216 Building master keywords table...
12:34:56.215 Adding 0 imported menu commands.
12:34:56.214 Adding 0 imported ATC aliases.
12:34:56.211 Done.
12:34:56.210 Updating aliases..
12:34:56.207 Success.
12:34:56.193 Loading F10 menu items...
12:34:56.192 Success.
12:34:55.946 Loading keywords database...
12:34:55.921 Done.
12:34:55.889 Initializing database tables...
12:34:55.886 Done.
12:34:55.885 Importing RIO extension pack...
12:34:55.830 Checking VA profile.
12:34:55.647 DCS World version STEAM not found.
12:34:55.610    6/7 DCS-side files were updated.
12:34:55.579    Reset: gameMessages.lua
12:34:55.576    Reset: TabSheetBar.lua
12:34:55.573    Reset: common.lua
12:34:55.570    Reset: speech.lua
12:34:55.568    Reset: RadioCommandDialogsPanel.lua
12:34:55.564    Reset: VAICOMPRO.export.lua
12:34:55.561    Unchanged: Export.lua
12:34:55.552    Saved Games folder = D:\Users\Roger J Howland\Saved Games\DCS.openbeta
12:34:55.548    Install path = C:\Program Files\Eagle Dynamics\DCS World OpenBeta
12:34:55.547    Using custom install path for 2.5 OpenBeta
12:34:55.546 DCS World version 2.5 not found.
12:34:55.532 Executing automatic lua code installation.
12:34:55.328 License: PRO
12:34:55.327 Plugin version 2.5.27.3 (release)
12:34:54.917 Initializing..
12:34:54.917 Press LCtrl+LAlt+C for config.
12:34:54.917 VAICOM PRO for DCS World. License: PRO
12:34:53.962 Plugin support enabled.
 

Link to comment
Share on other sites

29 minutes ago, Turbine 205 said:

In terms of the actual problem, yes I'm using the same profile as others within my squadron.  In fact I wrote some of the additional command scripts to add some additional features to control non Viacom specific tasks, like setting up DDI's the way I want them, configuring for different A/A and A/G modes.  All of which I checked against the keywords in the keywords command of the VA profile to ensure that I wasn't stepping over.

You're talking about plain VoiceAttack commands, right? 

I always keep those in seperate profiles, and this is not your issue anyway. VoiceAttack doesn't really do anything related to VAICOM. VAICOM is the one connected to DCS for the import. 

I'm crossing my fingers that a DB reset will help. 🤞🏻👍🏻

Cheers! 

Link to comment
Share on other sites

4 minutes ago, Turbine 205 said:

@MAXsenna
Thanks for taking a look.  I do apologize I've not delved enough into the Viacom setup and the manual.  How do I go about resetting the database?

Export on the Config tab or the Keywords editor tab. 

Reset keywords on the Reset tab. 

Link to comment
Share on other sites

@MAXsenna
Thank you for the help on that.  I was able to get it to work.  Must've been something with the Lua code.  I backed it all up and performed the keywords reset in the reset tab.  That didn't solve it so I did a lua code reset.  That did the trick.
 
Thank you @maxsenna and @sthompson for the help.
Awesome!

Sent from my MAR-LX1A using Tapatalk

  • Like 1
Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...