Release EDDI - Windows app for immersion and more

Status
Thread Closed: Not open for further replies.
With my larger ships (32t tanks) the script works perfectly however in my smaller ones (Courier, Cobra, etc), I too get the 75% warning on every jump. When I isolate the variables, they seem to give the correct values so I'm looking into the decimal values now.
.
Also watch out for the "< 5" line. This is checking if you have less than 5 tons of fuel left. Some of my ships don't have 5t total :).

I'm checking it out now too while flying my Anaconda back from Maia to my home-system and I found it only uses the main tank for telling the percentages. I have one extra 32t tank aboard so 64t in total. It announces the remaining fuel correctly (like 58t after my first jump) but for the percentages it only looks at the main tank (32t) so the 25% depleted starts at 24t, 50% at 16t and 75% at 8t remaining. I'm thinking about making a VA routine to fix this since I don't think the extra capacity is available in the scripts.
 
I'm running the fuel code , but it's not giveine me any warnings, copied the code above... created New Script, called it Fuel Remaining, and pasted the above. Is that right ?
 
Last edited:

The 'event' variable is event-dependent and only exists for the duration of the script, so you can't use an event.* variable unless it's defined in the event itself (as per the bottom of the 'Variables' help file for your given event).
 
I'm thinking about making a VA routine to fix this since I don't think the extra capacity is available in the scripts.

Makes sense now. Got extra fuel tanks in all of my ships. Pls let me know if you can fix it.

I'm running the fuel code , but it's not giveine me any warnings, copied the code above... created New Script, called it Fuel Remaining, and pasted the above. Is that right ?

The code from my first post relating to this was incomplete. use the one from the second post and delete the unnecessary parts.
Or search for the original by Author also in this threat somewhere.
sry for causing confusion.

The 'event' variable is event-dependent and only exists for the duration of the script, so you can't use an event.* variable unless it's defined in the event itself (as per the bottom of the 'Variables' help file for your given event).

Ok i just understand that i tried to use a variable that didnt exist.
Nevermind...
This is to high for me. i cant follow you. I better stop distracting you guys so you can concentrate. ;)
 
Last edited:
Thank you, who was the author ?
NVM Found it
{set currentfuel to (event.fuelremaining / ship.fueltank)}

{Pause(2000)}

Entered System Space of {system.name}.

{Pause(1000)}

Your last Jump used up {Humanise(event.fuelused)} Tons of Fuel, leaving you with {Humanise(event.fuelremaining)} Tons remaining.

{if (event.fuelremaining) < 5:
Warning: Ships Fueltank almost depleted. Immediate course correction to a System with scoopable Stars or Refueling Stations is required.
|elif currentfuel <= 0.25:
Attention, Ships Fueltank 75% depleted. Fuelscooping the next viable Star is Advised.
|elif currentfuel <= 0.5:
Attention, Ships Fueltank 50% depleted.
}
 
Last edited:
I've been playing with the bounty awarded event variables to make a reminder that I have unclaimed bounties. It's ok that the faction isn't persistent, just that I have outstanding bounties to collect. It works ok, but I have to manually clear the event bounty variables when I turn in bounties. I see that there is a journal event when you turn in a bounty. Is it possible to add this event to EDDI so that the event bounty collected variable could be cleared in voice attack when the bounty turn in event is triggered?

The RedeemVoucher event doesn't give a faction for which the voucher is being redeemed, which is why I didn't bother implementing it.
 
Everytime i change system with EDDI 2 up it crashes. Did i mess it up somehow or is anyone else having this problem?

I've heard of this problem from a few people but haven't been able to track it down. What operating system are you using, and what voice? If you turn off phonetic speech (an option in EDDI's text-so-speech tab) does that fix the problem?
 
Makes sense now. Got extra fuel tanks in all of my ships. Pls let me know if you can fix it.

I've made a ((EDDI jumped)) command in VoiceAttack and you can find it here : https://dl.dropboxusercontent.com/u/9590837/Fuel-Profile.vap

It only warns you when your fuel is depleted to 50%, 75% and 95%.

To use it you should copy the command to your regular VA-profile and uncheck the Jumped script in Eddies Speechresponder (otherwise the two talk through one and other)
I've checked it and it worked for me (it was synchronous with the full-bar in the cockpit)
Don't blame me if you have to call the Fuel Rats though :)
 
Thank you, who was the author ?
NVM Found it
{set currentfuel to (event.fuelremaining / ship.fueltank)}

{Pause(2000)}

Entered System Space of {system.name}.

{Pause(1000)}

Your last Jump used up {Humanise(event.fuelused)} Tons of Fuel, leaving you with {Humanise(event.fuelremaining)} Tons remaining.

{if (event.fuelremaining) < 5:
Warning: Ships Fueltank almost depleted. Immediate course correction to a System with scoopable Stars or Refueling Stations is required.
|elif currentfuel <= 0.25:
Attention, Ships Fueltank 75% depleted. Fuelscooping the next viable Star is Advised.
|elif currentfuel <= 0.5:
Attention, Ships Fueltank 50% depleted.
}
I actually put this in my "Jumped" script so it activates after every jump. I do an "Occasionally(7..." on the line for how much fuel I have left in the tank but the warnings and cautions are always checked.
 
The 'event' variable is event-dependent and only exists for the duration of the script, so you can't use an event.* variable unless it's defined in the event itself (as per the bottom of the 'Variables' help file for your given event).

Thanks, this succinctly explains why calling the 'Docking granted' speech script from Voice Attack (via plugin) doesn't work. So the question begs... since station type isn't reported in the Journal log for a 'Docking granted' event, only in 'Docked' and 'Undocked' events, where are you getting it?

I'm assuming you're pulling via a downloaded copy of the EDDB json files and serving it up via your own EDDI server.

If so, a thought... would you consider adding a VA plugin command for us to query EDDB data for a named system or station and populate VA accessible variables? For example, a {TXT: Requested station type} or {TXT: Requested system X} variables.
 
Thanks, this succinctly explains why calling the 'Docking granted' speech script from Voice Attack (via plugin) doesn't work. So the question begs... since station type isn't reported in the Journal log for a 'Docking granted' event, only in 'Docked' and 'Undocked' events, where are you getting it?

I'm assuming you're pulling via a downloaded copy of the EDDB json files and serving it up via your own EDDI server.

If so, a thought... would you consider adding a VA plugin command for us to query EDDB data for a named system or station and populate VA accessible variables? For example, a {TXT: Requested station type} or {TXT: Requested system X} variables.

It's a nice idea but there is basically 0 chance of the Microsoft speech recognition system being able to work out what you asked for.
 
Ok got fuel working ! But cant get Volcanism to report when scanning a body, if anyone figures this out please let me know :) Currently at Jelly fish nebula and this would be very useful
in finding a planet worth landing on . o7
 
Log example, with the bit I am trying to get EDDI to say, during the body scanned event. [where is it]
.
{ "timestamp":"2016-11-13T17:43:48Z", "event":"Scan", "BodyName":"Jellyfish Sector LC-V c2-11 A 7", "DistanceFromArrivalLS":300.175140, "TidalLock":false, "TerraformState":"", "PlanetClass":"High metal content body", "Atmosphere":"", ]"Volcanism":"minor metallic magma volcanism", "MassEM":1.448887, "Radius":6782998.000000, "SurfaceGravity":12.551645, "SurfaceTemperature":196.006714, "SurfacePressure":54.631287, "Landable":true, "Materials":{ "iron":20.9, "nickel":15.8, "sulphur":14.8, "carbon":12.4, "chromium":9.4, "manganese":8.7, "phosphorus":7.9, "zinc":5.7, "cadmium":1.6, "niobium":1.4, "yttrium":1.3 }, "SemiMajorAxis":89986785280.000000, "Eccentricity":0.000172, "OrbitalInclination":-0.051560, "Periapsis":243.428497, "OrbitalPeriod":20983212.000000, "RotationPeriod":151442.046875 }
 
Last edited:
Thanks, this succinctly explains why calling the 'Docking granted' speech script from Voice Attack (via plugin) doesn't work. So the question begs... since station type isn't reported in the Journal log for a 'Docking granted' event, only in 'Docked' and 'Undocked' events, where are you getting it?

I'm assuming you're pulling via a downloaded copy of the EDDB json files and serving it up via your own EDDI server.

If so, a thought... would you consider adding a VA plugin command for us to query EDDB data for a named system or station and populate VA accessible variables? For example, a {TXT: Requested station type} or {TXT: Requested system X} variables.

The only way I've been able to get MS Speech Recognition to work with my "Plot Route To" VA command is to add each system into the Speech Recognition Dictionary with my personal inflections and pronunciations. It still only works about 80% of the time and is incredibly time intensive (i've only added about 50 systems in the bubble). To do this, I use the new Dictation function and tokens in VA.
 
Last edited:
I've made a ((EDDI jumped)) command in VoiceAttack and you can find it here : https://dl.dropboxusercontent.com/u/9590837/Fuel-Profile.vap

It only warns you when your fuel is depleted to 50%, 75% and 95%.

To use it you should copy the command to your regular VA-profile and uncheck the Jumped script in Eddies Speechresponder (otherwise the two talk through one and other)
I've checked it and it worked for me (it was synchronous with the full-bar in the cockpit)
Don't blame me if you have to call the Fuel Rats though :)

Tested this and it seems to give me the 50% warning but non of the others. Not entirely sure though. I keep playing some more with it.
Thanks man!!
 
It's a nice idea but there is basically 0 chance of the Microsoft speech recognition system being able to work out what you asked for.

That's not what I'm suggesting.

I'm suggesting a plugin command where, for example, 'Script' holds the name of the system or station and the context is something like 'QueryStation' or 'QuerySystem' and the result produces VA accessible variables, like the mentioned above.
 
That's not what I'm suggesting.

I'm suggesting a plugin command where, for example, 'Script' holds the name of the system or station and the context is something like 'QueryStation' or 'QuerySystem' and the result produces VA accessible variables, like the mentioned above.

Okay now I understand. It's possible to do, but what would you be doing it for? I'm a little wary of adding too much load to the server as it's only a little thing.
 
Log example, with the bit I am trying to get EDDI to say, during the body scanned event. [where is it]
.
{ "timestamp":"2016-11-13T17:43:48Z", "event":"Scan", "BodyName":"Jellyfish Sector LC-V c2-11 A 7", "DistanceFromArrivalLS":300.175140, "TidalLock":false, "TerraformState":"", "PlanetClass":"High metal content body", "Atmosphere":"", ]"Volcanism":"minor metallic magma volcanism", "MassEM":1.448887, "Radius":6782998.000000, "SurfaceGravity":12.551645, "SurfaceTemperature":196.006714, "SurfacePressure":54.631287, "Landable":true, "Materials":{ "iron":20.9, "nickel":15.8, "sulphur":14.8, "carbon":12.4, "chromium":9.4, "manganese":8.7, "phosphorus":7.9, "zinc":5.7, "cadmium":1.6, "niobium":1.4, "yttrium":1.3 }, "SemiMajorAxis":89986785280.000000, "Eccentricity":0.000172, "OrbitalInclination":-0.051560, "Periapsis":243.428497, "OrbitalPeriod":20983212.000000, "RotationPeriod":151442.046875 }

I don't think that EDDI picks up the volcanism information. It's on the list to do, but the info in the event doesn't tie in properly with the info in the journal so it'll require a bit of work to hunt down the various possibilities.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom