JGPrince
Member-
Content Count
6 -
Joined
-
Last visited
-
Medals
Community Reputation
1 NeutralAbout JGPrince
-
Rank
Rookie
-
Recieving black screen, game unplayable
JGPrince replied to Avgeris's topic in ARMA 2 & OA - TROUBLESHOOTING
Hi guys, I know it's a thread resurrection, but was this ever solved? I'm getting the same issue now two and a half years later on an ATI Radeon HD 4300/4500 video card, and after a week of fiddling with it and trying every solution I've found, nothing works. Was this ever fixed? -
Arma2CO MP Crashes with audio loop
JGPrince replied to JGPrince's topic in ARMA 2 & OA - TROUBLESHOOTING
Well, we swapped video cards -- mine performed better than his, but the receiving bug still bit him. It recovered, but the card was problematic. We swapped back, even taking out a stick of ram reducing it to 2 gigs, but the receiving bug still happened. a handful of times it would recover, a few times it required a hard reboot, and the rest he still had to close the game. Short of a hardware upgrade -- which I will protest to because the computer easily meets the minimum specs, what can be done? -
Arma2CO MP Crashes with audio loop
JGPrince replied to JGPrince's topic in ARMA 2 & OA - TROUBLESHOOTING
Well, we tried again tonight, same settings as before, and the same error. 5 minutes in the receiving bug bit and he could not recover. It seems the issue was common in 2009 but not so much now, so what is causing it? -
Arma2CO MP Crashes with audio loop
JGPrince replied to JGPrince's topic in ARMA 2 & OA - TROUBLESHOOTING
Thanks, I'll give that a shot now. I posted a reply, but the forum said it needed mod approval. Basically the reinstall helped, we got 3 hours of play time, but then the issue came back and is as bad as ever. A few times it recovered from the Receiving bug, but then failed to do so. I tried it again today to see if I could examine the .rpt file, and got the bug within 3 minutes (haven't updated the page file yet), and here is what the Arma2 OA.rpt file says about today's crash: ---------- Post added at 20:04 ---------- Previous post was at 19:40 ---------- Well, I increased the page file from a variable 1536-3072 to a fixed 4606, what the system recommended. Within 3 minutes I got the receiving bug again, but it recovered after 10-15 seconds. I played for another few minutes until I died, then just as I respawned the bug hit again and would not recover. The rpt file: I'm at a loss, I've tried the various suggestions I've seen of extra cooling, increasing the texture memory from the options, decreasing it and the graphics, all to no avail. ---------- Post added at 21:01 ---------- Previous post was at 20:04 ---------- Well, I tried one more thing. I adjusted his graphics to match my wife's, set his video memory to normal, and on his Catalyst software enabled the VPU recover. Played it, within 3 minutes got the receiving bug, it came back after 20 seconds, and then I played for about 50 minutes on his machine without a hitch. It's not conclusive -- we got 3 hours in last night before it came up, but I'm hoping that the VPU recover (which resets the VPU without a restart) helps. Here's the latest entry in the .rpt: -
Arma2CO MP Crashes with audio loop
JGPrince replied to JGPrince's topic in ARMA 2 & OA - TROUBLESHOOTING
So an update, we completely reinstalled the games, first just Arma 2 (instead of CO), then Reinforcements with Operation Arrowhead. It worked great for a three hour match of coop domination, and then started up again. Only this time, the graphics went dark and he couldn't do anything, but the audio was not buggered, and the various chat messages continued to appear on his screen -- but the rest was dark with "receiving" perpetually showing. I then found this thread: http://forums.bistudio.com/showthread.php?t=78474&page=14, and set his video memory to very high, instead of normal. It worked fine for about half an hour, then did the same thing. I think tried it to default, and for two hours it kind of worked, the receiving issue would come up but alt-tabing out and then back into the game caused it to work again. And then that stopped working. So, we're at a loss. The three of us usually just play together so we can occasionally work around it, but it really limits his ability to fly or do other things. Any suggestions? The thread I linked to above hits the issue almost exactly, but I didn't notice a fix or workaround, and as the thread is two years old I would hope that one exists now. Thanks for any help! -
Hello all. I'm having some issues with Arma 2 CO+BAF+PMC, or rather my father is. I'm a long time Arma player, even back to OFP, and got my wife into playing it, and finally got my father into playing as well. We love doing LAN missions whenever we can, but we're having some issues. We all have ArmA2 CO with BAF and PMC, and while my wife and I run it just fine, it keeps crashing on my dad's PC. I forgot to mention we are all running 1.60. My wife has them all from Steam, I have the retail Arma2CO with the BAF and PMC dlc, and my dad has the retail Arma 2 CO and retail Arma 2 Reinforcements. His system specs are: AMD Phenom 8250e Triple Core 1.9ghz 3gigs DDR Ram ATI Radeon HD4300/4500 Series Onboard ATI Hi-def sound, basically whatever was on the motherboard. This is identical to what my wife's computer is, except that she has 2 gigs of ram, an Nvidia Gefore 9500GT, and both have the same processor and use onboard sound. Yet she can play it just fine. It even runs fine on mine, and I've got the same video card and ram as my wife, but with a 5 year old Athlon 64x2 Dual Core 4200. So I can't understand why his is not working, even on lower settings. What happens is if he plays missions or maps from Arma 2, the game works fine. But when he plays something related to Takistan and OA, it will randomly while he's playing go to a black screen with looping audio and the words "receiving" permanently displayed. He can't access the menu or do anything, BUT he can continue to type chat or use his mic, and we can read/hear him on our PCs. It doesn't hard lock the system, he just has to alt-tab or control-alt-delete to kill the game. I've updated his directx and his video card drivers, and we're trying a complete reinstall to see if that helps. I've seen some people say it could be a cooling issue, and right now we're using the Catalyst drivers to force a perpetual 85% fan speed, have the side of his PC case open, and have another fan blowing into it, but it hasn't helped. Any and all help is appreciated, thanks!