tjhowse

Works perfectly for me. Well done!

It's probably a matter of tuning your settings. If it's too jumpy try bumping up the average a bit. Also note that if you have your camera (wiimote, ps3eye, whatever) mounted on top of your monitor and your desk or monitor wobbles a bit, you're going to see jitter ingame. This is true of any head tracker. Here are my settings for my wiimote setup: Profile tab: Yaw Sens: 1.3 Pitch Sens: 1.4 Roll Sens: 1.5 X Sens: 1.0 Y Sens: 0.5 Z Sens: 0.1 Smoothing at 50 on all. Advanced tab: Zoom Smoothing Multiplier: 1 Dynamic Smoothing Reduction: 3 Average: 1% Curves: Make sure you adjust the point model parameters on the model tab to the dimensions of your clip. I made a 3-point-clip with dimensions 60/60/80/80. I have the model position settings set to pretty much zero.

Remember if you're not afraid of perfboard and a soldering iron you can whip up a perfectly functional head-tracking system out of a wiimote (or any other webcam) and Freetrack: http://www.free-track.net/ . Here's a video showing off my setup: . I use this and a TM Warthog, it's awesome.

Works at 1680x1050. Nice job. I have it bound to clicking in the mic switch on my warthog.

There is a setting in the DCS: A-10C menu which says "Sync HOTAS on startup", or something to that effect. This will solve the problem you're having. My problem can be described thusly: TM Warthog EAC switch example: Game starts, EAC ingame is off, but switch on warthog throttle is on. Player flicks EAC switch on warthog throttle to off, EAC swich ingame doesn't move. Player flicks EAC swich on warthog throttle to on, EAC swich ingame turns on. AHCP TGP switch example: Game starts, TGP switch ingame is off, homemade AHCP TGP switch is on. Player flicks homemade AHCP TGP switch to off, TGP switch ingame toggles to on. Switches out of synch. Must manually resync. Because the TGP switch doesn't have separate on and off commands, unlike the EAC switch, I can only toggle the state of the TGP switch upon state change of the TGP button from my homemade AHCP.

When I was setting up a home-made AHCP the only way I could find to bind a switch to, for example, TGP on/off was to make it fire a toggle on either the up or down signal from the the joystick button that represents the TGP switch. I can't work out how to make it send an absolute command, rather than just a toggle. If I don't have all the switches set to the correct positions upon startup then my switches get out of sync, requiring clicking in the cockpit to get them aligned again. I was wondering why the AHCP seems to be a second class citizen in terms of available bindings, when other panels have individual commands for the on and off states, like the EAC switch: EAC: Individual state bindings {down = iCommandPlane_EAC_ARM, name = 'EAC Arm' , category = 'LASTE Control Panel'}, {down = iCommandPlane_EAC_OFF, name = 'EAC Off' , category = 'LASTE Control Panel'}, TGP: Toggle {down = iCommandPlaneAHCPTGPOnOff, name = 'TGP switch ON/OFF', category = 'Armament HUD Control Panel'}, Does anyone know why this is the case? Does anyone have a workaround? Thanks, tjhowse.

I used an arduino uno with some custom firmware on the 8u2 chip to emulate a joystick. My AHCP shows up as a standard HID joystick in windows with 20-something buttons: http://forums.eagle.ru/showthread.php?t=71935 If someone wants I can provide the source code for the arduino and the 8u2 chip.

$100 in parts and about six hours to build, including writing the firmware for the serial chip and the microcontroller. I just need to get the labelling sorted out now, I'm thinking acid etching wouldn't be too hard.

I don't mean to tell you how to suck eggs, but are you using PAC-1 to help with the clustering of your rockets? It does help significantly. P.S. Same temphage from NS forums?

I'm looking at buying some small external screens to offload the MFCDs and I was wondering about the resolution of the MFCDs in the actual A-10C. I'm told the F-16's MFDs are 524x524. Thanks, tjhowse.

I'd just like to chime in and thank SFJB for his awesome profile! Saved me a lot of work, and it's probably better than anything I could've come up with. Good job!

Shortly after I posted that I duplicated my setup in the other option available in the drop-down box in the upper left of the controls configuration page. There were two, "game" and "sim". Now that they're both the same, everything works as expected. Nate's solution would've worked only if you'd selected the correct option on the gameplay options menu down the bottom left, "Simulation" or "Gameplay". It seems that a checkbox on the gameplay options menu denotes which control scheme that mode of game uses. Hope this helps, tjhowse.

I can confirm that joystick axes behave differently between generated quick missions and training missions, without any change to any configuration. I have an X52. I have the throttle, Z axis, set to combined throttle. Z rotation is on yaw. I have the slider on the throttle, "Slider" set to send keypresses at 5% from the limits for controlling the airbrakes. In other words, I have SFJackBauer's setup. When starting a training mission, any training mission, the engines won't start unless the switches are in the proper position and the throttle (Z axis) is on 0. The engines can be moved from "Off" to "Idle" by using RAlt+Home and RCtrl+Home, at which point they spool up and everything's peachy. HOWEVER, If I start a randomly-generated mission, using the "Create Fast Mission" menu option starting from the ramp, I get ingame and the engines will not go from off to idle unless the slider axis is on zero. Once it's on zero, the engines can be started. At this point it becomes obvious that the ingame throttle has rebound to the slider, since the slider can be moved from limit to limit, controlling the ingame throttle. The X52 throttle axis (Z) has no effect. Hope this helps, tjhowse. Edit: I can confirm that if you create a fast mission starting from the runway instead of the ramp, the same problem is manifest. None of the training missions I've tried (Startup, takeoff and maneuvering, navigation, weapons systems) show this problem.

Bohemia interactive support both TrackIR and Freetrack. You can select either or both in the controllers menu.

I'm having trouble understanding this. Who requested the removal of the other free headtracking application? It's just another input device. It would be akin to a particular flight simulator game only working with a certain brand of joystick. I reiterate: BIS added freetrack support into ARMA2 with a recent patch; what's preventing ED from doing the same? Thanks, tjhowse.

Hi, I know this is somewhat of a hot question in some circles, and I've looked through the stickies and found nothing newer than five months old on the subject, but I'm wondering if there's a chance that A-10C will support freetrack nativley either now (in the beta which I'm currently downloading) or once it is released? I was exceedingly impressed with Bohemia Interactive Studios when they added freetrack support to ARMA2, they've got me as a customer forever as a result. I would like to see Eagle Dynamics do the same. Thanks, tjhowse.