Jump to content

tjhowse

Members
  • Posts

    97
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. This very thread: http://forums.eagle.ru/showthread.php?p=1699631#post1699631
  2. 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?
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. I'm afraid not without significant effort. Unfortunately joystick buttons cannot be chorded in AHK. Workarounds are possible, but inelegant.
  9. 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
  10. 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:
  11. 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?
  12. 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]
  13. 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.
  14. 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.
×
×
  • Create New...