You're new to CCP products aren't you? As a long term player of EVE since 2004, I can tell you that CCP takes a notoriously long time to fix bugs. Why? I don't know. I really wish I had a good explanation. They're exceptionally fast at fixing exploits though so it really makes me wonder sometimes.

That being said, when they do finally fix their bugs, their fixes are usually spot on and never happen again.

Just because you may not agree with what I say, you can't assume I'm new at EVE or CCP.

There is a difference in this though. This is not a small, trivial bug. This is a major, game breaking, and potentially harmful to the hardware bug. Those we really haven't seen in EVE, and when we see bugs that are really game breaking, CCP tend to be a little more expedient about it.

Lets just say the crashes had been replaced with this line of code. ( time to bring forth the CCP menace)

DELETE/BOOT.INI

i know for a fact CCP would poop the boxershorts they have on and they would fix it right away.

so now tell me a long term 2006 eve player why they have not fixed the hardware crashing.
that alone is just as bad as telling an eve client to frazzle your boot.ini and we all know what that does to your computer systems OS.

GFX problems in eve online, fixed right away with hotfix and patching. but yet again this hardware damaging bug/s are left to run riot. exploits, ship bumping, etc etc all fixed right of the bat. but with dust they to bothered with adding more broken bloody stuff.

SOON does not cut the mustard anymore we had enough.
ITS BETA, does not count anymore, stuff needs fixing but they fail to lift fingers or even admit the massive problems we found as bug hunters.
More content, hmmm where did i hear that before , oh yeah in eve-online, then CCP woke up from Dreamland.
they want dedicated beta testers, but all they are doing is forcing them away from testing dust514.

the longer it goes on the more this forum fills with " game crashed"" invalid bug"" ps3 blown up" threads
not very nice for new betatesters to dust to have to read and find no action from the makers of dust CCP

Whoa partner. If closed testing bothers you that much maybe you should find something else to do until the final release is out. Then the Beta excuse won't count anymore.

why should i wait till final release. i mean if they cant fix stuff now whats going to say they will later. i mean 8 reboots in 3.5hrs.
if this was eve-online beta that shizzle would have been sorted, server would be taken down and message posted to keep updated.

i really dont know if ccp know if they are coming or going, i should not whooa there, thats something CCP should be doing.
take a stand back look at this problem and get it fixed. not brag about silly content added or some fancy dev event they got running.

right now and most will agree, dust 514 is becoming un-testable with these current system crashes and server hangs.
yeah it may sound like i am bossy, but i care more about dust being something and not just another FPS failfest.
Dust has to work or it taints eve-online " oh yeah that game that tried fps and scr3wed up lulz, noobs".

CCP can do well better than they have done, and to be honest it is about time they showed they can fix these problems off the bat right away, so testing can still be done with all taking part, not a handful here and there.