I was not aware of today's delay till I actually opened that link.
Just shocking, they're talking about delivering the first update in a series planned for a whole year halfway through it. I don't know how they plan to keep on schedule unless there's no content in the other updates promised with Horizons (which would end Season 3 before it begins).
Worried about this.
I think there's a thread specifically on this.
But my view is that Frontier have never defined a season as a year., I tend to think this was probably intentional, specifically for the reason that in software dev land you cannot know in advance with 100% certainty how long something will take. With any decent sized project the unexpected always crops up however well planned you are, so the plan has to account for that with leeway, and at that point providing precise estimates isn't gonna be the best course of action because ultimately that's going to be misleading.
Remember when for Horizons Frontier kept saying "thanksgiving" and would not provide anything more specific.
So with 2.1 it's looking like an ~8 week run over. This in itself is not that big of an issue but in the context of a "season" it is a bit of a problem due to the expectations of how long a season would be.
My feeling is Frontier will bite the bullet on this one, they've already advertised 2.1/2.2/2.3/2.4 so this is what they'll deliver during season 2.
It's just that the notion of season is then likely to be extended a touch, possibly 14 months instead of 12?
Who knows though.
Frontier have constantly talked about the issue being dependencies, in that they cannot do A before B is in and that needs C and so on, so the order they do things is somewhat limited and defined by this.
It may well have been that season 2 as a whole is *heavily dependent* on 2.1 and that means a whole bunch of work up front.
Multicrew (2.2) and CMDR creation (2.3) are gonna need procedural face generation implemented, and since 2.1 contains that it seems the core of that will be in the codebase with this first update.
In that respect, due to the nature of getting all the dependencies in place being a huge amount of work, the work required for the season as a whole may well be disproportionately skewed to 2.1.
And so we may find 2.2/2.3 at least, possibly 2.4 are completed much quicker due to much of the underlying framework having already been done in 2.1.
Ship launched fighters, 2.4, seems like it might be heavily dependent on 2.2, I guess it's possible there 2.2 might take longer than 2.4?
I guess you could also take the point of view that if we get 14 months out of a season, well you've got your money's worth due to the increased amount of work that's gone into it. I mean frontier aren't gonna be lazing around right now doing nowt, they're gonna be working their butts off to hit a (possibly) overtight deadline.
I know people don't like delays but ultimately this means the the feature is to be improved, and that's a plus. I'd rather they delay than cut stuff. Just needs a bit of patience.
- - - - - Additional Content Posted / Auto Merge - - - - -
There is a few sayings in software development...
'The first 90% of the code accounts for the first 10% of the development time. The remaining 10% of the code accounts for the other 90% of the development time!'
'A computer lets you make more mistakes faster than any invention in human history–with the possible exceptions of handguns and tequila!'
'If it doesn't have to work you can meet any deadline!'
Doh yeah this put it much more succinctly that I did.
- - - - - Additional Content Posted / Auto Merge - - - - -
Aren't they talking about July now?
Sorry can you source this please?
Why do you think it's July?