Is BIS looking after the "receiving..." issue?

[Dogtags]

BUT STILL: why can't BIS more open in telling what exactly triggers that sceen? Current info-level is still: "something went seriously wrong....."

Wow - we all thought this is normal.

I don't care what triggers it, I am happy to hear BIS are "Working on it" that is all that matters, gives me hope as ARMA2 is a beautiful game hiding behind a cloak of bugs currently, can't wait to see its full potential reached.

[No1sadvocate=US=]

Flushing the mem every 5 mins or so works for me.

[S!fkaIaC]

Flushing the mem every 5 mins or so works for me.

Would never consider that.

[No1sadvocate=US=]

well i can play the game.. Its better than not playing until it gets fixed...

[ICE-Raver]

I have yet to make it through a complete multiplayer game without this error.

On rare occasion it clears itself up, but 9/10 times I have to leave the server.

[FlunkyMonkey]

I don't care what triggers it, I am happy to hear BIS are "Working on it" that is all that matters, gives me hope as ARMA2 is a beautiful game hiding behind a cloak of bugs currently, can't wait to see its full potential reached.

I agree, this is a f*cking revolution as far as this company goes

[Alex72]

Had this problem one single time with 1.01. I got a clean pc and low videomemory. 2GB ram. So really, this cant be easy to find and fix just like that. Good to know its being checked though for those that have this problem.

[Dwarden]

Oh-ohhhhhhh Big B is watching me. all my smurf and porn downloads are reported too

Wai..Wait a minute, I turned off WER and uploaded .rpt and dot-whatever as been told, not used?


Btw, I use since yesterday 186.24 and I got 5h WITHOUT Rec-Bug, but I had this also with 190.?? and next day it returned, I hesitate to shout "hurray" now. I will try to get into a crCTI until weekend and report if it solves (for me) this issue.


BUT STILL: why can't BIS more open in telling what exactly triggers that sceen? Current info-level is still: "something went seriously wrong....."

Wow - we all thought this is normal.

turning off WER is very 'unwise' as any OS and program errors aren't reported to MS and the developers who took part in that program ...

no wonder things are then UNFIXED as developers don't receive related WER dumps ...

[FlunkyMonkey]

no wonder things are then UNFIXED as developers don't receive related WER dumps ...

I guess this has been our fault all along!

[Tiglet]

it's being worked on ....
oh btw there is systematic data collecting as we are receiving reports via MS WER (Windows Error Reporting) for years ...

it was mentioned more than just multiple times since 2001

Good to hear!!
I had to lower my video memory setting in the game to prevent this bug but now the game reacts terrible