the CTDs need to stop

[bradoon]

restarted game and the MOMENT i spawned.

ctd..

1

4278198529

8744

7

1109188752

0

3221225477

6372701

6372701

0

GL Vendor: ATI Technologies Inc.|Renderer: ATI Radeon HD 5400 Series|Access violation: Illegal write by 00613D5D at 4BAC7818

[expatpom]

it's an excellent idea and we have in fact done this in the past where the schedule allowed

at other times it isn't possible to do this without enormous delays elsewhere (and let's face it, things take too long already if you ask most players) and if no known issues exist there isn't any immediate cause to sit and wait for release

wish it were as simple to do as it is to say it but it never is

Thanks for the reply Doc! ,

Ah I'm not suggesting on every small patch that it has to wait until intermission thats suicidal for everyone and not practical to any extent.

Just with the 'major upgrades' I reckon you would have an understanding bunch especially given the aggro that this update has caused to an certain extent.

Plus it might make the workload easier for you guys in the long run not having to firefight en masse on here with every issue spread out over a number of weeks having conducted what was assumed to be an 'ok beta run and have it blown up in your face.

We feel ya pain mate we really do its not fun on both fronts I can imagine.

Cheers champ..

[BOtedeebar]

ctd'd 3 times in a half hour or so. Definitely something wrong.

Edited March 26, 2011 by BOtedeebar

[DOC]

Good news is we are well undewrway with an entirely new host architecture that promises to eliminate much of the crappy reason this kind if thing had reached the level it has. This will be a very big change to how things have evolved over the last 10 years of this very old code.

Can't give any kind of ETA of course (this is a huge job) but we have a modified host in beta testing (old arghitecture for the most part) that should improve things at the next point release, to tide us over.

[monsjoex]

But why do these CTD's not happen in the open beta and then it gets released and bam loads of people have problems?

[DOC]

50 people in open beta are probably 5% of the variables that exist in the entire game populations range of all things that contribute to this.

[BOtedeebar]

I just noticed on my crash log print out that the date refers to it being the year 1969. Could that be contributing to the crashes?

[Wed Dec 31 17:43:35 1969] Netcode2:209.144.109.144 Session Statistics

[kireh]

Date and time: 3/26/2011 21:03:23

Program compile time: Mar 11 2011 12:50:36

File version: 1, 33, 0, 255

GL Vendor: ATI Technologies Inc.

Renderer: Radeon X1550 Series

Access violation: Illegal read by 00793350 at 000000BC

OS-Version: 6.0.6002 (Service Pack 2) 0x300-0x1

[00793350] (ww2): :

[0050B2A3] (ww2): :

[004FB572] (ww2): :

[0044C47F] (ww2): :

[007D1BF1] (ww2): :

My last one, I see Im not the only one having illegal read's

Edit:

And another within 30 mins

Date and time: 3/26/2011 21:28:54

Program compile time: Mar 11 2011 12:50:36

File version: 1, 33, 0, 255

GL Vendor: ATI Technologies Inc.

Renderer: Radeon X1550 Series

Access violation: Illegal read by 00793350 at 000000BC

OS-Version: 6.0.6002 (Service Pack 2) 0x300-0x1

[00793350] (ww2): :

[0050B2A3] (ww2): :

[004FB572] (ww2): :

[0044C47F] (ww2): :

[007D1BF1] (ww2): :

Edited March 26, 2011 by kireh

[AHWULF]

00793350 at 000000BC is 55% of all the ctds in 1.33.0. No need to post them, I see every one of them in my automated bug list.

[Goatgas]

wow!! I complain about ctds and it gets pulled...no swearing, no names mentioned, just venting like everyone else. cowards.

[MOTORMOUTH]

wow!! I complain about ctds and it gets pulled...no swearing' date=' no names mentioned, just venting like everyone else. cowards.[/quote']

You provided zero data or even a shred of anecdotal evidence, just took a shot at the team. That's why your comment was pulled.

[MARTINI]

There was a CTD related to sounds that has been fixed for the next release.

[GOPHUR]

Did 1.33.2 Improve your CTD problems?