No, there weren't. There's exactly one client in the Steam package. The Horizons DLC doesn't install anything, it's just a DRM license token to unlock Horizons features in the client.
Wrong. This may be the case NOW, but for much of Horizons' lifespan, and certainly at launch, there were two completely different packages, a 32 bit version and a 64 bit version. Horizons was the 64 bit version, vanilla Elite, which was built on the 32 bit client, was its own client. It wasn't just a couple of DRM flags. One of the reasons I remember this is because for a while, the 32 bit version had shorter hyperspace jump times and I would often switch over to the 32 bit client when doing long distance multi-jump travel.
elite-dangerous.fandom.com
You are confusing codebases with target platforms. All platform builds of ED (for Windows 32/64, Xbox, PS4...) have been and continue to be generated from the same unified codebase. There has never been a separate Horizons client for any of those platforms. The fact that they stopped shipping updates to the 32bit Windows client at some point doesn't make it a separate client, just an older one. That's why builds have version numbers: so you can tell what version of the codebase they were compiled from.Wrong. This may be the case NOW, but for much of Horizons' lifespan, and certainly at launch, there were two completely different packages, a 32 bit version and a 64 bit version. Horizons was the 64 bit version, vanilla Elite, which was built on the 32 bit client, was its own client. It wasn't just a couple of DRM flags. One of the reasons I remember this is because for a while, the 32 bit version had shorter hyperspace jump times and I would often switch over to the 32 bit client when doing long distance multi-jump travel.
Version history
Elite Dangerous is the definitive massively multiplayer space epic, bringing gaming's original open world adventure to the modern generation with a connected galaxy, evolving narrative and the entirety of the Milky Way re-created at its full galactic proportions. Here is the version history of...No 32-Bit launch option for E:D Horizons :: Elite Dangerous General Discussions
I just bought Horizons and redeemed the code that was given. Once i started the launcher up i saw that there was no 32-Bit launch option for Horizons. Have the developers forgotten to add this to the launcher or is it hidden? Please help.steamcommunity.com
Horizons - Elite Dangerous 64-bit vs 32-bit Client Files - Two commander accounts
Because of reasons, I have ended up with two different commander accounts. My main one has the expansion pass, and thereby Horizons and the other one doesn't. When I first logged in with my main commander, I got a blue Install button and was able to download Horizons [64-bit], which also made...forums.frontier.co.uk
So here's what actually, really happened with Horizons: Frontier released a NEW, more advanced 64-bit client for Horizons, and continued to support the old existing client (which incidentally also ran on Mac) for a while. Then they dropped support for all 32-bit versions of the game completely.
Here's what could happen with Odyssey: Frontier releases a NEW, more advanced client for Odyssey, and continues to support the old existing client (which incidentally also supports VR) for a while. Then they drop support for all older (VR) versions of the game completely.
So to quote a wise, wise, very insightful person:
And whose fault is that?
All this talk about a publisher-less development cycle and... they've gone to publishing business themselves and became what they didn't want to in the first place. This kinda reminds me of idealistic politicians who are then corrupted by power after finally being elected.As of 2019, total sales of PC-based VR is around 5 million (source: https://www.statista.com/statistics/671403/global-virtual-reality-device-shipments-by-vendor/). I would be surprised if sales are 300k as that is quite low (given that you can pick up ED on sale so cheaply (granted they may not be actually playing).I think more like 15%, even 10%
I can hardly imagine that out of 3 million copies sold (approximately), there are 300,000 people who have invested in VR.
If you click on the orange box top right that says DEV POST, you can very quickly get to the most recent Dev contribution without having to trawl ... each time you click DEV POST it takes you to the next and the next until it tells you that you've reached the most recent post.
5 million ? That's very few compared to the tens of millions of PCs sold each year.
It's a mystery indeed
No, the most likely - and almost certainly what "Odyssey will not be compatible with VR at launch" actually means - is when you launch Odyssey, VR will not work. That's the clean way to do it.
I'm not sure what difference you think this makes. Are you suggesting because base and horizons have VR, calling odyssey from the same client would mean VR must work as well? But we can load base and horizons without VR. I can have my VR headset connected and load the client and not load VR (depending on parameters, afaik, eg as drkai's edlauncher uses).You are confusing codebases with target platforms. All platform builds of ED (for Windows 32/64, Xbox, PS4...) have been and continue to be generated from the same unified codebase. There has never been a separate Horizons client for any of those platforms. The fact that they stopped shipping updates to the 32bit Windows client at some point doesn't make it a separate client, just an older one. That's why builds have version numbers: so you can tell what version of the codebase they were compiled from.
Mark my words: There will be no separate codebase made from scratch for the Odyssey client. How do I know? Because I've worked in software development, and I'm pretty sure the people at FD are not insane.
That really doesn't mean it.
![[PS4] Lorenzo Waringos](https://forums-cdn.zaonce.net/data/avatars/m/234/234580.jpg?1612617334){kind=avatar}
