manual and take a look at one of your GUI config files via the GUI T.A.R.G.E.T. If you have no programming exerpeince, flip through (don't try to memorize) the T.A.R.G.E.T. Personally, I find the hats too sensitive for these types of button presses but if you want to get the most out of the HOTAS, you are better off learning to muck around in the scripts. I read about this in a thread recently (sorry - can't find the URL) so it can be done. Once you calibrate the afterburner position in SimAppPro, AB detent is also automatically aligned with the in-game throttle position in your F-16 cockpit. You may find it useful.Īs for mapping the 8-way hat, you have to use the scripting language and use the DirectX Mapping calls. It's not perfect but I was surprised as to how well I eventually got the slew sensor POV to work. It also uses the slew sensor to look around the cockpit.
Note that my config does not have the throttle timing issue so one can throw the throttle around as fast one likes without disrupting the calibration. I was able to add a 50% throttle and could add other percentages but at that point, I would rather just have a true analog throttle control.
#X WING COCKPIT THROTTLE PDF#
PDF mapping file as well as the mapping template for future games. Regardless, I will upload my custom script config in a separate thread. Not bad by any means but you can't move the throttle too quickly or it loses calibration. I've noticed that this throttle config has timing limitations as well. If you look at the in-game GUI and just go from 0% to 100% throttle you can just count throttle the bars. You are able to split the inputs into more than 30 intervals but the game's throttle control splits it into ~36.
0 kommentar(er)
