Discussion 3.7 VoiceAttack Profile Sharing. (EDDI / bindED)

CMDR bronney

CMDR bronney
Hello Boys! I've finished updating my profile based on Ishmair's for 3.7. Tested. Added many new features such as bindED, new EDDI states, night vision, FSS, etc. Also debugged many non-exiting conditions and solid tab checks hehe. So happy to share with you all. Have fun out there commander. o/

You need bindED: https://forum.voiceattack.com/smf/index.php?topic=564.0
and EDDI: https://github.com/EDCD/EDDI/releases

Profile walk-through (actual youtube is time-stamped):
Source: https://www.youtube.com/watch?v=mQ7xhUjEAE0&list=PL63PGTpR-DXo9ZwoIDvtvCXLkNppQyPwa&index=3&t=727s


Original Thread: https://forums.frontier.co.uk/threads/voice-attack-profile-sharing.53846/page-9
YouTube Demo: https://www.youtube.com/playlist?list=PL63PGTpR-DXo9ZwoIDvtvCXLkNppQyPwa
 
Last edited:

CMDR bronney

CMDR bronney
NEW VERSION is OUT:

VAP Download (with bindings) Updated 2020 Oct. 26 WIP (subsequent versions will be overwritten in the zip with new dates VAP as you unzip) :

Elite Logitech X3D- elite 3.7 WIP 2020 10 26-Profile.zip

drive.google.com drive.google.com
  • Overhaul FSD related commands, say disengage anywhere and it'll do logical things
  • Added some EDDI FSD related commands
  • Minor crafting tab sync checks (tab 5 instead of tab 4 now on the right panel)
  • Oct 27, Launch command. Added a 1 sec. pause after thrust up to retract gears
  • Oct 29, Bugged var in ((EDDI ship fsd)) trigger fixed, removed fighter = 0
  • Oct 30, sys-map, galaxy-map var outdated led to tab problems when calling either maps, then manual tabs, then back to panels. Updated affected commands to use the new EDDI {TXT:Status gui focus} instead which made both these vars irrelevant. Tested.
  • Oct 31, gave all commands and non voice commands a once-over. >90% of all commands are affected.
    • Replaced most outdated vars with
      {TXT:Status vehicle}
      {BOOL:Status landed}
      {BOOL:Status docked}
      {BOOL:Status landing gear down}
      {BOOL:Status hardpoints deployed}
      {BOOL:Status cargo scoop deployed}
      {TXT:Environment}
      Some legacy vars do have their merits and are kept
    • Sensor zooms + presses accommodate for supercruise zoom range difference
    • Added options to launch fighter one or two (launch fighter one player, launch fighter two crewmen, switch one, etc.)
    • Deleted vehicle deaths, replaced with ((EDDI vehicle destroyed))
  • Nov 1, added a while loop to target specific subsystems
    • Only 5 subsystems are online for now (Power Plant, FSD, Power Distributor, Thrusters, Life Support)
    • If I do Heatsinks and the ship doesn't have heatsinks, the while loop won't break so that's not optimal
    • Another way to do it is by counting total subsystems, for example, a Corvette can have 30. i++ 30, exit, etc.
    • The rest needs to wait for an EDDI state of targetted ship size because a Corvette could have 30 subsystems, a Hauler would count less, etc.
  • Nov 10, Reworked "Auto Dock" command, instead of boosting which almost rekted my dirty drag G5 Chieftain, throttling to no fire zone check instead XD.
  • Nov 19, overwrite new binding file as the "Night Vision" Alt-Y was conflicting with the Launch (from planet surface) command Ctrl-Y somehow, bound it to N instead.
  • Nov 26, updated System Scan and Wake Scan command to better handle exceptions. Wake scan still isn't perfect as if you say it without a wake scanner, wrong fire group, non-primary button, without locking a wake first, locking a low wake instead, it'll still bug. So yeah.
  • Nov 27, updated Auto Dock command to cater for when the disengage dumps you straight into "no fire zone". Also added different approach speeds for ship sizes. Or when you're flying the cow and the gap between no fire zone to 7.5k is too long lol. Tested on the Type-9 so it should be ok. If you encounter problems with other sizes please voice out.
  • Nov 29, bug fixed the "Cargo Transfer" and "Board Ship" SRV commands to do more UI downs as your cursor could be on the SRV desc. bit if you manual roles panel earlier.
  • Dec 03, improved panels to let you do things manually including tab next previous, and back, even pressing 1 2 3 4, or press 4 while you're in 1 etc etc. This update is suggested by CMDR WallK after he notices his HCS packs don't screw up when tabbing manually. There are 2 ways to brick this.
    1. There's a delay for when you press 1 for the left panel to render so that the API can register that your {TXT:Status gui focus} went from 'none' to 'external panel'. So if you wanna bug it, all you had to do is tab next/previous right when you press 1 for example.
    2. If you manually tab REALLY fast like double clicking your tab next bind, it will rekt. I tested them all. There's no solution.
  • Dec 05, Updated 'Docking Request' to do a right left right to "refresh" the weird clicking bug ED has. If you leave the highlight on request docking for some reason it doesn't work the second time you request docking when your docking is denied the first time. Tested.
  • Dec 11, new command "power buy". I am new to powerplay and notice the buying 10 per is very annoying so I just macro buy. Click Station Services, Contacts, Power Contact, and say "power buy". I will buy you 100 of the thing (buy 10 repeats 10 times). You can edit the command to suit your buys (how many times it repeats). Or if you're not buying and contracting, just delete a down from the down down down. Tested.
  • Dec 12, migrated all BOOL text compare to Boolean compare.
    • Deleted enable disable flight assist, just say flight assist, don't think you can't tell the difference whether you have it on.
    • Added flight assist check inside the "Launch" command.
    • Moved "Leave Planet" to the macros sub-cat.
  • Dec 21, updated "power buy" command because FDev updated powerplay buy to 20 per instead of 10, made new bindED command to hold UI Right for 2 seconds so it buys faster. Command repetition to 5 so total buy is 100 per command run. Edit the rep as you please to achieve your cargo spec.
  • Jan 03, cleaned up all vars by removing the EDDI datatypes (TXT:, BOOL:, etc) and updated condition types to match. 90% commands affected. No change in logics.
  • Jan 06, bug fix the target subsystems. Tick evaluate "not set" as blank for conditions on the txt compare of the 5 voiced subsystems. Update binding files to not use WASD Left-Ctrl and Space bar as I use those for thrusters and can conflict when held while other commands running. Added command "Scoop" to hold the scoop button as I changed my scoop binding from toggle to hold in options. This won't affect you if you set toggle.
  • Jan 10, updated ((EDDI jumped)) to set left-panel-tab integer to 1 as jumps reset your panel tab back to Navigation while keeping the other panels untouched for some reason. Tested.
  • Jan 20, not a profile update but just discovered you need to bind the ship's scoop the same key as the SRV's scoop for the "deploy scoop" to work in both. That's all.
  • Jan 21, fixed "next neutron" command to do a generic tab next instead of a focus check tab next to get around the Oct 30 bugfix. Tested. Also note that you should bind the tab next and tab previous in game to their keys, whatever you use on the right column is fine but stay away from the ALTS. I switched mine to shifts as below:
    1611190074854.png
  • Jan 26, renamed bindings file and XML tag to bronneys20210126.binds for safer imports.
  • Jan 29, "Auto Dock" command, moved throttle zero BEFORE boost for large ships for smoother transition in no fire zone for docking. Tested in Type-9 A rated.
 
Last edited:

Phinister

P
A sincere thank you for your work and your youtube guide/setup commentary! It took me a while, but after fiddling around for a few days i am now very happy with my VA setup.

Hint for people with a different keyboard layout (mine is a german one, obviously): If some commands do not work with your customized keymapping, and you get a positive feedback/no error message from VA, but nothing happens - then set the command in Elite to a different, US Keyboard-compatible key.
After that, tell VA to rebind the keys, and try again.. (probably obvious, but it took me a while to figure it out).

There are many tutorials out there, but what helped me a lot to configure my keybinding for Elite itself was this YT video by Scoobulus:
Source: https://www.youtube.com/watch?v=bUtn7uvpU0M
 
Last edited:

CMDR bronney

CMDR bronney
Thank you, CMDR Phinister, for your kind words. Ishmair is the CMDR that started the ball rolling in 2014. The tab checks and panels he started was so easy to understand that other CMDRs can pick up on his logics and continue the work. He's also doing a 3.7 in parallel so you should check his out. He's the real programmer and I especially like his "non recognized" commands and I find his code to be more elegant than mine. But as said, I couldn't wait so whatever works :)

I won't even play ED if not for VA and EDDI tbh. And now with bindED, the whole process is streamlined. Thanks to fellow CMDRs, we can make this happen.

Regarding your keybindings. I've bound all keys on the "right column" in case you need to bind custom, which you should anyway, on the left column. The beauty of bindED of course, is that nothing stops you from binding the right column on your own also and then say "bind the keys". VA will re-run bindED and work. My profile also should auto run "bind the keys" whenever you start the VA.

I do notice something funny with keyboards, for example, my "]" becomes curcumflex instead of "]". Very strange as it's already a Corsair K70 Mk2 US keyboard. If future CMDRs have trouble with keybindings, please note that bindED reads the right column. You're free to rebind to anything you'd like just make sure you bind the right column.

Another note is be careful with the L-ALT, R-ALT, Shifts, etc. For example, if you bind an action that presses ALT-N, and you bound N to nightvision. There could be cases where you are running the ALT-N and say nightvision at the same time, that VA will bug. I've since tried to fix and update the .bind file included. But the cases are infinite. If you notice something funny, just rebind the right column of affected commands to something new. While staying away from the hardcoded ED CTRL-F for example (FDev use this to show fps), or F12, I use this for steam screenshots.

The command I use most at the moment is "Focus Target" and "Target FSD" hehehe. :ROFLMAO:
 
Last edited:

UseLessUK

UseLessUK
Phinister said:
Hint for people with a different keyboard layout (mine is a german one, obviously): If some commands do not work with your customized keymapping, and you get a positive feedback/no error message from VA, but nothing happens - then set the command in Elite to a different, US Keyboard-compatible key.
Click to expand...

You should try the updated version of bindED which can be found here https://forums.frontier.co.uk/threads/binded-3-0-import-your-key-binds-into-voiceattack.558439/ which now handles the German keyboard layout as well as the GB layout. I can now use the ' and # keys again. The updated version now also watches the binds file so if its changed then the bindED plugin will auto reload it again for the updated keys.
 

Phinister

P
UseLessUK said:
You should try the updated version of bindED which can be found here https://forums.frontier.co.uk/threads/binded-3-0-import-your-key-binds-into-voiceattack.558439/ which now handles the German keyboard layout as well as the GB layout. I can now use the ' and # keys again. The updated version now also watches the binds file so if its changed then the bindED plugin will auto reload it again for the updated keys.
Click to expand...

Thta's exactly the issue i had. I will look into it as soon as i need a break from piloting. Running a separate VA-test profile after keymapping backup should be no problem.

bronney said:
Regarding your keybindings. I've bound all keys on the "right column" in case you need to bind custom, which you should anyway, on the left column. The beauty of bindED of course, is that nothing stops you from binding the right column on your own also and then say "bind the keys". VA will re-run bindED and work. My profile also should auto run "bind the keys" whenever you start the VA.
Click to expand...

Can confirm it does work very well. All my keybindings for VA are on the right column - easier to import into a different profile (switching to mouse, or gamepad for example).

And props to Ishmair of course, i did read his thread(s) because you referenced his work as the foundation for your adjustements, and will follow his efforts as well. A true pioneer!
 
Last edited:

UseLessUK

UseLessUK
Had a look at your profile and found the Full Reset command to be interesting ... I do wonder why you don't use EDDI to test to see if the landing gear is deployed or not using this;
Code: 
Begin Boolean Compare : [Status landing gear down] Equals True
If that var is true gear is down, if false it's not. And it saves you having to keep track of a variable the same thing can be done with Hardpoints, Cargo Scoop etc etc
 

CMDR bronney

CMDR bronney
UseLessUK said:
If that var is true gear is down, if false it's not. And it saves you having to keep track of a variable the same thing can be done with Hardpoints, Cargo Scoop etc etc
Click to expand...
I have :) I am just lazy and didn't delete the old vars in case anyone using the old one pick this up. Almost all 1s and 0s that can be replaced with EDDI are replaced. It's 99% reliable but I find sometimes the 1s and 0s worked better. There were cases where I login in space and it won't let me jump, Amy says I am already jumping but I am sure I wasn't in the "else" case.
 

UseLessUK

UseLessUK
bronney said:
There were cases where I login in space and it won't let me jump, Amy says I am already jumping but I am sure I wasn't in the "else" case.
Click to expand...
That will be because you're using your own variables and when you logged out in space and logged in again the variables are now in an inconsistent state. Which is why it'd be much better using the EDDI ones which cover everything you'd want to test for. A bonus is they also track the actual state of the game :D
 

CMDR bronney

CMDR bronney
UseLessUK said:
That will be because you're using your own variables and when you logged out in space and logged in again the variables are now in an inconsistent state. Which is why it'd be much better using the EDDI ones which cover everything you'd want to test for. A bonus is they also track the actual state of the game :D
Click to expand...
Yes I think I will spend a day converting all BOOLs txt compare to status and migrate as best I can. I don't like deleting vars because some vars are needed for the calibration panels to work. Anyway.
 

UseLessUK

UseLessUK
bronney said:
Yes I think I will spend a day converting all BOOLs txt compare to status and migrate as best I can. I don't like deleting vars because some vars are needed for the calibration panels to work. Anyway.
Click to expand...
Well when you start changing stuff remember that this {BOOL:Status cargo scoop deployed} is a token you can use in something like this;
Code: 
Write [Orange] 'Cargo scoop is deployed = {BOOL:Status cargo scoop deployed}' to log
And to test the actual value you use the type of comparison indicated by the prefix, in the above case that'd be Boolean, so you end up with;
Code: 
Begin Boolean Compare : [Status cargo scoop deployed] Equals True

With {TXT:Status vehicle} you'd use a Text Compare like this;
Code: 
Begin Text Compare : [Status vehicle] Equals 'Ship'
again if you want to output which vehicle you're in to the log you'd use this;
Code: 
Write [Blue] 'Current vehicle = {TXT:Status vehicle}' to log
 

DawnTreader7

DawnTreader7
Hey gents.

TL;DR = I want to collaborate with like minded individuals on a VA profile and learn how to do some of the stuff in "Ishmair's Elite Dangerous Using [EDDIBindED Plugins]-Profile".

Bronney, I know that you borrowed this profile from Ishmair and that he got it some how/where from Malic_VR. I was wondering is there somewhere that Malic, Ishmair and you are collaborating on it and sharing changes and updates?

I just got into VoiceAttack because I saw the 2020 Anniversary Stream and then Malic_VR's video came up after that. Some of the stuff he did in the "squirrels" in that stream were really awesome and I saw him use some really great voice commands. It got me thinking about my own VoiceBot program that I was using and I tried to create some stuff to replicate what Malix_VR's VoiceAttack was doing. VoiceBot failed miserably. I spent 2 hours setting up a voice command in VoiceBot and it was never able to do what I wanted it to do. I tried the Demo of VA and in 1/2 an hour had the same thing working that I had attempted in VoiceBot.

Needless to say, I purchased VoiceAttack and have started trying to adapt a profile from somewhere, it is "Ishmair's Elite Dangerous Using [EDDIBindED Plugins]-Profile" and I think it was the latest, but it seems he wasn't finished parts of it.

One of the reasons I would like to collaborate with others is that I am still learning VA. I do have a bit of programming in my creative blood, I can whip up a good Access Database for almost anything, but I need to understand the profile I am working with a bit more.

Another reason is that I don't mind spending some time setting up commands and stuff, but I would like to play Elite as well as I do have a typical life with Wife, Kids, Job and stuff. I can't spend all day programming VA just so I can have more "immersion" in Elite... :D

Anyways, let me know your thoughts. Thanks!
 

DawnTreader7

DawnTreader7
Hey Bronney, one other question...

bronney said:
I do notice something funny with keyboards, for example, my "]" becomes curcumflex instead of "]". Very strange as it's already a Corsair K70 Mk2 US keyboard. If future CMDRs have trouble with keybindings, please note that bindED reads the right column. You're free to rebind to anything you'd like just make sure you bind the right column.
Click to expand...

When you say "right" you mean in the columns in the control bind options in the game, right? If that is the case, I need to rebind everything cause the left column is my "keyboard and mouse" and the right column is "HOTAS". When there are columns for something.
 

CMDR bronney

CMDR bronney
DawnTreader7 said:
right column is "HOTAS". When there are columns for something.
Click to expand...
Yes I meant the right column. The profile doesn't use every available binds in ED, if you'd like to study my bind file just make a backup of yours and copy mine in. You should bind the right column with keys you don't use in game to avoid conflicts. For some things, I don't use unique keys. For example, up down left right for pip management, as we all do, so I just bind up down left right on the right column. I also don't have a joystick bind for night vision, so I just bind an "n". It doesn't really matter what you bind in the right column as long as it's a "key" that VA can "press". They don't have to be CTRL-F7, etc. Study my bind file you'll see. I made it CTRL-weird stuff to make it easier for KB+M users to bind their own left column that's all.

DawnTreader7 said:
I was wondering is there somewhere that Malic, Ishmair and you are collaborating on it and sharing changes and updates?
Click to expand...
No we aren't collaborating. It was never brought up and I wasn't interested mainly because we all get on and off of the game. I quit for 3 years doing other stuff etc and got back in October and notice the 2.4 is outdated so I went ahead to update it that's all. Due to "freedom", we don't lol.

I don't mind offering suggestions here in the thread whether it's related to my iteration, or other stuff you need help with that's brand new. However, I think you'd have way better answers in this thread as here lies the combined knowledge of us all: https://forums.frontier.co.uk/threa...ddi-enabled-va-commands-thread.311614/page-58

This thread is also watched by way more people than us here in my thread so you'd have better solutions and suggestions when it comes to your own iteration.

DawnTreader7 said:
One of the reasons I would like to collaborate with others is that I am still learning VA. I do have a bit of programming in my creative blood, I can whip up a good Access Database for almost anything, but I need to understand the profile I am working with a bit more.
Click to expand...
The best way is to "study" the profile, whether mine or Ishmair, doesn't matter. And try to see how and why we do things like that. Why some end conditions have exits and some don't. Why those EDDI commands have obsolete variables that's been replaced with EDDI states that haven't been cleaned up (because I am lazy, but really they serve as "comments" to future CMDRs who pick this up after I leave lol). Or Ishmair's ingenious tab checks and calibration methods. Just go thru each command one by one to study them. It's what I did for the previous update and this with bindED. It's supposed to take time, but it's never wasted.

Thank you for checking in, and I will be looking forward to the magic you mentioned :)
 

DawnTreader7

DawnTreader7
oh, I thought I had taken it from the link in this thread. Rats. Will have to have a look at yours. Thanks.

And sorry, I have 3 accounts with Frontier, hope I didn't confuse you changing mid stream like that. I have confused myself...o_O
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom