erbarma

Carrier Command: Gaea Mission – Beta Performance Analysis http://www.dsogaming.com/pc-performance-analyses/carrier-command-gaea-mission-beta-performance-analysis/

Now some of us are playing the Beta again and again. Hopefully BIS will support us with patches soon. Maybe key bindings and gamepad bindings too. (both analog stick buttons are unset at the moment) On the other hand Community can do work by their own and with every new patch Community can optimize their voice recognition solution. Then on game launch in September Community can present a nice solution from the beginning. Maybe BIS can support it too so it is recognized by game magazines and ratings. But solution licenses and sources must be clear. Personally I do not have time and I am not deep enough in forum and Community stuff but maybe someone can take over my idea. Thats because I write this comment. Solution I know is Glovepie http://glovepie.org/forum/ http://glovepie.org/index.php (not be confused by glovepie.org/index.html) http://glovepie.org/glovepie_download.php I tested Glovepie with M&B Warband Brytenwalda Mod and ArmA 2 Maybe there is a better and more open solution out there. Tell me. An official ingame voice recognition from BIS especially later for console ports would be nice but I think there is not time enough. Gaming magazines were impressed by voice recognition of Tom Clancy's Endwar on consoles but gameplay was not deep enough.

Because of my switch to a 24 TFT long time ago an the Release of ArmA 2. I baught a new GPU. It is time to play my favorite Games in native Resolution 1920x1200 now also my TFT can handle the non native Resolution 1440x90 very good. HD4870 with 2048 M VRAM I know 2048 MB VRAM make no sense for other Games also on 25601600 TFT. GPU and CPU needs more Power. And my CPU and my AGP/PCIE-DDR1/DDR2 Board is limited by ArmA2 4CoreDual-SATA2 with E5200 overclocked to 2x3.16 GHz because of Creative xifi that produces sound glitches with higer FSB also PCI is fixed to 33 MHz in Bios. I have 2*2GB/800Mhz DDR2 limited to 3,3 GB limited by the Board and alternative Bios Firmware. ArmA 1 and ArmA2 are placed on an Intel X25-M SSD drive. I prefer Vista/Windows 7 64bit because they can handle HDD and VRAM much better. VRAM usage comes to 1 GB and higher, ArmA 2 cannot display Textures correctly with XP 32bit. Both use newest ATI Tray Tool beta and Catalyst 9.6 I switched back to XP because I want to see the VRAM Usage in ArmA 2 (ATI Tray Tool, Everest, Rivatuner ...) Not possible with Vista or Windows 7. I used the ATI Tray Tool Overlay. very high/sehr hoch ... ArmA 2 ignores 1350 MB VRAM I prefer very high/sehr hoch at the moment, because in many situations there are 15 frames more. To handle smal village fights or smoke. On the other hand default/Voreinstellung has some nice advantages. Switch to Sniper/Google Optics, approaching big city, flying or driving through whole world or playing on busy servers which limit client frame rate. Exploring in Editor with 20 FPS/default is same situation is nicer than 30 FPS/very high. In ArmA 1 I use default/Voreinstellung because the Requirements spend less resources. The handling with textures and objects is very smooth and I have enough frames.