Lazy8s said:
No, it doesn't. The Criterion team that focuses specifically on the Renderware side doesn't even get the finalized implementation of a new feature that comes from the game side - from which they'd still have to make into a generalized solution for the toolset - until it's gone through final QA in the game, which happens at the very end of the development cycle.
Lazy, the company could have decided to operate differently. Simple as that. They aren't forced to ship game product before middleware update. They could ship them in lockstep with each other. Or they could choose to ship no game product at all. They could, instead of creating their own game content, contract out their game development talent as support services in conjunction with Renderware licenses. Etc. But, Criterion chose to A) compete with their clients by releasing their own game content and B) release that content out of synch with the company's Renderware product.
This wasn't being argued.
Didn't say it was. Just making sure it wasn't overlooked.
Criterion's game output is too small and limited to be capable of seeing benefit from such a ploy.
I think you've got this the wrong way around - being a smaller developer means that any advantage they can give themselves is bound to have a more significant effect on the outcome for them than for a large company like EA. If first dibs at the latest otpimizations can be measured to give Criterion a $1 sales advantage and the same for EA, who benefits more from that dollar? Criterion, obviously, since it would be a larger percentage of their bottom line.
With more influence comes more responsibility, though, which is why there is more potential for conflict of interest with EA, the biggest publisher, than with Criterion, a small developer.
...
The issue wasn't of their likelihood nor intention to use such tactics. Rather, it was the greater conflict of interest that could arise with someone of their size than with Criterion.
And yet, you seem dismissive of the XNA conflict of interest, simply because it does not involve a move from small company to big company:
The difference here is that the existence of the XDK and Direct X is already a given and that XNA just broadens that. If this was a topic about control of XNA being moved from a small company to Microsoft, the increased potential for danger would apply to them, too.
Who cares if the potential for danger has increased or not if the potential was already high? My point from the beginning of this thread has been that this conflict of interest that everyone is suddenly wringing their hands about has been rife at all levels of the game industry for years. If you're going to be worried about the potential conflict of interest, why tolerate it at any level?