I am asking that CCP release all content in 1.5. that means all weapons, suits, and most vehicles. I know it seems illogical to release something that is not finished, but for dust it would be the smartest thing, in my opinion, to do.

Here's why.

If you've been here since last year then you know what happens when CCP pushes something back to "fix" it. they push it back for a month or two and release it broken. the community yells at them for a month, and then they really fix it. Foxfour said something about how many man hours it would take to create simple things like new turrets and suits. The answer would be half the man hours wasted doing these "fixes" and only having the community tell you how to do it right.

Matchmaking is the perfect example. How many months was spent on this new matchmaking? all that QA testing, all that time spent and for what? it was the worst coded matchmaking i have ever seen. you couldn't get into a game with a squad, and most of the time you waited for 5 minutes only to get the team glitch. But how long did it take to fix after release? a week and a half. So, they wasted all those man hours only to release something broken anyway, and only to fix it in under two weeks. There are many examples of CCP releasing something broke and it takes the community yelling at them to fix it. Hopefully now they will listen to us when we tell them something is gonna be bad.

The truth is, no matter how much CCP and its QA department work on something, it will most likely be broken. It is best to do their best on it and release and let us give them some proper feedback. because these delays are not helping at all.

I doubt a DEV will respond to this. I just wanna see this game succeed and it keep taking 2 steps forward and 4 steps back.

I am asking that CCP release all content in 1.5. that means all weapons, suits, and most vehicles. I know it seems illogical to release something that is not finished, but for dust it would be the smartest thing, in my opinion, to do.

Here's why.

If you've been here since last year then you know what happens when CCP pushes something back to "fix" it. they push it back for a month or two and release it broken. the community yells at them for a month, and then they really fix it. Foxfour said something about how many man hours it would take to create simple things like new turrets and suits. The answer would be half the man hours wasted doing these "fixes" and only having the community tell you how to do it right.

Matchmaking is the perfect example. How many months was spent on this new matchmaking? all that QA testing, all that time spent and for what? it was the worst coded matchmaking i have ever seen. you couldn't get into a game with a squad, and most of the time you waited for 5 minutes only to get the team glitch. But how long did it take to fix after release? a week and a half. So, they wasted all those man hours only to release something broken anyway, and only to fix it in under two weeks. There are many examples of CCP releasing something broke and it takes the community yelling at them to fix it. Hopefully now they will listen to us when we tell them something is gonna be bad.

The truth is, no matter how much CCP and its QA department work on something, it will most likely be broken. It is best to do their best on it and release and let us give them some proper feedback. because these delays are not helping at all.

I doubt a DEV will respond to this. I just wanna see this game succeed and it keep taking 2 steps forward and 4 steps back.

I'm not sure you understand what "not finished" means in the world of programming. if they release unfinished content it will literally break the game. not like it'll be unbalanced but more like it will clip through walls and fly.

I'm not sure you understand what "not finished" means in the world of programming. if they release unfinished content it will literally break the game. not like it'll be unbalanced but more like it will clip through walls and fly.

The problem is that "broken" can mean a lot of things in programming. The problem could take months to fix, meanwhile the game will be a total mess. The matchmaker might have only required a few variables being tweaked to resolve the big problem. Some issues may require a complete code refactor to resolve, meanwhile we have a game that is horribly broken. DUST is in fairly decent shape right now, it's missing content, players and balancing, but it's still possible to play and have fun. If CCP dumps a heap of new broken content into the game, you can bet that it will take them many months to sort through the chaos and hot fix things, which itself could create many new problems, like so many people leaving that the matchmaker can't produce reasonable fight. This could snowball as all new blood gets chased away due to pub stomping.

Yes the delays are really annoying, especially since a lot of this stuff should've been released "soon" as promised at fanfest, but DUST is moving in the right direction (albeit very slowly). I hope CCP considers my test range suggestion. I think that could resolve many of the issues.

This.
We all very desperately want new content but getting that content at the expense of performance or stability is a fools request.
CCP listened and delayed a patch they were not comfortable releasing. They are giving us an opportunity to help them solve some of the problems they encountered. It makes more sense to try and work with them to decide the roles vehicles will fill and how they will interact with infantry, other vehicles and AV. Once we know what 'tanks' are and how they operate on the battlefield releasing racial varients will be both easier and more coherent.

I would like to offer some perspective here.

Consider how well the release of other content has gone.

OP flaylock, broken squads, bugged comms, the whole PC fiasco, the optional respecs giving out cash, Commando suit being trash, etc.

Those problems all stemmed from things that CCP considered ready.

Imagine how bad their incomplete stuff is. Imagine the horrors of what they would release if they followed your request.

When the stuff they finish is that bad, I don't want to even think about what horrible abortions of code they have running right now that actually makes them go "You know, this is really not ready yet". Must be a clusterfuck going on over there right now.

You know what. i didnt even think it could be worse than what they release. you may be right.