VoiceAttack-profiles
VoiceAttack-profiles copied to clipboard
Odyssey compatibility
So, I have a major problem: https://forums.frontier.co.uk/threads/horizons-odyssey-compatibility.574677/
Since playing the game will require switching between Odyssey and Horizons for a lot of players, at least until they merge the engine update / UI changes / planetary tech changes, I would have to support both modes simultaneously, and do UI interactions depending on which one is running.
First of all, I will only ever do this if EDDI adds some kind of state variable to check it. I am not going to start looking at the game’s journals to find it out myself.
Second of all, I might just go “fuck Odyssey” until they get their shit together, considering I’m personally not going to buy it until then, and that I’m doing this in my free time.
It looks like it’s exactly like I feared (towards the end there): https://forums.frontier.co.uk/threads/horizons-odyssey-compatibility-further-details.575005/
If I want to bring Odyssey compatibility, I will have to support 2 different UIs.
Fortunately I do not have to make a decision on that because I straight up do not own Odyssey and won’t for the foreseeable future; that means I literally will not have access to the new UI and cannot work on Odyssey compatibility.
Until further notice, there will be no Odyssey compatible version of the profiles.
Feel free to use them anyway, but UI-related commands can and probably will break.
Totally understandable/justified decision.
I will only ever do this if EDDI adds some kind of state variable to check it. I am not going to start looking at the game’s journals to find it out myself
In case you do ever decide to tinker, this is from today's EDDI 4.0.0-b1 release notes.
Added boolean values for odyssey and horizons game states
In case you do ever decide to tinker, this is from today's EDDI 4.0.0-b1 release notes.
Added boolean values for odyssey and horizons game states
Yeah, I’ve known.
I guess in case I get bored I can go ahead and at least gate the UI things that people report broken.
Update: I’m basically no longer playing Elite. That means that new features (e.g. feet controls) are highly unlikely to ever happen. If/when they merge Horizons players into the Oddity client, I might do a compatibility release for that.
I’m still working on Elite-related project for fun sometimes; see recent commits 😬
The Great Merge™ is upon us: https://www.elitedangerous.com/news/update-13-narrative-and-access-40
But also it’s not, the old client will still be available. So apart from “technically I can load into the Oddity client now” the situation for me has not changed, I would still have to support both clients in the profiles.
Right now I still don’t plan on doing that. At least not in my spare time. So as it stands there is not going to be Oddity compatibility (neither new UI nor any added on-foot stuff) until console / Horizons client EoL.
Considering the latest bait & switch (Horizons was supposed to get the Proteus Wave aftermath content, but didn’t) and the fact that there are actually things happening again in Elite (4.0), I might actually switch to 4.0 when it comes out if performance permits; and subsequently switch this from Horizons (3.8) to 4.0 (still not with Odyssey features since I still won’t buy Odyssey).
Then again, right now (see “bait & switch”) I might also stop playing entirely, so … no final word on this yet.
I guess with how hard they have fucked 3.8 I should test out 4.0 over the weekend and then have a decision.
There is still going to be a release w/o compatibility just for the sake of #159.
Going to leave this comment as my rolling list of changes as I play Odyssey. I did not play this game prior to Odyssey, so I am using my best guess based on how things are working during my gameplay; doing this to ease the pain of converting this to Odyssey as it's a phenomenal tool.
EliteAttack.EDDI Docked
update line 5 to Pause 1.3 seconds
EliteAttack.EDDI Docked
add after line 5 Press variable key(s) [edUI_Up] and hold for 0.1 seconds and release]
SpanshAttack.targetNextNeutronWaypoint
update line 7 to press edUI_Up
(Is this command supposed to auto-plot?)
So first of all, if you change commands for your own needs you should follow https://alternerdtive.github.io/VoiceAttack-profiles/configuration/general/#adding-commands
If you want to make contributions you’ll have to fork this repository, create a new branch off devel
and submit a pull request. Since .vap
files aren’t great for versioning you should probably include a manual diff between the commands.
Anything related to Odyssey can’t just be flat out changes to commands, there will have to be a conditional change for when you are actually running the 4.0 client. Otherwise it breaks for 3.8. AFAIK EDDI has a variable that you can check for that.
(Is this command supposed to auto-plot?)
No, just focus the system. The reason is simple; the further away the target system is the longer it takes to move the map selection there. There is no way to detect when it’s finished.