cobracmndr

It seems that if you are a PMC unit equipped with a Laser Marker and Batteries, you can mark a target, however other players, nor AI units will detect it as a target. This also appears to be the case if you are the gunner in the Wildcat or the Venom, using the Laser Marker there. If I swap my unit to a US Rifleman, everything works as expected. Has anyone else noticed this issue?

Has anyone had any issues picking up another player's laser marker? I have done this a few times without any issues in Takistan with OA, however on Chernarus with CO, I have yet to see this working.

Bingo. I'm using a Soldier_PMC but occasionally play as a Soldier_Pilot_PMC. That explains the seemingly intermittent nature of the issue. Thanks!

Hello, Occassionally the gun sights in all the aircraft are skewed to the left. Specifically, the crosshair (plus sign) will be about 1cm to the left of the aim point on the HUD. When it's working correctly, the two overlap perfectly. I cannot seem to repro the issue and do not know what to do about this. Any ideas? cobra

Hey gang! UNIT555 now has a dedicated 100Mb server that is online and open to all players. UNIT555 is not a clan or a group in the traditional sense. There is no formal game schedule and you don't need to add any tags to your code name. Instead, we are a mixed group of players from around the world that enjoy playing the game in a co-op, teamplay atmosphere. We put a lot of emphasis on planning the mission and using in-game VON to communicate. We primarily play variations of Takistan/Chernarus Force, by Bon_Inf. We have our own custom versions that we routinely update based on player feedback. If you haven't played TFOR/CFOR, it's a task-based mission with dynamic missions, OPFOR strength and random surprises, such as patrols, camps, ambushes and IEDs. It's similar to Evolution, minus the ranking system and with more variety. If you think you might enjoy playing with a crew of mature players that take the game seriously (but not too seriously), look for the UNIT555 server. Presently we are running CFOR v1.04, which means you will need Combined Operations to play (since it uses Chernarus and USMC equipment). Looking forward to seeing some new faces in-game! cobra

I am experiencing frequent freezes and I have noticed that they tend to happen after using the scope. What happens is that the frame rate drops and the game stutters until the gaps between stutters is less and less frequent, resulting in a complete freeze. I too am using the "Very High" RAM setting. My resolution is set to 2560x1600 with 1920x1080 3D res. Hopefully this adds a few more details to assist in the debugging effort.

baz: Thanks for confirming. Did you try setting max mem to 4GB in Windows 7 via "msconfig"? I'm wondering if that'll work rather than physically removing the DIMMs. I am going to try that approach this evening if I get a chance to play.

Baz: Did you have > 4GB of RAM and this issue, too? teaboy: The values are back to: localVRAM=1576468480; nonlocalVRAM=2147483647; Any suggestions on what I should hard-code these to? Both are less than the physical amounts, so I don't see how this would result in an out-of-memory issue. Should I lower them or increase them to match the exact physical limits?

Should I be seeing the values in the CFG file changing from zeros back to whatever it has detected?

Is it because I'm hosting that it happens to be before the other players?

Sadly, the game has crashed again. It did manage to stay up for about 3 hours. Not sure if that's coincidence though, since it lasted that long before. ---------- Post added at 12:12 AM ---------- Previous post was Yesterday at 10:42 PM ---------- :( This sucks.

Hi teaboy, I used to get a CTD that would say "Out of memory", which has happened with 1.56 and I *think* at least once with 1.57. These freezes, however, do not cause a CTD. The process just hangs and needs to be ended via Task Manager. Could it still be an "Out of memory" error? BTW here's my ArmA2OA.cfg: Note: The 580GTX has 1.5GB of onboard memory, so I think "localVRAM=1576468480;" is correct. I'll give your suggestion a try though! It definitely feels like when the video card has to pull some serious weight, that it freezes. It actually feels like a recursive loop that eventually locks everything up. ---------- Post added at 07:43 PM ---------- Previous post was at 07:35 PM ---------- Just ran AIDA64 and I can see that i have 1536MB of VRAM, which works out to 1,610,612,736 bytes. I'm about to try with "0" and see what it detects, but am wondering if I should hard-code it. The issue with detection seems to be one of it detecting *more* VRAM than you have, rather than less (as in this case), no? ---------- Post added at 07:57 PM ---------- Previous post was at 07:43 PM ---------- Just changed the ArmA2OA.cfg to: Re-ran the game (Steam > Library > Arma AO -> Launch Combined Ops) and the values in the .cfg are still zeros. Weird?

The only mods that are running are PMC and BAF. Could it be a script in a mission?

Hello, I'm running Arma 2 CO (Steam) v1.57 and am finding that the game freezes when playing in multiplayer. It has not frozen during extended (several hours) use of the editor or 5-10 min sessions in the "preview" mode. When the game freezes, the screen stays stuck on whatever frame it froze on. If I Alt+Tab out, I can't get back to Arma. Task Manager always seems to indicate that the process is using 13% CPU (clue perhaps?). OS: Windows 7 CPU: i950 GPU: 580 GTX RAM: 12GB MOBO: Asus P6X58D :confused:

I'm not having that *exact* problem, however I have been experiencing frequent freezes (not CTDs) where I can still hear some of the other players on VON (but not all) and they cannot hear me. The ArmaA2OA.exe process always indicates a "Not Responding" state and a CPU usage of 13%. This happens sporadically within either 5 mins to an hour of playing. CPU: i950 GPU: 580GTX Running A2 CO (BAF + PMC) v1.57