The Dreaded Receiving Error (A Question About It)

[The Dreaded Receiving Error (A Question About It)]

I'm not saying it is. It may just be that the current drivers don't "clean up" whatever the multiplayer is leaving behind. Since i restarted its not working again... I'm so confused.

[The Dreaded Receiving Error (A Question About It)]

omg! I AM KEEPING IT FROM HAPPENING!!!!!!!!!!!!!!! I CAN PLAY. The only thing i get is a 5 second receiving screen every few mins. I just totally uninstalled the ATI drivers and installed the Omega Drivers for ATI and everything is kosher. I think the custom drivers have a garbage collection feature or something to clear the bad data. I don't really care. it works. But. I'm scared to restart because i didn't restart at all since uninstalling the ATI drivers. Even though it said to. I'd imagine that the new ones HAVE to be working if I'm playing the game. www.omegadrivers.net

[The Dreaded Receiving Error (A Question About It)]

My question to those of you who feel that it is a RAM/Page File situation is whether or not video information is stored in page file/ram. I know for a fact that it is graphical because my log states the crash is caused by not being able to load textures.

Hm. All very interesting. BIS Should fix it though, it has been happening to a number of people. As with so many others, I really like the game in the time i can play it. I'm frustrated that I spent my $50 and 3 weeks later we still dont have another patch.

[The Dreaded Receiving Error (A Question About It)]

Ok. So i get the receiving error. Like so many others. Flushing extends the amount of time before crash. But I only get it in multiplayer. Why? if there is a graphical memory leak, why would it only affect my multiplayer games?

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

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

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

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

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

I am beginning to wonder if you started this thread to Troll it...

It absolutely CAN Take a long time to find a memory leak depending on what you're working with.

Have you personally ever debuged a program much less a Graphics Engine?

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

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.

[Issue With Direct X.]

Excuse me if I'm posting a common error, but I have not seen it yet on here.

So. I've had to restore my computer 4 times in the past 24 hours because of directx errors. I (like so many others) am encountering the receiving... memory leak. I set my memory to low to prolong my time before crash. Not only do i get the crash. Somehow steam overwrites my DirectX files with older/incorrect versions. If I try to re-launch arma post-crash I get a D3D9_InvalidCall. Even if i try to launch COD4 I get a "directx is the the current version, or is not configured correctly" or something along those lines. Why/How can it be doing this, I've tried deleting the Direct X install files from my Arma Directory but I think Steam re-writes them. Next I'm going to try making my DX files read-only.

Any Ideas?