Desert Conflict Mod Update - CH-53

[RedDot]

Re: Desert Conflict Mod Update - CH-53

I must admit it: I looks cool, but damn, wont it be hard to fly?

[zuiquan1]

Re: Desert Conflict Mod Update - CH-53

it was awsome back in DC, if the DEVS get it close to the DC charecteristics then you wont have a problem with it

[jimbob]

Re: Desert Conflict Mod Update - CH-53

When DCON comes out, if my team is able to get players and recruits like DC, and DCON saves BF2, take all the time you need. I am just hoping that people wont give up on BF2 because the main game is dead.

That entirely depends upon the attitude of others - not the release date of a mod that noone has to pay for and noone gets paid to make. Best of luck to you, DCON devs, I am SURE regardless of when you release your first build that you will have a fanbase instantaniously. Keep up the good work!

[imported_Calaros]

Re: Desert Conflict Mod Update - CH-53

You'd think it wasn't very dangerous, untill you here the thump of the engine, turn around and get hundreds of bullets to the face from it's mini guns.

I didn;t notice no miniguns. Cool that it has them

[imported_<GN>John]

Re: Desert Conflict Mod Update - CH-53

The original had two 50 cals and a tail gun which was a minigun.

With the right team backing you up, the seahawk (as it was called in dcf) was a force to be reconed with.

[{RR}MaizeMyDay]

Re: Desert Conflict Mod Update - CH-53

A great modeling & rendering job. I used to fly in these back in the 1980's during my days. I just wanted to note some corrections to the original notes about this aircraft:

Model: CH-53E Super Stallion (3 engines, 7 blades). The older Sea Stallion CH-53D models had 2 engines, 6 blades and are phased out.

Future: They are not being superceded by the V-22 Opsrey. The Osprey is replacing the aging fleet of CH-46 Sea Night aircraft. The CH-53E continues in service as a heavy lift troop/cargo/aircraft recovery helo. It has computerized automatic flight control systems (AFCS) and is a dream to fly...very smooth. The one in DC flew like a pig and it should have been faster (170 knots) and more agile. I hope they fix that in DCon.

Everything else noted appears to be accurate. I might also add it's produced by Sikorsky, the same company that makes the Blackhawk.

[torment]

Re: Desert Conflict Mod Update - CH-53

lol. how meany will it hold in the mod. cos it would suck for 25 people to get it buy a plan lol....

[Ahk-Med]

Re: Desert Conflict Mod Update - CH-53

I'm not, nor have I ever been on a mod team. However, I've been playing mods and TCs since Wolfensten 3D. I think that gives me just as much right to comment on the mod scene as the guy who paints textures for mod XYZ.

For the most part, I agree with Pennybags, mod teams are better off to release early and often. I'm not trying to trick or convince any team to release now, that's their decision. In the long run, if their mod is ever worth playing it will show in a rough release and you'll get the early player support you need. An imperfect model, skin, or map isn't going to be a deal breaker. Don't agree with me? How about Valve Software, you know, the company that has taken in several mods and turned them into sucessful commerical products.

http://www.planethalflife.com/featur...dfocus/02.shtm

We've summarized this MOD development philosophy with the phrase, "Release soon, Release often." Commercial developers work for 2-3 years, release their game, and hope to god people like it. You don't have to make that leap of faith. You can design your whole MOD, write 25% of it and polish it to a playable state, then release it and begin getting feedback immediately.

Not only are you working on a mod for an engine w/ zero developer support, that same developer is doing their very best to ensure the game your modding is tossed in the trash and replaced with a new revenue stream 18 months after release.

The notion that you're bulding a mod for the tiny hardcore community seems foolish. Why do most work on a mod? To show their skills and land a job in development. Wouldn't it be best if your mod was exposed to the largest fan base possible? Every day a release is not made results in less people who will play and/or even hear about your mod.

I think the biggest problem is the mod teams are too ambitious. An example: rather than develop desert and sea warfare maps for your first release, why not stick to a couple desert type maps only and spend your time polishing that? When thats proven succesful you can direct your attention to sea warefare maps. If the polished desert map don't attract and maintain a playerbase, do you really think a sea warefare map with a couple of new models would have saved the mod?

Commercial developers have a hard enough time releasing polished bug free games, what makes mod makers think they can? Again, if your mod is worth playing, people will accept the bugs of earlier releases. AT rockets pass through vehicles and the red teammate bug are still in vanilla, but despite the bitching, people are still playing.

TotalBF2 displays the progress of all kinds of mods on the front page. I'd wager that more than half the mods that have made the front page are never released.

Mod teams can do whatever they want. They don't owe me anything. I simply believe that an overly ambitious long development is the wrong approach. Release early, release often.

[Mateck]

Re: Desert Conflict Mod Update - CH-53

I loved to fly with CH-53 from BW mod in Operation Flashpoint.