In-Development Prototype planetary landing assistance using VoiceAttack inline function

I did know it worked as I tried it out before posting :)

The normal way to share scripts with other EDDI users is to post the script and the details, much as I have done in my post. I'd say that your installation instructions should detail how to enter the required script into the correct event in EDDI as well as the script itself.

Just as an aside, you'll notice that in the scripts the default value of the body_radius is zero and this is deliberate since you can trap the zero value in your VA scripts and output the appropriate response. The timing of the state variables is not guaranteed in EDDI so there is a possibility that the body_radius will not be set when the near surface VA command is triggered.
I guess EDDI users frequently copy and paste code fragments and whole scripts so they will understand the installation instructions.

Funnily enough, one of my early tests did encounter a body_radius set to zero as a result of the timing issue you mention. Provided the script is guaranteed to run, and the body_radius is eventually set in the state, I could try inserting a repeat loop with a pause in the VA event handler. I'm wary of making this a 'while body_radius < 1' loop which could be never-ending. Maybe, 'repeat 5 times' and tell the user if the radius is still not set.
 
I guess EDDI users frequently copy and paste code fragments and whole scripts so they will understand the installation instructions.

Funnily enough, one of my early tests did encounter a body_radius set to zero as a result of the timing issue you mention. Provided the script is guaranteed to run, and the body_radius is eventually set in the state, I could try inserting a repeat loop with a pause in the VA event handler. I'm wary of making this a 'while body_radius < 1' loop which could be never-ending. Maybe, 'repeat 5 times' and tell the user if the radius is still not set.
I wonder if there is a way to force the delay in EDDI for testing purposes. It would make sense to test for the radius not being set until after the event just to see what happens in the VA script but you'd need a way to do this reliably. Might be worth asking in the EDDI thread.

Personally, I'd put in a message to say that the radius was being determined if it came back as zero the first time and then a warning message after the timeout period (your 5 times loop), saying that since the radius could not be found the directions to the target could not be determined and the entire loop abandoned. Something along the Iines of:

"Waiting for planetary radius to be determined" and "Unable to determine planetary radius, direction to target cannot be given."

But that's just me.

By the way, I'd make the loop counter a variable that can be set in the VA script somewhere so that it can easily be tweaked by the commander to cope with slower computers.
 
Thank you these suggestions, I think it's time you took the 'in' out of 'incompetent'. At some point I will start referring to Landing Guidance as a package you developed with a little help from me. :)
 
This is very cool.

Hard coding the lat/long into the VA command is a bit klunky and provides an opportunity for improvement. 😉

Thinking about what it would take to add a tab to EDDI for entering/bookmarking POIs and saving in a local json for access via speech responder scripts or VA commands.
 
This is very cool.

Hard coding the lat/long into the VA command is a bit klunky and provides an opportunity for improvement. 😉

Thinking about what it would take to add a tab to EDDI for entering/bookmarking POIs and saving in a local json for access via speech responder scripts or VA commands.
You can probably tell from my earlier posts that I'm more familiar with VA than with EDDI; I started using EDDI just for the events it exposes to VA, so it seemed obvious to me that I should define destinations in VA commands. If there's a better way I'd like to know. Whether it's a VA command or an EDDI tab (I don't know what that is yet), don't you end up having to type in the latitude, longitude, and body name?

The use case that prompted me to start this project is that of an expedition with predefined waypoints and meet-up locations; my desire is to enable an expedition member to create a set of destinations, rather like bookmarks in the galaxy map, that the explorer can select and use.
 
This is very cool.

Hard coding the lat/long into the VA command is a bit klunky and provides an opportunity for improvement. 😉

Thinking about what it would take to add a tab to EDDI for entering/bookmarking POIs and saving in a local json for access via speech responder scripts or VA commands.
Now that's an interesting idea. It is a shame that the EDDI interface is not available when it is running as a VA plugin. I'm not sure how you would enter or edit new POI data without soothing VA down first.

It should be fairly feasible to input lat and long as speech, there are several examples of such elsewhere...
 
You can probably tell from my earlier posts that I'm more familiar with VA than with EDDI; I started using EDDI just for the events it exposes to VA, so it seemed obvious to me that I should define destinations in VA commands. If there's a better way I'd like to know. Whether it's a VA command or an EDDI tab (I don't know what that is yet), don't you end up having to type in the latitude, longitude, and body name?

The use case that prompted me to start this project is that of an expedition with predefined waypoints and meet-up locations; my desire is to enable an expedition member to create a set of destinations, rather like bookmarks in the galaxy map, that the explorer can select and use.
I use VA as an interface to various switches so I'm not going to be able to run EDDI as a standalone application. I'll be looking for ways to do things with VA as the interface rather than the other way round.
 
Now that's an interesting idea. It is a shame that the EDDI interface is not available when it is running as a VA plugin. I'm not sure how you would enter or edit new POI data without soothing VA down first.

It should be fairly feasible to input lat and long as speech, there are several examples of such elsewhere...
It may be possible to input co-ordinates using speech, although POIs are often quoted to four decimal places and it may be frustrating if you can't accurately capture the exact numbers. Also, the Landing Guidance needs the full name of the target body and speaking 'Eol Prou RS-T d123-5 a 1 a' or whatever is probably not feasible, which comes back to typing, and if you're typing that you might as well type the lat and long. Still open to ideas.
 
EDDI tab (I don't know what that is yet)
Within EDDI, The Cargo Monitor, Crime Monitor, Mission Monitor, etc are 'tabs'.

don't you end up having to type in the latitude, longitude, and body name
Not necessarily. For somewhere you haven't yet been, then yes, manual entry would be required. For bookmarking a present location, then that's already available.

Depends on how elaborate you want to get. You could use Friend, Wing, Squadron chat to send or automatically intercept/store coordinates, as EDDI has access to chat journal events.
 
Last edited:
I use VA as an interface to various switches so I'm not going to be able to run EDDI as a standalone application. I'll be looking for ways to do things with VA as the interface rather than the other way round.
EDDI window is available from VA. You can also call/run EDDI speech responder scripts from VA.
 
You can probably tell from my earlier posts that I'm more familiar with VA than with EDDI; I started using EDDI just for the events it exposes to VA, so it seemed obvious to me that I should define destinations in VA commands. If there's a better way I'd like to know. Whether it's a VA command or an EDDI tab (I don't know what that is yet), don't you end up having to type in the latitude, longitude, and body name?

The use case that prompted me to start this project is that of an expedition with predefined waypoints and meet-up locations; my desire is to enable an expedition member to create a set of destinations, rather like bookmarks in the galaxy map, that the explorer can select and use.
It should be possible to set up a few VA scripts that would allow the user to enter the coordinates. The user would say "latitude [minus] one five three point eight four two two one longitude [minus] four nine point seven one three" (or something of the sort) and the scripts would set two VA variables LAT and LONG to the spoken numbers.
 
It may be possible to input co-ordinates using speech, although POIs are often quoted to four decimal places and it may be frustrating if you can't accurately capture the exact numbers. Also, the Landing Guidance needs the full name of the target body and speaking 'Eol Prou RS-T d123-5 a 1 a' or whatever is probably not feasible, which comes back to typing, and if you're typing that you might as well type the lat and long. Still open to ideas.
Ah I see. I'm thinking of arriving at a destination, such as the planet upon which Dav's Hope resides and then entering the desired coordinates to get there. I can see a use for both methods especially if you could then say 'save coordinates as waypoint 1' and have it enter those into the EDDI system that Hoodathunk is contemplating.
 
For bookmarking a present location, then that's already available.

Depends on how elaborate you want to get. You could use Friend, Wing, Squadron chat to send or automatically intercept/store coordinates, as EDDI has access to chat journal events.
These feel like enhancements for a later release - and I'm grateful for the suggestions. In the first instance I would prefer to solve the simple problem that many commanders have of putting their ship down at a given location on a given body.
 
It is?

You can?

I must have misunderstood something then. Better and better.
Yup.

Code:
Execute external plugin, 'EDDI 3.4.2-b1' and wait for return
With 'configuration' in the context for opening the EDDI window.

Have you looked at the EDDI.vap commands, included with EDDI?
 
Ah I see. I'm thinking of arriving at a destination, such as the planet upon which Dav's Hope resides and then entering the desired coordinates to get there. I can see a use for both methods especially if you could then say 'save coordinates as waypoint 1' and have it enter those into the EDDI system that Hoodathunk is contemplating.
I like the 'save coordinates as waypoint' idea.
 
These feel like enhancements for a later release - and I'm grateful for the suggestions. In the first instance I would prefer to solve the simple problem that many commanders have of putting their ship down at a given location on a given body.
Only the saving to the EDDI thing. The first bit is going to be very useful, just speaking in the lat and long, and I've already started work on it. I'll test it out and let you know how it goes.
 
Yup.

Code:
Execute external plugin, 'EDDI 3.4.2-b1' and wait for return
With 'configuration' in the context for opening the EDDI window.

Have you looked at the EDDI.vap commands, included with EDDI?
I didn't know that there were any. I'll go have a poke around. Thanks.
 
The EDDI Voice Attack Integration Wiki is your friend. :)

 
Top Bottom