You know, I sure hope some folks at Taldren take note of this thread. There are some seriously good pros and cons coming up here that may help them in future patch or development decisions.
FireSoul, I think you and "Evil" Dave have done wonders -- more in the last 3 months than Taldren has done for OP in over a year.
I'm actually quite surprised that so many people have chosen OP as their favorite, or qualified their choice with "if OP D2 worked, then ..."
Nanner, thanks for the kudos about the hard work the OP admins have done in the past, but someone was absolutely correct in saying if our hard work could have gone into improving the campaign experience rather than trying to make it half-workable, OP D2 would have been much better. Heck, just within the SFCX group we have come up with at least 2-3 campaign ideas, "major" and otherwise, that would be really cool, only to have to put them off indefinitely because of the D2 bugs. I'm sure the other admins could say the same. We've also come up with ways to work with what we have in the cartel layer issue only to be confronted with the speed bug, inability to do neutral coop, broken missions, etc. In the end, some of us refocused our energies elsewhere, like SFC3 testing, because we couldn't make any progress with OP in its current state.
That said, if the forthcoming OP patch DOES fix the speed bug, look for an SFCX campaign shortly thereafter. We want to have a dedicated shiplist (specialized to our needs and "corrected" per SFB specs similar to FireSoul's list) and specific VCs (rather than the general each planet = X pts., each base = Y pts., etc.).
One more thing I'd like to bring attention to is SQL for OP. Unless things have changed drastically since I was last "in-the-know," OP DOES NOT HAVE SQL. Then again, EAW's SQL support, I think, is still considered in a test state. SFC3's SQL support seems to be getting there, but still unofficial. If the other two are going to have SQL support, OP should, too. Castrin has a lot of things he would like to do, but can't without SQL.