The two groups started working together. They were "one group" up through the intial version 2 of SP:WW2.
But when the SP3 code became available, some of us wanted to move to that code base to further develop the game and make more sweeping engine level changes than some others. Specifically because of the opportunity through the SP3 online code to bring the game to Windows and the goal of interactive realtime play.
There were also "artistic differences" as they say, in how the game should be developed. There are dozens of decisions in how to "tweak the engine" to get the results you see, and as you say you like certain aspects of what we did in some cases and SP Camo in others. At some point you get to irreconcilable paths and the only way to keep everybody happy is to split. So that is what happened.
The bottom line is that the two groups wanted to pursue indpendant paths towards what they saw as their "perfect SP game".
How is forcing these two divergent paths back together helpful? There is as much chance you would get the two aspects of the games you DIDN'T LIKE as the ones you did! And invariably what you thought were the "good ones" were some else's pet peeves.
And there is only so far you can go into making the game "user configurable" We can't have "SP Camo/Matrix" buttons for every choice of variables in the whole game!
Now there was an agreement that both parties could use the SPWW2 stuff - Camo used the SP2 code base to start from, and we used some of the icons until we phase in our own.
But from there on out there was really no going back. It was not possible, nor deirable to "cut and past" things from one game into the other. They are are just too different.
Both groups took some of the same things forward, so some of the features between the two games are very similar. Others are quite different, because from the "big list of stuff to change" each group added its own ideas and reprioritized it based on its desires.
You can't just combine the lists, because some things like internet play, are just too hard to do in the DOS game, while Windows carrys certain baggage with it.
So what does "work together" really mean?
OOBS seem a good place to start, but wait - SP Camo likes to use "home language" names for things, we have stayed more with "generic names". And becasue of the most recent changes the formats and much specific data are different. So what seems "simple" is more difficult to execute than it first looks, assuming that there is even basic agreement on the data in the first place (see Tiger front turret thread
The "maturity" I refer to in the SP:WW2 OOBs is as much organizational and fact checking as "basic research". Since the SP:WaW engine uses different data, ultimately all the cross referencing across OOBs and logical ordering of entries must be done step by step, and that takes time, whether we used the unit and formation names SP Camo used or not! The QA on over half a million pieces of data takes months and moths and for consistency 's sake really has to be done by a very small team of folks (ultimately by one person in the final analysis).
We already share the same principle user base and have heard pretty much the same requests over the years, with two independant "camps" you the user has twice the chance of seeing something you want implemented!
But I get the feeling that by "work together" what people want is a big SP Chinese menu so they get to "pick form column A or column B" to customize the game by picking form thfeature sets of both games to set i up to their liking their liking. That is just an impossible task given the fundamental differences in the two code bases.
Believe it or not we get complaints already that in essence say "its too much trouble to have to configure the game to make it how I want...why couldn't you get it the way I want it in the first place!"
Its simply impossible to be all things to all people. That is a big part of the reason the two groups have "compartmentalized" to a great extent. Two independant looks give you twice the chance of geting the things you want in one or the other.
[This message has been edited by Paul Vebber (edited August 03, 2000).]