Seil

I'm pretty sure I can round up some guys from our squadron depending on when the events are scheduled. Does this mean 2-4 pilots or events or squadrons or ??? Please elaborate.

http://www.youtube.com/watch?v=jmHTKj0gpaU

Woo hoo to everything on that list! I can't believe how many people are complaining..... Progress is progress. We all want everything to be finished yesterday, patience my friends ;)

Negative Ghost Rider! I used to use this with my old G940 on the two stage trigger. Should support DirectX access out of the box.

Free as in beer and independent of specific devices would be AutoHotkey http://www.autohotkey.com/

That ^^^^ and don't try to move your stick, more like squeeze your hand muscles. Talking about SMALL corrections! As said before, practice, it'll happen before you know it. Just keep at it.

I'm guessing you're taking fire when you're attempting to employ guns? Guns are best employed from a slant dive (30-40 degrees) try starting from approx 5000 ft altitude. Keep an eye on your range indicator under the pipper- You should be firing (on average) between 1.2 and 0.5 miles from the target. Tanks will require you to be closer, in the 0.8 to 0.5 range. APCs and trucks you can engage from the 1.5 to 0.8 mile range. DO NOT fly over the top of your targets. You should stand to survive a bit better. ;) Typically return fire starts when you're around the 0.8 mile mark (depending on the unit) If you're trying to use guns against a Shilka or ZSU23, stay further away, I wouldn't even attempt to get as close as 1 mile. Of course if you're good enough with the guns, you can bend/break some of the above tips to your needs ;) Good Luck!

The way I did it though PeterP, doesn't use snapviews.... Not saying either way is "right" or "wrong"... I just never use snapviews. Thanks for adding this though!

Exact file location is: C:\Users\__USERNAME__\Saved Games\DCS\Config\View\Server.lua It has been awhile since I modded mine, so if it doesn't exist you might have to go into the same path under the DCS install folder (Config\View\Server.lua) and copy that file to the Saved Games folder. I just edited the Eyepoint and limits_6DOF arrays to find something comfortable for myself. It can be a pain in the ass as you have to tweak the config, load DCS, instant action, note the effect, quit DCS repeat until you're happy.

L.E.G.I.T. Thanks!

Agreed. And technically, the Warthog's HOTAS are composed of an F16 stick and F15 throttles. (the throttle controls are slightly different, but close enough) Also, there is the possibility of other sticks to come that will attach to the Warthog's gimbal....

I'm not in front of my sim rig right now, but the file you need to edit is located in your "My Games" (My Docs) folder under DCS, view\server.lua I'll double check and report back once I get home tonight... give me another.... 5-6 hours ;)

Heh, I had no intentions of pushing you into debt. But glad you enjoy your HOTAS! Interesting.... I've seen others complain about it, but I've never had any issues or complaints about the microstick.... I wish it was the full sized authentic control, but obviously for cost reasons it isn't. That being said, it IS a hall effect input and it seems responsive, smooth and very controllable. A10's don't have after burners.... I know there are plenty of other aircraft to fly but it IS the "Warthog" HOTAS......... Also never had any issues or complaints about the software, device representation or programming custom profiles.... If you just plug them in, and load up DCS (to fly the A10C), there's litterally NOTHING to change or do; everything works perfectly as intended. If you want to get crazy and customize some things, you have all the power in the world to change every aspect - at the cost of a slightly more complex programming method / understanding. Lastly, none of this is relevant to the OP's topic :p

I think you're nuts man. You need to fly with it. More than 2 hours. You keep saying "desktop" but the TM Warthogs are replica simulation controls, not a cheesy desktop joystick. I'm also not sure which buttons could be "too stiff" - The only ones I can think of are the auto pilot and LG Warn Silence - WHICH you don't want to accidentally turn off with an easy-to-press button. Also, if you're flying *ANY* aircraft with dual engines, do NOT lock the throttles together on the warthog. Fly with them unlocked - always. It will be sort of weird at the very beginning, but you'll thank me later.

The head position is different once TiR is enabled. I ended up modifying it in the config files so as to have the correct HUD view by default. One thing to know: Zoom in/out controls are independent of TiR, you can move your head closer / further away from the HUD with TiR, but the FOV changes with zoom in/out. If you haven't played with that yet, might give it a shot. There's a checkbox that needs to be undone in the TiR software for the hotkeys called "Trap". If you uncheck that box, then your hotkey will both re-center your virtual head position as well as allow the simulator to see the key press. If "Trap" is on, only TiR will get the key press.

YES!!! I've actually been looking for it for awhile now..... There was issues going on this weekend and I was trying to figure out what was going on in the thread and I haven't been able to find it....

Right I understand that, and I use overlays for my MFDs... but I'm saying it's kind of moot to have the display overlay on my screen and then look at another screen just for the benefit of touch input.... especially at that price -Seil

Sorry man, especially since there is the limitation of requiring the outputs to be repeated on your display, definitely not worth the asking price. I already have TM MFD controllers and wanted this for the CDU, but I'll pass. -Seil

You mean like waking up in the morning and being tired of the same old weather patterns outside your window? .......

Depends on what aircraft you want to fly, and what you want set on your hotas. That being said, if you walk through the wizard on the Target GUI for a new profile, you can point and click program everything on the controllers.

You can do this, you just have to write a Target program for it. In the Target scripting manual, there's a couple examples for building a profile for FC that allows you to send an output when the switch is in the middle position.... This profile wouldn't be compatible with the A10C though, you'd have to switch profiles when you switch aircraft.

Should use the forum's search function, answered 1000 times - Use the Target GUI and there are point and click controls to manually override the lights. The manual is where I find all my answers :D

Thankya 8) I'll drop the source if you want, I'm just trying to finish designing the light state logic for alarms and such right now..... dunno, maybe I otta make a full out thread for this profile :music_whistling: but, I'm setting cms push as a two state (long /short) where short is normal in-game with just a standard dx binding and the long is PTT ;) ...... c'mon you know you like that! Used to be only a push for me on the G940 as PTT... best of both worlds :D Mic SW UP / Push are also un-used in the real bird (at least according to the spec we have) so those are also setup as aux PTT commands Paddle is shift... although there's only TiR center bound as shift + master mode on the stick for easy access (I'm smoking like a chimney out the window to the side) ...and some overrides for backlight intensities that are using the shift + MFD rockers Also, shift + ???? unknown button, thinking about using left throttle button will trigger an internal hotas startup calibration mode - basically using the 5 LEDs to designate any controls that are not returned to starting position for quickly resetting the hotas for a new flight (saves a lot of time when you're drunk) any other ideas are welcome, I'm trying to keep the base controls STOCK and have minimal management controls on the shift states - HUGE improvement over having to SHIFT + EVERYTHING to a couple limited D-Pads on lesser sticks. :p (referring to a couple from a particular brand in specific)..... (also have TiR so trim is accessed without a shift like the real bird)... planning to test TM trim vs sim trim, any comments? LED feedback via export conditions are represented via on/off as well as blinking states w/ variable patterns and rates.... I'm really not getting too carried away here, I currently have the 4 light boxes under the extinguisher handles (gun ready, nosewheel, marker beacon, canopy lock) as on/off with the four MFD LEDs... and then blinking patterns for GCAS, Engine failures, master caution... ???? Trying to capture the "head's up" spirit with those LED's (not having dedicated replicas of everything in the pit) I have on the fly intensity adjustment capabilities for the backlights (I like to have some light on my real controls without them on in the simulator's cockpit) although I thought it'd be cool to have it synchronized. And on/off MFD and Throttle back lights when power is supplied to your systems :D Hopefully I'll get some time this week to wrap this and that other project up ;) Anyways.... sleep is needed.

Congrats Ebs! Welcome to the party! I haven't applied my program yet, I have one in the works as well (almost done). Plan to keep everything stock save for PTT and running my backlighting and LED control from export data ;) -Seil

Never did get to mess with this over the weekend, was too busy with other projects... I'll attempt to hack this up later tonight after I get home - No promises, I'm guessing I'll find out it's not doable, but's worth a shot just in case ;) I have both TiR 4 and 5, I could theoretically whip something up, but I'm suspecting this is going to fall into the category of "beyond the point of diminishing return".... In other words, hacking up the axis signals from TiR 4 may take more work than it's worth.... I'll post back with definitive findings after some tests. -Side note: If ED has enabled the encryption flag in the SDK, they can force TiR 4 to run encrypted, as I said above, 4 supports the encrypted communication, it just doesn't require it to work. In this case it wouldn't matter which version you had :(