To be safe, I delete the EDDI folder in the /VoiceAttack/Apps folder, but that's it.
Navigate to your User folder and goto /AppData/Roaming/EDDI ... within the EDDI folder you'll find a 'personalities' folder. Copy it somewhere safe.
- Status
To be safe, I delete the EDDI folder in the /VoiceAttack/Apps folder, but that's it.
Navigate to your User folder and goto /AppData/Roaming/EDDI ... within the EDDI folder you'll find a 'personalities' folder. Copy it somewhere safe.
Thx for the info.
There are a number of player journal events that don't appear to have been fully implemented yet and that players might want to hook into to make their shipboard AI more aware. I've created a summary below.
Are there plans to implement any of the following?
Combat
- 5.2 CapShipBond (do you know what sorts of events currently trigger this, if any?)
- 5.6 FactionKillBond
- 5.12 PVPKill
- 8.26 RedeemVoucher
Exploration
- 6.1 Scan (many parameters have been implemented but not all?)
- 10.11 JetConeBoost (react to FSD supercharge complete)
- 10.12 JetConeDamage (report on damaged modules after a supercharged FSD jump?)
Crafting
- 6.2 - 6.4 Material Collected / Discarded / Discovered (Add parameter for material category to segregate different kinds of materials?)
- 8.9 EngineerApply
- 8.10 EngineerCraft (Would be very helpful for tracking materials/commodities available and consumed during crafting)
- 8.11 EngineerProgress
- 8.32 ScientificResearch (track engineering materials contributed towards a goal)
Modules
- 8.12 FetchRemoteModule
- 8.13 MassModuleStore
- 8.18 ModuleBuy
- 8.19 ModuleRetrieve
- 8.20 ModuleSell
- 8.21 ModuleSellRemote
- 8.22 ModuleStore
- 8.23 ModuleSwap
Missions
- 8.13 MissionAccepted (add missing optional parameters for targets, destinations, and passengers?)
- 8.16 MissionCompleted (add missing optional parameters for targets, destinations, passengers, commodity rewards, etc?)
Misc.
- 9.1 - 9.9 Various powerplay events
- 10.1 ApproachSettlement
- 10.5 - 10.7 Various data scanned events
- 10.24 - 10.26 Various Wing events
Note: I imagine that 8.2 BuyDrones and 8.33 SellDrones are the limpets events?
Thanks!
Are there plans to implement any of the following?
Combat
- 5.2 CapShipBond (do you know what sorts of events currently trigger this, if any?)
- 5.6 FactionKillBond
- 5.12 PVPKill
- 8.26 RedeemVoucher
Exploration
- 6.1 Scan (many parameters have been implemented but not all?)
- 10.11 JetConeBoost (react to FSD supercharge complete)
- 10.12 JetConeDamage (report on damaged modules after a supercharged FSD jump?)
Crafting
- 6.2 - 6.4 Material Collected / Discarded / Discovered (Add parameter for material category to segregate different kinds of materials?)
- 8.9 EngineerApply
- 8.10 EngineerCraft (Would be very helpful for tracking materials/commodities available and consumed during crafting)
- 8.11 EngineerProgress
- 8.32 ScientificResearch (track engineering materials contributed towards a goal)
Modules
- 8.12 FetchRemoteModule
- 8.13 MassModuleStore
- 8.18 ModuleBuy
- 8.19 ModuleRetrieve
- 8.20 ModuleSell
- 8.21 ModuleSellRemote
- 8.22 ModuleStore
- 8.23 ModuleSwap
Missions
- 8.13 MissionAccepted (add missing optional parameters for targets, destinations, and passengers?)
- 8.16 MissionCompleted (add missing optional parameters for targets, destinations, passengers, commodity rewards, etc?)
Misc.
- 9.1 - 9.9 Various powerplay events
- 10.1 ApproachSettlement
- 10.5 - 10.7 Various data scanned events
- 10.24 - 10.26 Various Wing events
Note: I imagine that 8.2 BuyDrones and 8.33 SellDrones are the limpets events?
Thanks!
The problem with cockpit breach event is that there's no way of knowing when to stop the countdown. It is something that was asked for but we haven't obtained a suitable event.
Regarding upgrades: from one version of EDDI 2 to another you should just download the new version and install it. EDDI will handle any changes that are needed to the configuration files.
New version works fine as far as i can see. Had no problems installing it. Shipnames are saved again [up]
Hmm... dont know if i understand it right. Is there no event happening for EDDI to know when to stop the countdown? What about the docking request? Again not sure i got this right.
Maybe then not a countdown but instead an anouncement of time left. Just in the moment the cockpit breaches.
like: breach<>EDDI checks<>lifesupport failure in<>Anouncement of time left, according to installed lifesupport module. end.
^^if that makes sense.
Well anyhow, for now i will make something like: "Lifesupport failure imminent" thats not so cool but at least EDDI says something
docking events seem to be working very well atm
![Cmdr Delmonte[VR]](https://forums-cdn.zaonce.net/data/avatars/m/82/82957.jpg?1711998379){kind=avatar}
Nope not server lag this time ! (For a change) don't know why or what but, uninstalled, removed ALL EDDI folders and re installed, all working fine, (Though it forgot my ship names after i re entered them, will check that again tonight)
-
In short its now working fine again !
(Happy cookie) o7A lot of these are in place but not with the same name. For example, taking the combat ones:
- CapShipBond and FactionKillBond are represented in the 'BondAwardedEvent'
- PVPKill is represented in the 'KilledEvent'
The reason why a lot of these have been renamed is because there are often multiple FD events that I consider better as a single logical event (e.g. the award of a bond) or single FD events that I consider better as multiple logical events (e.g. Scan becomes BodyScannedEvent and StarScannedEvent, because they're fairly different in terms of the information provided and what can be done from it). Alternatively it's to allow grouping of events by name (for example ScientificResearch is in as MaterialDonatedEvent, to fit with all of the other Material*Event that are already there).
Some other items are those where I was waiting for bug fixes that never came (for example with wings there is no way of knowing when a player leaves your wing, and modules where there were some missing field names), or I just ran out of time/willpower to add them all in (you'll note that there are more missing events for entries towards the end of the manual than the beginning). And some I just had no idea what they did due to lack of examples (e.g. ApproachSettlement - when does it trigger, when does it not?)
I'll take requests for any additional items if they have a decent justification behind them and rationale for using them, but a lot of the remaining ones I consider next-to-useless in terms of what EDDI does today.
Nope not server lag this time ! (For a change) don't know why or what but, uninstalled, removed ALL EDDI folders and re installed, all working fine, (Though it forgot my ship names after i re entered them, will check that again tonight)
-
In short its now working fine again !
Are you possibly a prolific explorer? It might be that the local database was getting clogged up with large numbers of systems and taking a while to update (although anything in the seconds range rather than milliseconds does sound excessive...)
Yep
It does sound like it's a database issue then. I'll add some indices in there for the next release that should speed things up.
That would be great ! Thank you
Thank you
I've made something similar in VoiceAttack. Haven't had a canopy breach since but i've tested it by turning off Lifesupport and it seems to work. In VA as soon as I turn off Lifesupport I say "Lifesupport off" and my AI tells me I have 10 minutes oxygen left (it checks my installed Lifesupport grade). Then it notifies me after I've reached 75%, 50%, 25%, 1 minute, 30 seconds, 10 seconds and then says death is imminent. When I turn Lifesupport back on (or when I enter a station) I say "Lifesupport on" and it stops the countdown.
Now I've integrated it with EDDI and it should start automatically when my canopy is breached. I tested this with the Undocked event and as soon I undocked the countdown started so that seems to work. It stops when I dock. Now I just have to wait for a canopy breach
Maybe I'll try with a cheap Sidewinder.
@OP thanks for the app. I had a little dabble last night after I came across your thread. struggled with it at first to get it working. someone mentioned I needed to import profile from ur app into VA. (big mistake). could not get it to give me any response apart from jumping from system and docking. however it would not give me any info on markets, scanning bodies, I like things to be working so, 6hrs later I went to bed. 7am.. lol I am totally braindead now as I type this so forgive me!
I am very impressed with it. shame I cant rep you more than +1
I also cant wait to set some commands up. though I am a novice/noob here. I can set them up in VA so I will give it a good go.
back to point: after removing the EDDI profile from my profile for VA it was working correctly at stations, it was now giving me market data. it was still not giving me any data on bodies I lock on too or scan!
your app in VA is online and EDDI status is operational.
can anyone help fix it for me. thanks
I am very impressed with it. shame I cant rep you more than +1
I also cant wait to set some commands up. though I am a novice/noob here. I can set them up in VA so I will give it a good go.
back to point: after removing the EDDI profile from my profile for VA it was working correctly at stations, it was now giving me market data. it was still not giving me any data on bodies I lock on too or scan!
your app in VA is online and EDDI status is operational.
can anyone help fix it for me. thanks
Last edited:
{TXT:Ship frame shift drive class} doesn't seem to be populating with anything
{TXT:Ship frame shift drive grade} works fine
{TXT:Ship frame shift drive grade} works fine
It's {INT:Ship frame shift drive class} I think.
Last edited:
If you are integrating with VoiceAttack (which isn't necessary, by the way) then you should read through the instructions at https://github.com/cmdrmcdonald/EliteDangerousDataProvider/blob/master/VoiceAttack.md#using-eddi-with-voiceattack and the troubleshooting guide at https://github.com/cmdrmcdonald/EliteDangerousDataProvider/blob/master/TROUBLESHOOTING.md These should give you a starting point.
Note that specifically regarding scanning bodies: there is no event generated if you don't have a detailed surface scanner on-board and enabled.
Note that specifically regarding scanning bodies: there is no event generated if you don't have a detailed surface scanner on-board and enabled.
I've made something similar in VoiceAttack. Haven't had a canopy breach since but i've tested it by turning off Lifesupport and it seems to work. In VA as soon as I turn off Lifesupport I say "Lifesupport off" and my AI tells me I have 10 minutes oxygen left (it checks my installed Lifesupport grade). Then it notifies me after I've reached 75%, 50%, 25%, 1 minute, 30 seconds, 10 seconds and then says death is imminent. When I turn Lifesupport back on (or when I enter a station) I say "Lifesupport on" and it stops the countdown.
Now I've integrated it with EDDI and it should start automatically when my canopy is breached. I tested this with the Undocked event and as soon I undocked the countdown started so that seems to work. It stops when I dock. Now I just have to wait for a canopy breach
Hmm... is there an easy way for you to explain this in detail?
Cause i dont know how i can do something like that. sry...
i am willing to test it ingame if you want
Hmm... is there an easy way for you to explain this in detail?
Cause i dont know how i can do something like that. sry...
i am willing to test it ingame if you want
No "easy" way to explain since I made it with trial and error but I've exported the commands to a vap file you can import into your own VA-profile.
You can find it here: https://dl.dropboxusercontent.com/u/9590837/Lifesupport-Profile.vap
It contains four commands:
Lifesupport off - this is the command with the countdown.
Lifesupport on - this just Kills the Lifesupport off command and thus the countdown.
((Eddi Cockpit breached)) - This command is executed when the event Cockpit breached occurs
((Eddi Docked)) - This command is executed when the event Docked occurs
In Eddi's Speechresponder I've created 2 new scripts:
"Cockpit breached JP" - This is an empty script which is called in the VA command. I've unchecked the "Cockpit breached" script.
"Docked JP" - This is the script which is called in the VA command. I just copied the contents of the original "Docked" script to this one and unchecked the original "Docked"
If you've done all this (not sure if it will work because I've never exported a partial profile for someone else but me to use) you could try it out by first just saying "Lifesupport off". This should check the lifesupport you have onboard and begin the countdown with the number of minutes it has.
If that works then next time you're canopy breaks it should start the countdown until you dock or die
- Status