ORIGINAL: Arjuna
I'm afraid there are others who would prefer I not make constant updates that keep slipping as they say this indicates vaporware.
Where'd you gather that? I've never seen ANY comment like that, and Adam's, Freeboy's or my posts in the general forum didn't suggest that either.
Sometimes I tend to think that you want to misunderstand things or to read between the lines, although there's nothing to see there. [:)] It's not my job to interpret their comments, but I can tell you that I -for one- never suggested something like that.
Also, I don't follow Adam where he says that he seems to feel rather bored by regular dev updates, like it turns the game into a well known piece of software, for him.
Freeboy hit the nail in the gen. forum:
ORIGINAL: freeboy
"It has such a great appeal, both the interest in the battle and the interest in this particular model that from purely a MARKETING perspective releasing a discussion about a game and then not having it be released is causing folks to respond negatively, if it was something less valued the negative feelings of dissappointment would not be there.."
It may not be easy for you as a programmer to walk on a fine line where it takes a good mix of building up anticipation and taking along customers (and keep them informed). People just tried to point that out, you shouldn't take it personal.
Also I'd like to think that we have a pretty good track record for delivering robust original titles. We've been doing so since 1985.
No doubt. Impressive record. That's rare in the software world.
Hopefully there won't be such a code-slip like in the stock version of COTA, in particular the arty-thing, which made the game so unenjoyable for me, that I did not pick up the game again until after the release of the first patch, which corrected that arty behaviour.
And to make sure you don't get this wrong now, I am not suggesting COTA was bug-ridden, but I am expressing that I could not enjoy the stock game (at all), because my personal play-style heavily depends on micromanagement of artillery units. If I can't plaster woods and river banks with arty shells, I get unhappy (unlike the enemy units). [;)]
That should mitigate against any vaporware fears. Regardless we will continue to provide regular progress updates and give our best estimates of release based on what we know at the time. Cheers
I don't think there are any fears like that. Comments from ppl rather aimed at the list of ETAs that started to disappoint some ppl after a while. I, for one, think that your dev updates coupled with screenshots are very informative and make ppl look forward to the release. Some people may feel that the ETAs take away from that fun, though, as your "estimates" tend to be a tiny bit off, I think. *cough*. [;)]
ORIGINAL: Arjuna
...Moreover I think it also educates users that developing complex software that involves a high proportion of orginal R & D, invariably hits snags and problems which can't be seen in advance.
Yeah, a good attitude, but we have a saying here, sometimes "less is more" ("weniger ist mehr"), means less (ETAs) would do more good PR-wise, at times.
Re: R & D : Hist. data in PG titles appears to be well researched.
What I found to be quite amusing and surprising, though, that Simo, when he gave a lecture (in the games.historical newsgroup) on how PG enhanced historical accuracy and realism of the upcoming installment, pointed out that PG ("we") had researched how much fuel had been fed/allocated to the Bulge theater.
Quite amusing, if I think about the fact that I had to invest some 2-3 days to verify and actually prove (in order to convince you of) what most Germans with some historical interest (not necessarily with an interest in military details) know:
That lack of fuel appeared to be the major problem during the course of the battle, that quite some armored units started out with 60% fuel in their tanks, that then the distribution often failed, that deliveries came late, or that they were even horse-drawn (starting around 18th/19th of December) later on. I even delivered the exact total amount of fuel (in gallons IIRC) that had been allocated for the offensive by the OKW and pointed out that stocks had been "parked" at the Rhine, somewhere near my hometown. So, if I'm not mistaken, it was me and not "we".
But hey, it's ok, as long as the game will be as accurate as possible.
Another details is, and this goes for other contributors as well, that although it's not your customers' job to contribute with additional research, it usually takes around 3 "inruns" (like we say), where one has to work hard and gather hard facts or details each time, until you "buy" a "claim". You're critical and careful (which is a good thing here), but this also involves a lot of
convincing in case someone happens to know better regarding one or another detail, mind you for stuff the DDT group could (should) have come up with, actually. So, instead of assigning a bunny to verify a sound claim from the community, you have a tendency to dismiss or challenge a request/claim, at first.
I would then totally understand if someone would cease to share thoughts, after his very first attempt to contribute.
That said, you deliver fine and stable products, but you also have one of the nicest fan communities in the Matrix (if not wargaming) universe, plus you have committed people like the Panther bunnies, but also committed customers like TMO, POE, ElSavior, for example, and there are many other ppl who love this game and who contribute in one or another way, and you may want to treasure that. That said, there's no need to act like the "beleidigte Leberwurst", no real translation for that, but it means stop sulking. [:)]