Jump to content
Sign in to follow this  
S!fkaIaC

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

Recommended Posts

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 :yay::yay::bounce3::bounce3:

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites
Oh-ohhhhhhh Big B is watching me. all my smurf and porn downloads are reported too :eek:

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....." :eek:

Wow - we all thought this is normal. :D

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 ...

Share this post


Link to post
Share on other sites

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

:rolleyes::803:

I guess this has been our fault all along!

Share this post


Link to post
Share on other sites
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 :(

Share this post


Link to post
Share on other sites

Since the threads dealing with the "receiving.." bug are still not merged I have to state at 4 places......

186.24 Nvidia driver made it that I can participate now at large crCTI battles at XR-server, still getting that screen every 5-15 Minutes especially when I driving in an vehicle, but until now I managed to cure the situation by tabbing to the mission-map. If it happens in the next days that it is getting locket at the Rec...screen I will report it asap.

Share this post


Link to post
Share on other sites

Sorry to say, but 186.24 DID NOT solved the issue, I got locked several times now during a MP game, had to terminate ArmA2 to escape from "Receiving..." screen.

Share this post


Link to post
Share on other sites

Not sure if this is possible but it would be a fix until BIS patches the problem.

Could we create a .bat file or similar to run the flush command automatically every so many minutes. That way you could play the game without having to think about putting the command in manually. It would be almost normal.

Share this post


Link to post
Share on other sites

They care as much of it as about The Random Lockup issue. In explanation: Buy yourself a Little Bugfixer Kit!

Share this post


Link to post
Share on other sites

I'd the bug when i play MPmission alone (lan, locked server) :yay:

Sounds, White dots, and black screen :bigglasses:

ALT+F4, I respawn in my bed :stuck:

BIA debugs the game pls :cool: :D

Share this post


Link to post
Share on other sites

Any answer from BIS concerning this receiving bug ?

I know this may take time for them to fix it, and understand that, but why this silence about it ????

Share this post


Link to post
Share on other sites

Ive got a HD4570 with 1 gb i set everythin to low and all options managed by application. But i get the receiving bug everytime when i play the large maps and getting near a big city. On smaller maps the bug doesnt appear ... ok less often but it is playable. What i noticed is that my ati card gets very hot above 100 degree. BUT and thats funny its only in arma if i play prototype or some other next gen games und HIGH details the graphiccard is under 70 degree. Even after hours of gaming ... don´t know why that happens. AN i cannot find any errors in the windows event log, and there should be one if the graphic card resets or something ..

I love the game if it runs i can live with all the minor bugs but that bug is a killer ... only thing that works is if i get killed at the receiving screen it starts instantly over and i can respawn.. So what i do is i only drive with unarmored vehicles so that my teammates can kill me if necessary. Ehat btw is a very nice feeling. You shout to get killed u only hear the sound of the shot and see the respawn screen (doesnt work always!). But i cannot play any armored vehicles or planes or helicopters ... i mean i can but if i get the bug the team is fucked if i am the driver ....

Share this post


Link to post
Share on other sites

As we say here : "bienvenue au club".

Same problem, with a 3850 512Mo, but no overheating at all, and good performance, till the black receiving screen of death, every 2 minutes.

So : just tell us you are on it guys, like Mr Wolf in Pulp Fiction :)

Share this post


Link to post
Share on other sites

Placebo is bombarding us with statements related to that issue. :eek:

Share this post


Link to post
Share on other sites

So : just tell us you are on it guys, like Mr Wolf in Pulp Fiction :)

ahahahahahahahah..at least a bit of fun......this bug makes me very nervous...when i got some free time i will make some test with video settings

Share this post


Link to post
Share on other sites

Let's summarize:

There is a significant number of BIS customers getting the "receiving...." screen under various circumstances (for some only in MP, for some in SP, not consistent over the time). It is hitting both Nvidia and ATI GPU owners.

BIS did not disclosed so far what exactly could trigger this screen.

BIS did not stated if they see any need for action on BIS side (Maruk was rather fingerpointing on Nvidia)

BIS is totally silent and Placebo as mediator between BIS and community is from questionable value for the community.

Well...

Share this post


Link to post
Share on other sites
Let's summarize:

BIS did not disclosed so far what exactly could trigger this screen.

BIS did not stated if they see any need for action on BIS side (Maruk was rather fingerpointing on Nvidia)

BIS is totally silent and Placebo as mediator between BIS and community is from questionable value for the community.

Well...

As you know I am also getting this frustrating game breaking screen. However I have to totally disagree with point 2 because there was a post a couple of weeks ago by BIS that I know you saw that said that they are indeed working on the issue.

So for everyone's information BIS are working on the issue.

I am afraid it comes down to being patient and hope they include a fix in the next patch. I am just as frustrated as the rest of you and I have just thrown my arms in the air and given up with the game until patches arrive.

Not much help but it is something to cling onto. I just hope the rumor that most BIS staff went on holiday after release and wont be back until August is not true for our sanity sake.

Share this post


Link to post
Share on other sites

I was planning to buy the game so i tryed the demo first.

Guess what, recieving message on MP all the time.

GFX card is Asus ATI.

Im a BIS-game player since 2001 (ofp-arma1) but i doubt if i will buy Arma2.

I think i will wait a few months and go for OFP2.

Share this post


Link to post
Share on other sites
point 2 because there was a post a couple of weeks ago by BIS that I know you saw that said that they are indeed working on the issue.

Can you please link that post? I only found Maruks statement to that issue.

Regarding holidays: Nothing against that they close the company for a month, but they could say so.

http://forums.bistudio.com/showthread.php?p=1323608#post1323608

Read from post 70 on, in post 77 Suma replied, Suma requested some more info in 83, I replied again, but then.......conversation ended as usual.

This is now the thread I refer to:

http://forums.bistudio.com/showthread.php?t=75107

My post #10 states that I do not believe that 1.02 cured anything, Maruk replied in #11 that whatever he has in mind that was fixed was included in a certain patch.

And he stated:

Or isn't more accurate to say the latest Nvidia drivers are not compabitble with the game? What drivers do you use btw?

I do not know if it was clear to him at that time that both Nvidia and ATI users are affected.

Honestly, even if I appreciate it, I do not expect Suma and Maruk to show up here and post, I rather expect that Placebo or other moderators managing the communication between BIS <-> community.

Edited by S!fkaIaC

Share this post


Link to post
Share on other sites

Yup, what communication ?

"Mr "X" told Mr "Y" that maybe Mr "W" heared from his neighboor that they seem to be working on the case ?" :j:

I guess this alphabetic familly didn't pay the game...

Share this post


Link to post
Share on other sites

Honestly, even if I appreciate it, I do not expect Suma and Maruk to show up here and post, I rather expect that Placebo or other moderators managing the communication between BIS <-> community.

Here we go Placebo

1.03 is I believe close to being finalised and thus somewhat imminent.

Share this post


Link to post
Share on other sites

Placebo's special way of answering patch related questions is IMHO not the way to gain any goodwill among the affected customers.

And "imminent" in BIS language could also mean several months. And he "believes", does he has no access to BIS to get it more precise?

All I asked for was if BIS is aware what the root cause for the "Receiving bug" is. Knowing that would give us possibly the chance to avoid situations triggering that issue.

If they do not know the root cause I have doubts that they can fix it soon, hence it is not serious pointing to patch 1.03 leaving the impression a fix will be included in patch 1.03 comming "soon".

Edited by S!fkaIaC

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×