Templar, you're acting as if this build is the only one they have.

Apparently, from what I've heard, they fixed a lot of the mechanics issues from the last build. For example, they improved (not fixed) hit detection...

Also, your comparison with BF and GoW... Both are huge companies. Epic developed the U3 engine, and license the engine out to a lot of games companies, so can afford a lot of in-house testing.

Actually, I can't be bothered with this argument anymore. All the points have already been made, and you don't seem to understand the beta testing period. It's not like the next build will be this build with extra stuff tacked on.

That's it from me.

Now, look at what what Dust 514 is missing:

No accurate, responsive controls.
Weapons don't have have weight & don't feel empowering to use.
Weak sound design & effects.
Poor hit detection & terrible lag.
Animations aren't fluid.
No unique map design to encourage different gamepaly: CQC, ranged, vehicles only, infantry only, etc...
Lackluster graphic.

I measure Dust 514 from what I have seen so far, my opinion is formed on what I see and play NOW.
Most of you instead say "Dust will be better TOMORROW".

If the the future will prove me wrong then I will win a great game to play on PS3.
If the the future will prove me right, well...

So, I've been seeing some posts of people claiming that in this stage of beta, there are aspects of the game that cannot be fixed, that it's "to late" to make major changes to the core mechanics of the game.

I have a question for those people - how many of you, have ever developed a high end, high budget FPS game for the PC or a gaming console? How can you so knowingly state that it is "to late" to fix? Besides, there aren't that many game breaking issues, aside from spawn camping and draw distance, both of which we know are being worked on. How can you say this game is so "bland" when you have seen 1 (2 for some of the older testers?) landscape, 1 mood (again, 2 for the older testers?), and 3 installations? It is profoundly stupid to make such a statement.

What you are seeing right now, is a miniscule portion of the universe that you are being welcomed into, and all you have to say is "this sucks, can't fix it, bye"? Some people...

We are 3 builds in and the only thing they did was make it look pretty. Weapons are not good, draw distance is still bad, hit detection still sucks. Don't get me started the aim assist, lack of speed this build. Also this is the only shooter I know thats been in dev for 3 years and runs like ****. Alpha build from 09 looked better but the camera was dark so now I'm not so sure.

Word was CCP got some exDICE guys to work on this... guess that's a rumor! I've played and seen Alphas better than this so the excuse of oh it's a beta is a **** poor one.

Ok I really need some help here regarding how some game mechanics are broken? Hit detection, animations etc.

Now isnt the point of buying into the Unreal engine so that a game designer doesnt have to worry about the basics?

Surely the U3 engine is quite capable of doing perfectly good hit detection? So what are CCP doing wrong in programming the engine?

Now as far as animation is concerned surely again the engine is there - all CCP have to do is load up the 3d model files and let the existing engine do its thing? So I can only assume that CCP have installed basic model files and textures as they want to test other issues first? Id bet they have done a small internal test where they maxed out the textures, models etc then scaled them back for beta test of other issues. After all at release they will want the public and testers to still say "OOOh thats pretty"

You wanna know what Dust is gonna look as good as? Check out the planetside 2 demo from E3 - that **** is the shizzle. But its played on one large map that is gonna be real boring 6 months in. Dust will have Millions of battlefields...

You wanna know what Dust is gonna look as good as? Check out the planetside 2 demo from E3 - that **** is the shizzle. But its played on one large map that is gonna be real boring 6 months in. Dust will have Millions of battlefields...

First we won't have million of but planets thousands of planets/maps.
Second, most important, they will all be randomly generated...think of it as Diablo maps/dungeons, just in 2012.

Part of the issue with the hit detection is that its server-side, not client-side. Right now we're running on a server that's only so capable, but they've been upgrading it as they go along. While some people have been insisting that the hit detection be made client-side, but I'd prefer it just stay as it is and be improved upon, because client-side hit detection is one of the factors that makes aim-botting and all other manner of hacks possible.

well said. Client sided mechanics for an FPS are bad news....not trying to turn this into Combat Arms here

Client side hit detection does have draw backs, but it also prevents people from ping shielding.. Not very easy to land a shot on someone with a 500+ ping.

Perhaps some sort of combo between the two could be put in place. Say, if someone has a ping higher that 300, maybe hit detection for that person only would be swapped over to client side rather than server side. Would make ping shielding impossible, while for everyone else making aim-bot's less viable and keeping things balanced?

Not sure I said that very well.. oh well.

simple, not gonna be a problem once CCP kicks their servers into high gear. The server situation we have now isnt gonna be the same at launch. These are simply test servers, from what i have read...