Kinda what I meantOnly critical one. That's the whole point of maintenance mode.


Kinda what I meantOnly critical one. That's the whole point of maintenance mode.
I wonder if the same argument would have been used if it was gimballed multicannons.One can not just "use other weapons" to the same effect.
If ,they roll out a fix,they have demonstrated how little they actually care about HorizonsIIRC that's a Horizons issue.
If so, deploying a fix will take extra time since Consoles patches are have to pass MS/Sony procedures.
Edit: they will not roll back the Update. But you can use other weapons until they deploy the fix
They didn't freeze dev for Horizon to focus on odyssey.
They did it because they couldn't bring Odyssey to console and it was too much work to maintain both build. As a result they can ignore horizon and work on Odyssey.
They froze Horizons to cut costs
Wait, what??
I thought they had stopped dev for consoles only, not Horizons as well.
What did I miss? When was this announced?
Elite Dangerous will continue on console as it is now together with critical updates, but we will focus on new content updates on PC on the post-Odyssey codebase.
I assume these are ships that have to be purchased in Horizons, such as the Krait. Some time ago, Frontier changed it so that you need to be in Horizons in order to switch into them. My brief contact with support about this pointless change suggested they were confused about the point of Horizon-exclusive ships - which ofc work just fine in the base game. You just had to have the DLC to buy them.In non-Horizons, only 17 of my 22 starships stored on my Fleet Carrier can be selected in the Shipyard (services menu shows 22).
Switching to Horizons, selecting from the full list, then switching back to non-Horizons was a workaround.
Update 11 Hotfix
We're looking to release a hotfix this week to address some of the issues discovered since the release of Update 11! We're aiming for the first half of the week for this hotfix right now, but we'll let you know concrete information soon. There shouldn't be significant downtime (think 15-30 minutes, not hours).
Realy hoping they dont break console builds trying to fix PC issues...might be better to not have a console hot fix at all...I'll cross my fingers, but not hold my breath that my cannons will be fixed with update.
As of 3308-03-21, Class 3 Fragment Cannons are still unusable and have been so for 6 days.
Presently I am making-do narrowly with Odyssey, still being well below the stated minimum hardware for the moment. I have found many small bugs with it in the meantime, potentially well-known already, though either way not so much a problem were I able to rely on Horizons. To list a few:
Some old bugs are still around, such as the Galaxy map having an artificial limitation which prevents searching for the h system (next to IC 4756 Sector TJ-Q c5-3).
- Night-vision highlights oneself, inside the starship.
- Night-vision ruins the small square portraits, including those of others.
- Night-vision looks much more jagged, especially on slightly off-horizontal surfaces, such as the wings of the Mamba as viewed from inside.
- Night-vision looks quite overdone with the highlighted edges, presumably due to much more model detail in Odyssey (models look lovely otherwise).
- Various effects and overlays draw atop each other weirdly in the wrong order, including explosions, beam laser shine, starport/carrier docking markers, and night-vision highlight.
- Own chaff is not visible from within the canopy (it should look like this).
- Supercruise sometimes passes through a planetary ring when low-waking close to the ring.
- The Transactions panel freezes when opening/navigating/closing, with time proportional to the number of bounty claims (around 1 second for 200 claims).
- In the Missions panel at a starport, the show/hide status of a faction can become inverted if toggled too quickly.
There, I beta-tested it.
Without any known comment about it from Frontier to be found, I can only assume that the forward direction will never fix them.
I posit that everything should revert to update 10 while the Fragment Cannon issue specifically is isolated.
I have no idea whether "voting" an issue changes anything. If it does, please do so here.
This was exactly my thought upon discovering a broken Horizons, but the observation of reality is:Considering frag cannons are a very popular module and a lot of people have spent a lot of time, effort and resources on mods, I doubt Fdev will just sit on this issue indefinitely.