tjhowse

This very thread: http://forums.eagle.ru/showthread.php?p=1699631#post1699631

Has anyone worked out if there is a way to map both positions of the two-position switches on the A-10C AHCP panel? Specifically the TGP, hud mode day/night and norm/stby, CICU and JTRS? At the moment they only operate as a toggle when the switch is flicked on and off again. Previously I had it working such that whenever the "button" was pressed or released it toggled state, so it would work if the physical AHCP switch positions matched those in the sim. I would prefer for the switches to be always synchronised. The issue is that the up and down states have no explicit command. For example the GUN/PAC ARM switch has three commands: iCommandPlaneAHCPGUNPACArm iCommandPlaneAHCPGUNSafe iCommandPlaneAHCPGUNArm Whereas the TGP switch has one: iCommandPlaneAHCPTGPOnOff Anyone have a solution for this?

Most 3D printer software takes STL files. It's a pretty standard format that most 3D modelling packages can export. I use Slic3r to convert the STL into the gcode used to control the printer.

Have a look at my video here. I created a trim wheel box for the mustang using a teensy. I provided the code at the end.

Currently it should work just fine for UHF radios. If everyone's installed the plugin properly, and set their mumble settings as per the guide, you won't be able to hear anyone who's not on your UHF channel.

Wrong. He was working part time on the OR, part time at id Software and part time at Armadillo Aerospace. He quit id entirely last week.

You're talking about a cockpit-stabilised mouse cursor, rather than screen-stabilised. Just like the cursor on the TGP, which can be ground-stabilised.

I'm afraid not without significant effort. Unfortunately joystick buttons cannot be chorded in AHK. Workarounds are possible, but inelegant.

I went ahead and did that for you. The string of numbers and commas denotes the delays between the countermeasures being dispensed. For example: flareIntervals = 50,50,1000,50,50,1000,50,50 Fires three bursts of three flares, each burst separated by one second. A delay of 0 signals the script to stop parsing the list, which is automatically added to the end. #singleinstance force #NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases. ; #Warn ; Enable warnings to assist with detecting common errors. SendMode Input ; Recommended for new scripts due to its superior speed and reliability. SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory. ; Modify these to suit your preferences: ; ################################### ; The joystick number of your Warthog. Can change depending on system configuration. joystickNumber = 1 ; The delay between each countermeasure. flareIntervals = 50,50,1000,50,50,1000,50,50 chaffIntervals = 500,500,500,500,500,500,500,500 ; Adjust these to suit your keybindings. flareKey = {Del} chaffKey = {Ins} ; ################################### ; Don't touch these: ; The rate at which the scripts runs in milliseconds. checkRate = 50 flareCooldown = 0 chaffCooldown = 0 flareCounter = 0 chaffCounter = 0 flareFlag = 0 chaffFlag = 0 flareIntervals := flareIntervals . ",0" chaffIntervals := chaffIntervals . ",0" StringSplit, flareIntervals, flareIntervals, `, StringSplit, chaffIntervals, chaffIntervals, `, Hotkey, %joystickNumber%Joy18, goFlares Hotkey, %joystickNumber%Joy16, goChaff Loop { if ((flareFlag == 1) && (flareCooldown <= 0)) { Send, %flareKey% flareCounter++ flareCooldown := flareIntervals%flareCounter% if (flareCooldown == 0) { flareFlag := 0 flareCounter := 0 } } if ((chaffFlag == 1) && (chaffCooldown <= 0)) { Send, %chaffKey% chaffCounter++ chaffCooldown := chaffIntervals%chaffCounter% if (chaffCooldown == 0) { chaffFlag := 0 chaffCounter := 0 } } if (flareCooldown > 0) flareCooldown -= checkRate if (chaffCooldown > 0) chaffCooldown -= checkRate Sleep, checkRate } goFlares: flareFlag = 1 Return goChaff: chaffFlag = 1 Return

Your examples are very good, however I think if you worked a little harder at it you might have arrived at the following: #singleinstance force #NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases. ; #Warn ; Enable warnings to assist with detecting common errors. SendMode Input ; Recommended for new scripts due to its superior speed and reliability. SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory. ; Modify these to suit your preferences: ; ################################### ; The joystick number of your Warthog. Can change depending on system configuration. joystickNumber = 1 ; The delay between each countermeasure. flareInterval = 1000 chaffInterval = 333 ; The number of countermeasures dispensed in one activation. flareCount = 10 chaffCount = 10 ; Adjust these to suit your keybindings. flareKey = {Del} chaffKey = {Ins} ; ################################### ; Don't touch these: ; The rate at which the scripts runs in milliseconds. checkRate = 50 flareCooldown = 0 chaffCooldown = 0 flareCounter = 0 chaffCounter = 0 Hotkey, %joystickNumber%Joy18, goFlares Hotkey, %joystickNumber%Joy16, goChaff Loop { if ((flareCounter > 0) && (flareCooldown <= 0)) { Send, %flareKey% flareCooldown := flareInterval flareCounter-- } if ((chaffCounter > 0) && (chaffCooldown <= 0)) { Send, %chaffKey% chaffCooldown := chaffInterval chaffCounter-- } if (flareCooldown > 0) flareCooldown -= checkRate if (chaffCooldown > 0) chaffCooldown -= checkRate Sleep, checkRate } goFlares: if (flareCounter == 0) flareCounter := flareCount Return goChaff: if (chaffCounter == 0) chaffCounter := chaffCount Return This allows for easier customisation, and enables concurrent countermeasure programs with only a single script. If you wished to challenge your AHK skills a little more, I suggest you attempt to modify my program to allow different cooldown times to be loaded from an array. It would not be hard to allow for arbitrary patterns of countermeasures, rather than regularly-spaced programs. Of course, this is largely academic, as DCS' modelling of the effect of countermeasures is unclear, and countermeasure patterns that are used in real life may simply waste resources in this sim. Keep trying! :pilotfly:

Cool! :pilotfly:

I experimented with ftnoir with a PS3 eye without the filter removed, just doing face tracking. It worked pretty well, though not quite as responsive as my freetrack+wiimote setup. Can you provide a screenshot of the video feed from your camera with the IR pro clip visible?

Mine is now working too, with freetrack and http://forums.eagle.ru/showpost.php?p=1234317&postcount=28 in the .\bin\ directory rather than .\bin\headtracker\ . [url=http://forums.eagle.ru/showpost.php?p=1234317&postcount=28][/url]

I'm in the pro-rift camp, mostly because whatever John Carmack touches is generally technically great. I predict that many games that use the rift will implement a kind of "squint" button, which will zoom your view slightly to allow a closer look at a whatever you're looking directly at. This will alleviate most concerns about distant (bogies) and/or fine detail (dials) being difficult to see. If it's done properly it shouldn't be disconcerting.

I don't use profile software; Target or Saitek, when I can avoid it because I don't like installing buggy third-party software to do something small and simple that I can do myself and tweak to my heart's content. Also, an autohotkey script has a much lower memory footprint than a bloated profiler.

I wrote an AutoHotkey script to enable wheelbrakes in FC3 using rudder pedals with axis toebrakes, such as my saitek pro flight combats. 1) Download and install AutoHotkey. 2) Paste this into notepad and save it with an ".ahk" extension. #singleinstance force #NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases. SendMode Input ; Recommended for new scripts due to its superior speed and reliability. SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory. ; If your system has more than one joystick, edit this value to use a different joystick joystickNumber = 5 downFlag = 0 upFlag = 0 loop { GetKeyState, joyx, %joystickNumber%JoyX GetKeyState, joyy, %joystickNumber%JoyY if (((joyx > 50) || (joyy > 50)) && downFlag != 1) { Send, {w Down} downFlag = 1 upFlag = 0 } if (((joyx =< 50) && (joyy =< 50)) && upFlag != 1) { Send, {w Up} downFlag = 0 upFlag = 1 } Sleep, 50 } return3) Edit the "joystickNumber" variable to the enumeration of your rudder pedals in the windows game controllers list (start -> run -> "joy.cpl"). On my system this appears as follows: 4) Make sure that "w" is bound to your wheelbrakes in FC3 on each aircraft. 5) Run the script. Note that you may have to change the lines featuring "%joystickNumber%JoyX" and "%joystickNumber%JoyY". Depending on how your pedals' drivers map the toe brakes to axes, you may have to change the last "X" and "Y" to two of "Z", "R", "U" or "V".

Good point! I'd forgotten about those. At present I have the MFCDs on my left and right monitors with hawgtouch providing buttons. I'd have to use the mouse to manipulate those and other cockpit controls. UFC, CDU, etcetera. I think I could handle that.

I fly the P-51D, A-10C, the F-15C and the Su-27. I cannot think of a single control that I need the keyboard for; everything is on my TM Warhog. The only thing I need the mouse for is rolling the canopy shut on the mustang, and the ramp-start on the hog. For me the resolution is the only thing standing between the rift as-is and the ideal world. If the res is good enough to read the text on an MFD, I'll be happy. Having a better res to spot bogies would be good too, but I think I can manage.

I set up FTNOIR with a PS3 eye and generous lighting. I found it to be a reasonable solution to head tracking, but not as good as my wiimote-powered freetrack setup. There was more jitter and sluggishness. A good solution for someone on a budget in a hurry, but no more.

I made this video showing a 1v1 between an F-15C and an Su-27. It shows some basic fundamentals of BVR:

Someone's built FSX support for the rift already.

I made this video yesterday showing a sortie between myself in an F-15C and an expert AI Su-27. The first half is real-time in cockpit, the second half is an analysis in tacview. I thought it might be of interest to this community. For best results, watch in HD. Hope you enjoy it!

There's an area of space behind and below the tanker you must occupy before the boom operator will start hunting your port. Keep experimenting until you find it. Also make sure your refueling slipway is open, and the refueling status indicator to the right of your HUD indicates "Ready". If "Disconnected" is illuminated, tap your nosewheel steering button to reset. I'm assuming you've done the radio stuff correctly for the operator to even have lowered the boom, but it's possible you didn't go the last step to signal to the tanker that you're ready to take fuel. I don't remember the specific radio command, but it's the first option in the radio menu.

No I don't, I have a HOTAS setup. I don't touch the keyboard. No, the rift has a huge field of view; 90 degrees horizontal. I don't think you're right. When the only visual data your eyes are receiving is coming from the sim, you're entirely immersed. Coupled with proper depth perception, and high-Hz head tracking... there's nothing that can come close. Watch the videos on youtube of people freaking out, fearing for their physical bodies because they're so immersed in what they're seeing.

I think avoiding a legal ensnarement with NaturalPoint should be of the absolutely lowest priority. Nobody should capitulate to those plainly anti-competitive bullies. Bohemia Interactive (Operation Flashpoint, Armed Assault) have sacked up and thumbed their nose at NP by incorporating native TIR and freetrack interfaces into their games since ArmA 2.