The iRacing development model was always the right one to take. It takes time to develop, test and package all the code and content to support a quarterly release. iRacing have long term developments (AI, rain, tire model etc.) where they may or may not slip a quarter with a release, and they rarely tell us ahead of time what is going to be in a specific release unless they are really sure of it. I suspect this will happen with rain, which will affect nearly everything in the same way as Dirt and new surface model did.
If we look back to past release history with rF2, especially content, we can see that this was already in fact what was happening. Though the releases were December (to hit Xmas buying), May/June (to hit peak racing season) and September. This fell apart in the last couple of years but was getting quite reliable. I found the Roadmaps were useful for anticipating this. In the "release when ready" model, Roadmaps cease to be useful.
MSGS has to perform quarterly updates to Wall Street. When stating you have a new license, like for IndyCar, that is a significant (i.e. "material") event which can affect the stock price and needs to be controlled. Licensing a single new track or car for rF2 isn't, and so there should be no restrictions in announcing such. With the upcoming IndyCar release, the CEO already stated on the earnings call they were going to do an esports series in Q4 using rF2 as the platform, so there was nothing stopping S397 pre-announcing this because it was already public. S397 need to sort out this messaging; its badly wrong now.
The upside for a quarterly release, is that there's the inevitable "push"/"crunch" to get stuff out to hit what is usually an arbitrary deadline. And we all know, quality suffers when you do this oftentimes (see: Ignition release, clearly wasn't ready but had to hit Xmas release). That said, a specific release window does focus the minds of the devs. I've seen it in other Enterprise software; either for a single client or for global releases, which we used to do every 6 months and is arguably an even better option. If you don't have this to focus things, stuff tends to drift and not get completed. I think we see clear evidence of this at S397. When focused on something important, like Virtual LeMans, stuff gets done (like our GTE Ferrari). If not, we get 2 years delay in a UI reskin.
If we look back to past release history with rF2, especially content, we can see that this was already in fact what was happening. Though the releases were December (to hit Xmas buying), May/June (to hit peak racing season) and September. This fell apart in the last couple of years but was getting quite reliable. I found the Roadmaps were useful for anticipating this. In the "release when ready" model, Roadmaps cease to be useful.
MSGS has to perform quarterly updates to Wall Street. When stating you have a new license, like for IndyCar, that is a significant (i.e. "material") event which can affect the stock price and needs to be controlled. Licensing a single new track or car for rF2 isn't, and so there should be no restrictions in announcing such. With the upcoming IndyCar release, the CEO already stated on the earnings call they were going to do an esports series in Q4 using rF2 as the platform, so there was nothing stopping S397 pre-announcing this because it was already public. S397 need to sort out this messaging; its badly wrong now.
The upside for a quarterly release, is that there's the inevitable "push"/"crunch" to get stuff out to hit what is usually an arbitrary deadline. And we all know, quality suffers when you do this oftentimes (see: Ignition release, clearly wasn't ready but had to hit Xmas release). That said, a specific release window does focus the minds of the devs. I've seen it in other Enterprise software; either for a single client or for global releases, which we used to do every 6 months and is arguably an even better option. If you don't have this to focus things, stuff tends to drift and not get completed. I think we see clear evidence of this at S397. When focused on something important, like Virtual LeMans, stuff gets done (like our GTE Ferrari). If not, we get 2 years delay in a UI reskin.