Calamity_Cruse

I have a set of Saitek Pro Flight rudder peddles. This unit is recognized by Arma II. The Yaw (Main rudder peddles motion) is recognized as the Y-Axis. But also both toes tip forward, something flyers will recognize as "breaks" in a flight sim. Arma II recognizes this as Left Toe: X-Axis, Right Toe: Z-Axis. I've got Arma II configured to use the Right Toe to Move Forward, thus freeing up my finger from the fatiguing task of holding down the "E" key, and the left toe as Move Backwards. But herein lies my problem: Like all other Axis controls, Arma II breaks up the motion of travel into +[Axis] and -[Axis]. This is fine for Joy sticks, and even the rudder peddles Yaw motion, because springs hold the axis in the middle of it's movement., but the toe axis motions are different. They start at one range of motion (a value of 0) and travel in one sweeping motion to the other rend of travel (a value of 65,555). Because Arma II will only recognize +[Axis] and -[Axis], I have to tip my toe to the half way point (a value of 32,777) before the game starts to recognize the input. I want to know if this is something that can be changed, an INI file perhaps, so Arma II uses the whole range of motion, 0 to 65,555, for forward movement, instead of the current 32,777 to 65,555. Any one have any ideas?

Hey Guys, Sorry I haven't been keeping up with this thread, but I've been tackling some hardware issues with the Vendor. For a while I stopped playing Arma II, but after I replaced my X-45 with an X-52 Pro and started suffering BSOD's (Blue Screens of Death), I thought I should have my system checked out. Turns out that since I purchased the machine from HP in August, I've had to replace my hard disk (Not related to these problems, but does illustrate how much of a lemon I have), the Mother Board, and now I've got a replacement video card I'm waiting for the warranty tech to come and replace in the morning. Meanwhile, this weekend I've been doing some more play testing. I'm working around the SaveGame bug by re-naming the save files before allowing a new one to be created - either a manual save, or an autosave. I've been limiting my speed as I drive through towns to about 20 to 25 MPH. I speculate that this gives the card enough time to load the texture maps of all the buildings. But I'm still getting the occasional triangles that replace the scenery, and buildings blinking in and out. Then the game will crash to desktop. After that happens, I have to go back to the last save game before the triangles, because once they've been introduced they corrupt the the save files and the frequency of occurrence increases. All this is, of course, is with the suspect video card. After the video card HP will have me swap out the memory, then format the drive and re-install the op-sys. After that I'm throwing in the towel and returning the box. But, if it does become stable (No more BSOD's) and I still am having problems with the game, I'll pickup this trouble thooting thread again. Calamity.

I'm having this same problem too. System: CPU: I7 920 @ 2.67Mhz RAM: 6Gb OS: Vista 64 HD: 640Gb (Dual SATA 320GB in RAID-0) VIDEO: GeForce 9600 GS W/756 Mb Ram I've updated the Nvidia Driver. Checked the Temp with EVGA - 52 Degrees C. Tried the in-line command string "-maxmem=2047 -cpuCount=4 -nosplash", and when I entered the game I was able to run it for about 2.5 minutes. Drove my Humvee into Krasnostav (I'm playing Manhattan in the campaign) and whamo! Game crashes. I'm also getting crashes to desktop on Save-Game (During the campaign missions), Getting lockups and crashes in the Scenario "01: Trial By Fire" - which I read in another forum post was supposed to be more stable. I've had the spiky artifacts, lost terrain texture mapping, and ultimately had a crash, in two of the "Armory" Missions - and of course the Manhattan campaign mission where everyone else is seeing them too. All-in-All the Game is not "Ready for Prime time". I'm an old OFP player, Mission Writer, and Mission Reviewer. I was on staff for a couple years at the old OFPed.com as "Calamity". I must say I'm really disappointed here. I've been waiting years for an update to OFP. Right now I'd be giving this a 0.2 overall. I'm pretty sure BIS will get this fixed, but my patience is wearing thin. What's the next thing to try? Any patches for English/American Vista 64 yet? Let me know, Calamity out.