Tank50us

since I don't drink, I'll be the Designated Driver

I'd like to hear more about this...

it could just be that THAT was the version they had easy access to. It'd be like wanting to do an early P-47 (with the Razerback cockpit), but you could only find the D versions. Sure, if you looked around enough you could find the version you want to do... but at some point... money becomes an issue.

Yeah, the taxpayers did, and Mav nearly wrecked his trying to save Cougar! That's certainly news to me... but to go on the post of the guy you were replying to... yeah... we have a good hunch of what would be viable solutions to this mess, but to date, there isn't one beyond "let's hope they can work it out like adults". Failing that, and considering how popular those modules were, ED would either have to make replacements themselves or contract a 3rd party to make them. I doubt they'd let them sit and rot.

I'd gladly fund the creation of a new DCS Module if I won the lottery XD Heck, such a team might have the first versions of the module within a year. That said, in my original statement, I did say IF. And it's also dependent on what happens with the legal teams.

Alternatively, if RB just decides to call it quits, and gives up the Source Code, maybe the devs that actually worked on those projects could band together to from a new 3PS, and then deal with ED directly. Funny thing about this whole mess... is that RB is more like a second publisher then an actual developer. So there'd be no real stopping such a team from forming out of the ashes. The only thing that stops them from fixing the modules... is the lack of source code needed. that's called a "Gentleman's Agreement", and unless you have a notarized document with a signature on it, it's about as good legally as toilet paper.

I think he means if HB were handed the MudHen and told to get it working again it'd delay the implementation of the player-drivern Intruder.

I mean... there is an option... one that's been brought up several times, and now has a whole thread in the wishlist section: Make new versions, and if someone hasn't gotten a refund, they get the new toy for free or significantly reduced cost

and how many Trainers have we gotten since? I could be mistaken, but the Hawk was probably the first... now we have the L39, C101, and the MB339... plus one of the Mirage F1 variants is a two-seat trainer.

knowing Rons ego... don't hold your breath. As I've said on that thread... this could've been settled months ago with the signing of one contract... and it apparently hasn't happened yet.

It would be. But let's not forget that outside of getting the Source Code for the existing modules, or getting RB back to work... there's only two options for ED: Replace them entirely or abandon them... and considering people LIKE those aircraft, it leaves them with just one: Replace them. Also, I think people need to understand that 95% of us will NEVER set foot in these pits outside of airshows or museums. So I think it's safe to say that "Good enough" should be the end goal of any module. Exact 1-1 is fine... but it's ultimately better to get something into our hands soon, and refine as time goes on. Think of it like Elite Dangerous vs Star Citizen. Elite was a functional title after about a year and a half of development, and was released to the public about a year later.... but Star Citizen? Still waiting. In DCS terms... there's the F-15E. RB sat on that thing for about a decade before they released it. And in that time, multiple third party developers cropped up, made something, and released it. Were those modules perfect on day one? No. But they were refined little by little until they got where they are now. Hence my statement about an F-15E replacement could be released to us inside 6 months, as ED has everything they need already to pull it off. It's just a matter of refining it until it's perfect after the fact. Which I personally would be fine with, especially if they come out and say "Hey, if you didn't request a refund for the RB F-15E, you get this for free or at a significant discount".

Well.. If RB isn't coming back to keep their modules working... I'm sure there's a few people who'd be happy to accept a new job...

in legal disputes like this, the money sits in a bank account specifically earmarked for it, and neither side can touch it until the legal issues are fully resolved. So when ED, for example, issues a refund, it's coming out of their pockets, not the escrow account. Now, if the matter is ultimately resolved, and RB comes back to developing the modules... they'll get what they're owed, minus any refunds paid out.

Honestly, with exception to the Mig19, ED has most of the documentation to make a decent 'replacement pack' for those that didn't get refunds, but these aircraft would, by necessity, have to be different versions of what RB made, JUST IN CASE someone in RBs legal department rolls up a newspaper. F-15E can be replaced, like for like, with a different version of the E... I wouldn't go with the EX, as it's too new and there isn't enough documents available yet... but a 1989 or 1990 E model? That'd work. The Mirage 2000C can be replaced by a more recent M2k, maybe the Mirage 2005? Harrier can be replaced by the last USMC version... which has the Hornets radar... which is already in game The Mig19... that's a tough one since getting Russian Documents is notoriously difficult. But there is a team working on the Mig17 right now. The real catch is how much development time would be needed to get each one working. A replacement Strike Eagle could probably be in our hands inside of 6 months with BASIC functionality (A/A weapons, Dumb and Laser-guided Bombs, working flight and damage models), but that's only because they have most of the work done for them with the F-15C (same engines, radar, etc). But a new Harrier or Mirage? We'd need a couple years. Minimum. This all being said... I just hope they can figure something out with RB, either to get them working again, or get the source codes. But until then... pray.

This isn't any different then if Activision contracted another company to do some work on a COD title, and they turned around around and took the engine assets to make their own game or make something for another client. Activision would most likely either sue them into oblivion or withhold all payments from the moment they caught them. This isn't a bourgeois vs proletariat situation... this is a case of one group violating the terms of a contract by doing something they weren't supposed to do. This situation could end tomorrow with the signing of one contract. But that side won't budge... and they're the ones with more to gain... and all they have to do IS SIGN A CONTRACT.