Modularize the .VAP Profiles

[sutex]

Post here if you wish to follow , any response to this
http://voiceattack.com/smf/index.php?topic=659.0

A check on export for "linked" commands and a user query :
There are some command missing for the selected exports to work properly
Do you wish to add them to the list ?

We've been waiting for this function to be implemented for months! It could be worth putting in a request on the Voice Attack forums, remind Gary and all that

[Bragolatch]

Could be a nice addition to VA

A check on export for "linked" commands and a user query :
There are some command missing for the selected exports to work properly
Do you wish to add them to the list ?

If yes is selected the check should of course be done again after adding the missing commands,
to make sure those didn't have dependencies too. Rinse an repeat until nothing is missing then complete the export.

[Gangrel]

In reference to other posts, which are highlighting the need to be able to export .vap or html via the category function in VA
https://forums.frontier.co.uk/showth...=1#post2249091

And this also shows what happens when you export a profile which doesn't contain everything needed to run it. This is why the .vap there has so many "unable to execute commands". So even if you have the "category" version of the export, if the commands needed are NOT in the correct category, this would happen.

Side note: It would be better for your profile to run the ((commands)) instead of the *VOICE* activated one instead. There are ways around the "Unable to execute command". Choose the "execute by name (advanced)" option. This can help cut down on the error.

So instead of "open comms; Open comms panel; comms panel on"... it would be ((Comms Panel))_[1]. It is just a little bit easier, instead of referring to a command which refers to another command.

This is why (with the Beta packs and stuff like docking requests) always tries to run the "keybind" command instead of the spoken command. The spoken side is open for your customisation. The ((command side)) is not really meant to be touched (change the keypress and that is it), be as basic as possible and run the background logic.

What I would personally do, is copy the commands to a "blank" profile and run them from there. You can do this by right clicking the command and choosing "copy to..." Takes a few more clicks, but it is a work around. It also means that you can make sure you get the logic there as needed.

The best way to deal with profiles here, especially if you are not aware of what people have as a baseline to work from, is to ASSUME that they don't have anything present. Make sure that it all works "out of the box" for them, with as little setup as possible.

[1] Using HCS Voice Pack logic here. If you are not using the pack, then ignore this.

[sutex]

In reference to other posts, which are highlighting the need to be able to export .vap or html via the category function in VA
https://forums.frontier.co.uk/showth...=1#post2249091

[Lensman]

I agree with you Modularizing it for better Dev work. Ill Pass it on and see what we can do ^_^

i agreee with rega's agreement - this could make things easier if you're trying to create a profile for a different game...

[ForumAdmin]

I agree with you Modularizing it for better Dev work. Ill Pass it on and see what we can do ^_^

[sutex]

, "But i do think one of the reasons we have had issues with importing them is they are depending on other commands to be executed as well for them to work."

Yes that 's the main problem , if docking was a seperate .VAP and had all the sub commands it needed to run , you could then just import that , Also VAP been modularized , means exporting just the ONE .vap to a new profile , just makes it easier to see those commands , for you then know what is need for Docking, for it to work , because all the sub commands are there

If you import Comms, Docking, Nav panels , and the sub commands are repeated , the you get the RED overwrite , which is good way of learning how it all works and what is common to other commands

Modularizing VAP also allows the DEV's , to just make a bunch of NEW sub commands , if there's a better way of doing the timing , or if Comms panel changes again , instead of doing the whole Profile

Example , there's great new Docking.vap , we down loaded it open up VA , click on Docking , automatically all the sub commands are selected for our current Docking , we export that , as a fail safe , then delete the old Docking, and import the new Docking.vap

[ForumAdmin]

Hey Sutx , thanks for your feed back. Ill have a chat with void flakes about this one, But i do think one of the reasons we have had issues with importing them is they are depending on other commands to be executed as well for them to work.
So if you try to import a command that is depended on one that is'nt there, Voice attack has a bit of a fit.
As for changing what you have to say for a command to run . Iv changed one myself for the departure maneuver to " Lets GO " did'nt have any issues. not sure about the panel commands tho. As it does say it is beta so we are trying to tweak it the best can, iv been using the profile for sometime, with some issues but i tent to get around them. But like i said ill have a chat with Void about it , see if we can split them up in to different profiles maybe . Still think only issue is the limit voice attack has on the import function for now .

[sutex]

As of last update .1.6.4 Beta Profile ,have attempted twice for an hour or more to import the commands I need, either into my Current profile, or out into your 1.6.4 Beta Profile, invariably I've miss the sub commands a Command needs for them to work
It's difficult to see the whole of the condition values as it does not fit onto the page. so I can see what is, There has to be a better way of using just the commands you want We have nearly the same "SAY" to execute these commands , but what they call is completely different ,Or its the other way around different "SAY" calling the same conditional or commands

Can we Please have theses Profiles split up into their Categories , to make importing easier

Any new command ; ie WINGS wings.vap
Docking
Panels
Comm
FTL
Targeting
Menu Commands
Reset

If I want just the new comms functions to import Or my version of DOCKING just doesn't work , Then If I check Comms , or Docking then everything they need to run is also checked , nothing else , I can then export these or import just these
As everyone profile is growing and people are mixing and matching , then for easy of use , Modularize the .VAP Profiles, is the only way to go

previous post https://groups.google.com/d/msg/voic...g/onkODMGebVwJ