4 replies to this topic

[Christopher Hamilton]

i have current drivers (AMD, windows), tried an nVidia too (2 PCs), 32gb ram win7 64bit running 32bit client due to not beeing able to start 64bit client. i am a regular user of the repair tool... yes. everytime i run the client.

today i bombed out of CW 5 times in 5 minutes after a fresh client and system start.
i do clean out shaders folder already on a regular base.

WTF is wrong ? who else got this ?

client bombed out when turning 5 steps from drop the first time.
bombed second time trying to uphill 10 steps from base.
it bombed out again after one chat message on third, didnt even move.
it bombed again upon entering CW
then upon connecting.

Edited by Christopher Hamilton, 06 February 2016 - 07:04 AM.

[Christopher Hamilton]

it just didt bomb out again. one chat message, 50 meters distance.

[Christopher Hamilton]

and again... i managed to get to the door and its 31:33 already

Edited by Christopher Hamilton, 06 February 2016 - 07:09 AM.

[Christopher Hamilton]

and hang with audio artifacts had to shoot the client in the head

"due to leaving an active match...." WTF your kidding me ? cant you remove that **** when the client wholesale bombs the f... out because of crappy coding ?
gee, use a malloc debugger FFS.

[nehebkau]

Christopher Hamilton, on 06 February 2016 - 06:59 AM, said:

i have current drivers (AMD, windows), tried an nVidia too (2 PCs), 32gb ram win7 64bit running 32bit client due to not beeing able to start 64bit client. i am a regular user of the repair tool... yes. everytime i run the client.

today i bombed out of CW 5 times in 5 minutes after a fresh client and system start.
i do clean out shaders folder already on a regular base.

WTF is wrong ? who else got this ?

client bombed out when turning 5 steps from drop the first time.
bombed second time trying to uphill 10 steps from base.
it bombed out again after one chat message on third, didnt even move.
it bombed again upon entering CW
then upon connecting.

Have you run a RAM test -- from the boot menu on startup? Had a similar thing a few years ago and ended up with some bad ram. (maybe a test of your graphics card's ram?)

Edited by nehebkau, 06 February 2016 - 08:27 AM.