Ooh, good spot. I'll fix that for the next release.
- Status
Ooh, good spot. I'll fix that for the next release.
jgm,
In my ongoing saga to be able repeat the landing pad location following the initial 'docking request' event, I did a more thorough read of the Cottle documentation with regards to IStore objects, in the context of passing event objects to the event driven EDDI speech responder script calls. I think I finally get it now... IStore objects are not passed to user-called speech responder scripts.
With this new found understanding, acknowledgment that Voice Attack is severely hamstrung in its inability to pass / manipulate object, arrays, etc, the arduous nature of 'flattening' objects for use in Voice Attack, but with there being a significant gap in what users able to do in a Cottle template... My request would be to:
1. Make each event object individual and persistent between events and the associated data within updated with each new event... possibly already the case?
2. Allow users to also pass the name of an event object to be used as the IStore object to a user-called speech responder script.
For example:
Set Text [Script] to 'User written docking granted'
Set Text [Event] to 'docking granted'
Execute external plugin, 'EDDI 2.0.11' and wait for return
obviously, with:
context = speech
Text variables = Script;Event
IMHO, this would go along way for users being able to utilize the full power of Cottle scripting in EDDI.
Thanks for reading.
In my ongoing saga to be able repeat the landing pad location following the initial 'docking request' event, I did a more thorough read of the Cottle documentation with regards to IStore objects, in the context of passing event objects to the event driven EDDI speech responder script calls. I think I finally get it now... IStore objects are not passed to user-called speech responder scripts.
With this new found understanding, acknowledgment that Voice Attack is severely hamstrung in its inability to pass / manipulate object, arrays, etc, the arduous nature of 'flattening' objects for use in Voice Attack, but with there being a significant gap in what users able to do in a Cottle template... My request would be to:
1. Make each event object individual and persistent between events and the associated data within updated with each new event... possibly already the case?
2. Allow users to also pass the name of an event object to be used as the IStore object to a user-called speech responder script.
For example:
Set Text [Script] to 'User written docking granted'
Set Text [Event] to 'docking granted'
Execute external plugin, 'EDDI 2.0.11' and wait for return
obviously, with:
context = speech
Text variables = Script;Event
IMHO, this would go along way for users being able to utilize the full power of Cottle scripting in EDDI.
Thanks for reading.
Last edited:
Remove EDDI folder from user/APPdata, use uninstaller in the VA/Apps/Eddi folder ... reinstall. Then just input your informations again in EDDI or if you saved your EDDI settings copy those to Appdata (but i did not do that because i thought my credentials were f'ed). These are also the steps you should take everytime a new version is released by the awesome jgm if you want a clean EDDI.
Inside EDDI events are asynchronous and transient entities; there's nowhere to make them persistent, and even if there were there's no guarantee that the right event would be present at any given moment.
Passing information from VoiceAttack to scripts isn't something that I have found a sane way of doing, but I'll take another look and see if I can come up with something.
Thanks. I don't think I'm being melodramatic by saying that Cottle scripting is a shadow of its full potential without user variable passing, however minor.
For example, just the ability to pass one of each (Text, Small Int, Integer, Decimal, & Boolean) would be huge.
For example, instead of saying 'shutup' each time or manually turning off scripts, I could pass a boolean to test whether to run all (or only parts) of the script. Or I could pass the landing pad number and the station name to repeat the 'docking granted' info.
Last edited:
Was there not a 'log out' button on the companion app tab?
No, there was a spot to enter my password and a Next button (I think). Then when it failed it displayed the error reported but Logout only appears when you are successfully logged in.
So to be perfectly clear on the companion app tab my login name was present along with a blank input field that was obviously for a password and a Next button (I think it said next). Attempting to log in produced the reported error and left us with the same Username/password fields. There was no Logout button and no way to force reconnection to the app. Uninstall/reinstall forced that but obviously that's like using a sledgehammer.
Last edited:
Frontier API appears to be down... noticed last night when I first logged-in, still down this morning.
EDDI reporting "Failed to obtain data from Frontier server (READY)"
Confirmed via EVA phone app also unable to connect
EDIT: Back up now... strange
EDDI reporting "Failed to obtain data from Frontier server (READY)"
Confirmed via EVA phone app also unable to connect
EDIT: Back up now... strange
Last edited:
It's on the issues list as an enhancement, but not something I'm working on at the moment. I have some items to consider on this front.
It's still down for me. I haven't been able to connect to the companion app from EDDI for a while now.
Last time i had this problem a clean reinstall of EDDI and setting it up again (no credentials copy) worked for me. Maybe it's worth a try?
Companion API is on Frontier's side, I'm afraid. Tempting though it would be to hunt it down and kick it, I don't think Frontier would be best pleased.
(The EDDI server, which provides system information, is fine).
Is there any EDDI command to switch personality by any chance? I went through the documentation but didn't see anything of the sort. I was making two profiles, one more verbose and the other less so or with different information on certain events (like system transit, docking, etc), and was looking for a convenient way of switching to each profile. If that's not a feature, do you have any tips as to how I would go about doing the above?
Loving EDDI but 2.0.11 has had a funny bug happen at least for me. I landed on a planet to farm some arsenic and after about an hour I recalled my ship again. What happened after that as I warped into another system was that EDDI said "Your Test Buggy is jumping into BLAEBLAE system" and after that every time I scoop she says "Your test buggy has been refueled".
Is this yet another of those things that are fixed with a relog?
Is this yet another of those things that are fixed with a relog?
Last edited:
You can do it with voice attack. Export 2 Profiles with the different Infos. Than you can switch by importing the desired profile to voice attack.
This is an issue with the Frontier API, where if you start the game in a buggy or fighter then you are marked as being in that "ship", but when you return to your mothership the API doesn't provide details of which ship you are now in.
Hence you're stuck in whatever you started in (until you swap ships).
I can probably find a way to work around it, but haven't had a chance yet. In the meantime if you are back in your mothership you should be able to shut down and restart EDDI for it to pick up the updated information.
- Status