quantum112
Member-
Content Count
19 -
Joined
-
Last visited
-
Medals
Community Reputation
10 GoodAbout quantum112
-
Rank
Private First Class
-
[ARMA 2:OA] "Receiving..." while in-game
quantum112 replied to quantum112's topic in ARMA 2 & OA - TROUBLESHOOTING
Hey, check this out. I installed Windows 7 64 this afternoon, and after reinstalling the game and checking Arma2OA.cfg; localVRAM=2131763200; nonlocalVRAM=1878253568; So far I have not been able to reproduce the "Receiving..." in the editor, and I've dive-bombed the hell out of Feruz Abad from 3000 meters in the air for like 10 times... I hope I haven't spoken too soon. Still have to test multiplayer. -
[ARMA 2:OA] "Receiving..." while in-game
quantum112 replied to quantum112's topic in ARMA 2 & OA - TROUBLESHOOTING
Tried both yes, didn't seem to make a difference. In the mission editor the screen takes 3-4 seconds, and during that time since it is local, I guess the game stops. But in MP, the server keeps my plane running while I can't control it and that's a big problem. Drivers for this card have been flaky since release, I don't know...maybe I can try with Windows 7. I'll probably switch to nVidia next card as well :) -
[ARMA 2:OA] "Receiving..." while in-game
quantum112 replied to quantum112's topic in ARMA 2 & OA - TROUBLESHOOTING
Video memory is set to Very High, I'll try other values. Single 4870X2, so two cores with 1 GB VRAM each. localVRAM=1073741824; nonlocalVRAM=123076608; I'll try what you mentioned. By the way, are you using the same in-game name? If so we may have played together yesterday, I was on a side-mission only server (forgot the server name) playing as OPFOR, there was someone called TonyGrunt driving a captured M1A2 Tusk, the mission was to destroy enemy tanks. Was that you? :P My name was Arx. @Günter I'm not the host, I don't think I can affect those settings locally. It seems to be a local issue as it happens even on an almost blank map in the mission editor. Update: I've changed the Video memory to default, and after a few passes across the map and a few (Receiving...), stuff like this happens now. Alt-tabbing to and from the game made the textures reappear again. Any clues? -
[ARMA 2:OA] "Receiving..." while in-game
quantum112 replied to quantum112's topic in ARMA 2 & OA - TROUBLESHOOTING
Domination. Co30 DomiOA West [2.60zc] AI RA is the map. -
This is an error that I get quite often in Arma2: CO, only when moving quickly (airplanes and sometimes helis). I get a black screen with "Receiving..." on it. It takes ~10 seconds for this screen to go away, during which the controls do not respond, and by that time I am thankfully already dead. Very embarassing in multiplayer. If I am dive-bombing from high altitude in fighter jets this will happen every time, both A-10 and F35B, presumably because all the textures have to pop in so quickly. Right as I am about to pull up, this dreaded screen pops up and in a few seconds all I can hear is *booom*. Is there anything I can do to make airplanes actually playable? My system: C2Q Q6600 @ 2.4 GHz 4GB 1066 Mhz Mushkin DDR2 ATI HD 4870X2 2 GB XP 32 SP3 Samsung SpinpointF1 1000 GB 7200 rpm (game install) WD Caviar 160 GB 7200 rpm (page file 4 GB) Game patched with latest beta (same thing even with non-beta patch), all drivers latest, 1 month old clean install, etc. No mods or anything ever installed. No overclocking. This happens in mission editor as well.
-
...what? No. Anyway, I managed to fix this by opening up my ARMA2OAPROFILE file in My Documents and finding the line that says "keyNetworkPlayers[]={};" I removed the number in the {} brackets and that unbound the key. The problem was in the fact that the player list key was -not- listed in any of the controls ingame, so there is no way to change it without tinkering with the config file. Also, arrow keys are totally impractical, there is nothing in the vicinity to be used for reload, prone, and all the other functions you need to have at hand in ARMA... The setup I'm using is basically a mirror of WASD in that you have enter, backspace, space, alt, control, shift, and all the other keys right next to where your movement keys are.
-
Hi, I have a dumb problem here... namely the player list key is 'P' and I can't seem to change this. I'm left handed and I use "PL:" " key configuration so P is my move forward, naturally whenever I press this the player list comes up ... really irritating. Is there a way to change this control? Thanks
-
Win 7, 5.1 sound over Digital
quantum112 replied to quantum112's topic in ARMA 2 & OA - TROUBLESHOOTING
Would really appreciate some input on this...stereo is not very fun :confused: -
Arma 2: Combined operations not showing bullet count and zeroing
quantum112 replied to xoroku's topic in ARMA 2 & OA - TROUBLESHOOTING
You're welcome ;) -
Arma 2: Combined operations not showing bullet count and zeroing
quantum112 replied to xoroku's topic in ARMA 2 & OA - TROUBLESHOOTING
Make sure ArmA2 has the latest 1.07 patch. Had the same thing and installing the patch fixed it for me. -
Win 7, 5.1 sound over Digital
quantum112 replied to quantum112's topic in ARMA 2 & OA - TROUBLESHOOTING
Hmm, close, but no cigar. I did a test. I placed a T90 tank on the runway, started the engine then went out and walked around it. Only the front and center channels actually played the engine noise, and it wasn't too reflective of the way I turned around. I heard only some kind of bird chirps on the rear channels every once in 10 seconds or so. To compare, I did this same test using analog output, and as I turned around with the tank behind me I could clearly hear the sound moving through all the speakers according to how I turned. Not so with Digital Output (it's still using pure stereo :/ ). Thanks for the idea though. I guess it is already using OpenAL or I wouldn't be getting 5.1 even in analog. Anyone else have ideas feel free to chime in :) -
Hello. I am having trouble getting ArmA2 (& OA) to output 5.1 surround sound over a digital output. I have a Gigabyte GA-X48-DQ6 motherboard with the Realtek ALC889A chipset, latest Realtek drivers 2.51. OS is Windows 7 64 bit. Speaker system is Logitech Z-5500 with in-built decoder that supports DTS and Dolby Digital. Here is the issue: using standard 3.5mm analog plugs (the 3 of them), I get 5.1 sound with no problem. This is because of the way ArmA detects sound configuration: by reading the settings in control panel or drivers. All fine. Unfortunately, the sound quality of onboard analog sucks, and I'd much rather prefer to use the optical output. The problem with this is, it goes through a separate device called Realtek Digital Output. As we all know, Digital signal can only carry 2 channel PCM, unless the signal is encoded with DTS or Dolby Digital - my motherboard supports "DTS Interactive (5.1 Surround)" option. When I tick that, the same option gets selected in the control panel, and if I use this option I get working 5.1 in pretty much all other games which normally support it. However, since ArmA reads this info from the control panel, I am guessing it doesn't know what to do with "DTS Interactive (5.1 Surround)" (as it doesn't say how many speakers exactly there is, and you can't use the Configure option like you can for analog to set Stereo, Quadraphonic, 5.1, 7.1 etc) so it assumes the default - Stereo, and as such I only get sound from the left or right. Is there a way to force ArmA2OA to output 5.1 regardless of the control panel because my gear is obviously capable of giving 5.1 over Digital output, yet the game assumes it can't (shoddy coding, this. There should be an option in game to select what speaker configuration you want to use...) Thanks
-
No, they're within a specific folder for games, not in program files. Running XP 64 and I'm the administrator, so no issues with that either.
-
Not sure why you're not seeing it, works fine for me. It shows the HUD of aircrafts/helis, the boxes where it shows SPD and ALT are empty. And yes, on the first one there is no ammo readout. Nor in vehicles, or for any gun for that matter.
-
Yep, I did that, and it seems to no longer crash. But look what's still happening. How to fix this?