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

[S!fkaIaC]

I feel a little bit fooled since this is the only "technical" statement delivered by BIS so far that I am aware of:

The "receiving" screen during normal means something has gone wrong, like system memory surface allocation has failed, or driver reported an internal error. Before patch 1.02 the behaviour in this case was to terminate the application. Since 1.02 we reset the device and continue running.

You might find some more details about the reason of the reset in your ArmA2.rpt file.

On his request:

I have checked the code and I think I have found one case where the Reset is done in mistake. The case is when textures needed for the scene do not fit into limits set by Texture memory detail. I will try to fix this in the next patch. Until then you you might try lowering your Texture detail or increasing the Texture memory settings as a workaround.

... I replied:

Thx for the quick reply Suma.

One question to make this clear to me: "Device reset recovery requested" does trigger what action exactly? because either it triggers something wrong, or my system reacts wrong by getting stuck.

I mean whatever goes wrong, a "recovery action" should "recover" from that situation means I notice a short flickering/wrongLOD/black screen and then it goes on as normal.

No is the question what exactly makes that we stuck and the black screen remains in some cases and the "Receiving..." disappears only for 1s but keeps flashing this way? Does it means it stucks in a restart loop?

Later Suma replied:

I have analysed your report once more and what is strange to me is the "Vertex buffer not allocated" message. This message should no longer be produced by 1.02, corresponding code containing it has been removed.

Can you delete your .rpt to make sure we are not analysis some left-overs from previous sessions?

Can you make sure you are really running 1.02 (both in the main game menu you should see 1.02.58064, and in the .exe file properties the version should be 1.2.0.58064)?

I replied:

It was only in 1.01, it never appeared in any of the 1.02 .rpt's.

I forgot to delete the .rpt during 1.02 upgrade manually and I do not know if your upgrade procedure was supposed to do it. AFTER I once deleted it, that vertex thingy was not seen anymore, only this

Error: Failed to create surface texture (HWHATEVER-TEXTURE.paa[#])

followed by

*** Device reset recovery requested



To be sure, I deleted several times the rpt, played until the bug appeard, and then saved rpt under different name. Significant is always the Failed to create surface texture as last or almost last entry, all spam around is related to the buggy mission code of crCTI warfare 0.4.


I have an account in devheaven, should I open a TT related to this issue and dump all my rpt's as full file there together with other files you might need?

And many other unlucky owners of ArmA 2 with the same problem posted their descriptions of bug and their rigs as well as the crashdump files.


As a thank you we got this from Maruk in another thread:

This fix mentioned there is already present in 58134
as available http://www.arma2.com/support/updates...r.html?lang=en

---------- Post added at 03:42 PM ---------- Previous post was at 03:40 PM ----------

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

Well, what now? Why you fix ArmA2 if it is Nvidia? Having since weeks a SW that I can not use made me not really calm.

So WHAT is now BIS's intention?

Saying to us: "bad luck, you have the wrong setup" - without saying exactly what the ideal, tested setup is?

And there are just 2 GPU manufacturers in the world, why is it not possible to make wider compatibility testing?

IMHO to many users having the same problems to point to single HW or driver issues.

If there is no serious intention go after the root cause within the next 1-2 months, please say it NOW, so that we have the chance to return our game now.

Keep in mind that your customers spend in addition to the 30+ Euro for your game additional 200+ Euro for a GPU upgrade or even few 1000 for a new rig, just to find out it is "incompatible".

Could Suma or Maruk give us unworthily customers a clear statement that what they intent to do and where they see their obligations?

Thank you in advance

The unlucky No-ArmA2-player

[Deadfast]

From reading the thread you quote you're not exactly the most helpful customer.


The only thing you posted was your video card name, so how comes you are surprised nobody from BIS is able to help you?

[S!fkaIaC]

From reading the thread you quote you're not exactly the most helpful customer.


The only thing you posted was your video card name, so how comes you are surprised nobody from BIS is able to help you?

Errrm, you are just lazy, that is all. With a little search you would find out that I even stated the colour of my underwear in case it matters. Search with my nick if you are able to do that. To help you and others I asked the moderators to merge all "Receiving..." threads (in addition by message), but they do not see the need.

And everything beyond reporting an issue is already far,far more then you can expect from a customer.


But this is not the point of this thread. I just want to know if BIS is behind that and if it is feasible to have a solution within the next months.

If BIS does not see any need to solve it on their side (or making attempts to) we can give up and return the game.

Since 1.02 we reset the device and continue running.

This is actually not true in my case (and few others). I interpret it in a way that in case of error the game should continue, but it does NOT.


Edit: I even asked a very popular game-mag for the specs of their systems.

They were very very open and told me that they NEVER had any "receiving..." bug on any of their test systems, but the smallest Nvidia was a 9800er. One tester mentioned that GF8/9 drivers are known to react like that in case of memory shortage.

Question is now: Is it a problem of ArmA 2 "overloading" the GPU or is it Nvidia handling it wrong?

Should we spoon-feed both BIS and Nvidia with the root-cause analysis backed up with PC-internal bus-traces and the necessary changes to ArmA2/Nvidia driver ready-to-implement?

Just to be accepted as "helpful customer"?

I am such a useless customer......

[Tiglet]

yep, I have the same issue, just during play it goes over to a black screen and it flashes receiving non stop, makes me extremely pissed tbh...

[ahmedjbh]

Im sure they are working on it.

Stay cool, BI havent let us down so far, why would they change?

[FlunkyMonkey]

Im sure they are working on it.

Stay cool, BI havent let us down so far, why would they change?

Everyone would shut up if they just TOLD us they were working on it ffs!

They are treating us like we are their step-parents on thanksgiving

[No1sadvocate=US=]

well. memory leaks can be hard to find. But one this massive... idk. Code mistakes cause them. I'd imagine there will be a patch solely for this problem.

[S!fkaIaC]

Im sure they are working on it.

Stay cool, BI havent let us down so far, why would they change?

Could you stop spamming such nonsense? I am a BIS customer since 2001 so I see the cow flying.

[mc sonar]

very good idea S!fkaIaC!

thank you for this, cause i have this problem now since i have arma2
and i am just a few seconds away to uninstall and forget about this dream of a nightmare....

i love bis, i love arma2 deep behind my artificial heart valve....but i can not play - i can not play this

[S!fkaIaC]

well. memory leaks can be hard to find.

WRONG! EAAAAAAAAAAAASY!!! I invite both BIS and NVIDIA into my home, I will provide housing, barbecue, beverage and a fucked up system and/or ArmA2, they can provide their competence. It takes me 10 minutes playing and I reproduce the bug for sure and they can start slapping the arguments around their heads about who might be guilty.