ivanwfr

...class action complaints or street manifestation ?

True but there is a TARGET solution /way around for that one: SetSCurve(&Throttle, SCX, 0, 0, 0, curve, zoomIn[/zoomOut])

I don't like it either and I had to open mine to repair it after I suppose having knocked it a bit too hard - a bridge guard missing here? - and I don't like what I have seen inside! I'm sure that it could be the low resistance kind and sturdy at the same time. If anyone has any good replacement reference with the right dimensions, I could certainly replace it instead of asking TM!

Here is the thread I opened about my investigation: TARGET - Advanced programming. It's not an easy subject and if you look at it like you did the first time you saw the DCS A-10C Flight Manual, no worry, it simply requires the same frame of mind. Nobody here has been pushed into this sim, I think we're all looking for trouble to keep us busy with something immersive. Target and HOTAS are just means but when they do precisely what You - as in not someone else - programmed them to do, it takes a significant part towards feeling in control. Anyway, should there be any obstacle for anyone ready to get a bit dirty, I'll be pleased to help as it has become a real hobby. [edit] Another way to approach Target could be by simply requesting an original functionality. If someone can express any clear macro design, I'm pretty sure I could not help but looking for a solution. The only requirement would be to drop the Plug-and-play 2xUSB input for the Combined equivalent as a starting point.

Have just read Frostiken post about TM Warthog, potentiometer, hall sensors, maneuvering and curves. So, if this is all about quality, control and precision, something is missing here! It looks like we're talking about how to use the 5 gears of a Bugatti! I'm still obstinately - once more - talking about TARGET scripting, again and again. As well as there is something beyond Notepad in a PC, any axis curve can be dynamically adjusted by script real-time with a flip of any switch. Even the Slew pointing stick becomes quite usable with a scripted kind of precision-control. SetSCurve(&Throttle, SCX, 0, 0, 0, curve, zoomIn[/zoomOut]);. If we just plug this device in and use it as if it were a toy, we get what we deserve, just a very expensive toy. Plug and play they say! OK, just do that and switch to A-10C Easy mode to be consistent. If you rather chose to read the 600+ pages of the A10C manual, you should also consider investing some effort into the main instrument handling... +1 on my own campaign target board ;)

SpaceMonger

And you will have to tell her/him that she/he will have been a lovely patch off-topic subject even before she/he was born ;)

It does, and easily !

Yeah, but Boot/VMem on it is nice to have too! It starts/stops your w7-64 rig as a microwave ;)

If you are not ready to WORK the TARGET scripting feature, I agree with what has been said so far but if you are, I would go as far as saying you could unplug your keyboard (not really but close!). I'm one of the very few seriously digging into what TARGET has to offer. I would even say that I'm still waiting for someone to talk about it with. Instead, all I can read is that plug and play featured is lost as soon as you use it. If this is true with Logitech devices that have so crappy software/hardware quality ratio, TM Warthog HOTAS is the first device I ever had on my table with such a good combination. Sure, my point has something related to the fact that I deal with software for a living. But any well wired enough brain able to fly an A-10 meets the requirements. Just to stress one of the amazing possibilities, the layer modes give you 6 different bindings for each of the >50 switches... Even more, you can add your own modes with a little clever state programming (TEMPO feature has hidden potential)...

Thanks Seil, Now, I have a bookmark for a TrackIR knowledge base. And thanks Cayenne for these links that make a good addition for those like me who are still having a hard time to decide what needs to be done to adjust environment and user discipline with so many parameters to be taken care of. What I would appreciate most would be that this thread be kept about the most important bits of advice from those who have used this device for some time. Specific problems like those indicated by Cayenne would be welcome as well as long as they are links to their own thread rather than detailed discussions better focused separately. ;) But, please with some topic label to tell what the link is about

I really enjoyed reading your experience report as it sounds clear and clean. Facts are currently loosing precedence over random anonymous opinions or gossip consensus. I suggest you should make a copy of this post to the head of a dedicated thread where facts would be welcome and opinion be banished. It's not this hard to filter them out after all in these forums, dedicated/dumb ratio appears to be high above average. Thanks again from a new TIR user who likes the thing already but knows that time has to do its job to make these points tracking become natural.

You definitely can't afford two layers of foolishness... posing as a flying-couch warrior (the male genre) plus showing off as if you were a kind of walking wedding cake attracting a consumer (the other one). Hopefully, there are more of the first kind here (from whom I expect sarcasm awareness) than the other (from whom I would get some kind of deadly back surge next time I hit this thread ;)

I did not investigate but the one thing about Pro clip I dislike is this wire. With a hair band (or my Plantronics headphone) you can drop the audio headset when not required. Unless IR is modulated, wouldn't a simple battery do the trick? USB is there only for it's 5v red wire ...anyone?

You know I was joking.. don't you? In fact, I'm pretty sure that some lua solution could display a custom text overlay, like training sessions and communication menu do. I'm not (yet) tinkering with lua as I'm too busy with TARGET at the moment but I'll keep that in mind...

Maybe someone skilled enough could work on having one of the MFCD turned into an iPhone to get us on the Web while flying! This and a Google Doc and here you go!

Signed too by an owner of TrackIR 5 Pro!

You can also try a G700 programmable mouse button.

Hi deephouse, just as an example (wrong switch!) // 'P', 'LAlt' 'HOTAS Pinky Switch Forward' // 'P', 'LCtrl' 'HOTAS Pinky Switch Aft' MapKey( &Throttle , PSF , CHAIN( PULSE+ L_ALT+ 'P' , EXEC("GameOutput(&Throttle, OUT_ID_LED_BACKLIGHT, 1);") ) ); MapKey( &Throttle , PSB , CHAIN( PULSE+ L_CTL+ 'P' , EXEC("GameOutput(&Throttle, OUT_ID_LED_BACKLIGHT, 0);") ) ); You still have to bind a keyboard shortcut to [Lighting Panel] [Console Light Increase / Decrease] as they don't have any by default.

French Coolie version of the same story ;)

So I must be the lucky one with TARGET. I've never seen it crash and your nightmare looks like a dream to me... Just have a look at what Logitech or others give you in order to "customize" your input devices... It could be related to the fact that I've spent more effort that others in order to understand what happened when it did not behave as expected instead of giving up with a crappy word? But if flying with a keyboard is not 100% satisfying, could you tell more about how you didn't do it ?

I have to disagree until you show me a single input device scripting environment that compares to TARGET. I keep reading this kind of "opinion" about how to do things or how you can't do them using this software... That's amazing how one can read nearly anything and just the opposite in any single forum. It even looks like this works for about everything on the planet. BTW, my shift keys are S4, MS-Up and MS-down just because they are all temporary contacts, not part of the default mapping, activable at the same time as other switches like modifiers should be... and the pinky switch is the weakest mecanical switch on the Throttle (just listen and compare to Auto Pilot switch). My few cents about how to select a shift switch. Here is my own "opinion" in the form of lines of code and the documentation that goes with it. Just an experiment to witness how they will be transformed into vapor-ware thanks to this magic web-logic. PNP_ivanwfr_110522.zip DCS_Bindings_110521.zip And I did not loose anything of the plug and play default mapping, thanks to using TARGET, it's all 100% in there.

It looks like FC2, and DCS A-10C as well, do not listen to keyboard events. Instead, they sense each key state the same way they do for DX Input switches and in this case, AutoHotkey won't help... Now, you're looking for a real keyboard ;)

Yea, I was looking for technical details from MS ... wrong idea -- I mean technical is irrelevant here ;) -- at last, found a mistake I didn't do! Here is the -- not simple -- solution : http://www.autohotkey.com/

maybe useful info: Pause == Break