Teej

Not entirely accurate to call it "a legacy hornet with increased tanks..." etc. It's essentially a new airplane. Very little in common with the "legacy" hornet. 4' taller, 4' wider, 10,000 pounds heavier empty... And as to the radar...Where did you see provisions for the F-14 radar? I don't think the F-18 platform has any more capability to carry the F-14's radar system than my car does. It'd be irrelevant, too...the F-14's radar was built around attacking bomber formations with the Phoenix missile.

Uh...the F-20 never made it past prototype. They tried to sell it but nobody wanted to buy, foreign or domestic. I think that can be safely ruled out. Despite the sweet mudhen model, I see a lot of problems implementing something like that in a detail-sim.

People call that the friction control because on the real jet, that's the throttle friction adjustment.

Gotcha. Yeah. Well...I don't know if it helps get around your engine brake problem (because it doesn't give you any extra axes to play with) but there's a couple of things you could do... For things that are system toggles like that...your master arm for example...you could make it so that if you were holding S3 (or whatever you've defined as your "/I" control) it didn't send the master arm (or engine brake) command. That way if your switch got reversed, you could "reset" it. If you went with a script based target profile instead of GUI, there's a lot of extra logic you could add too. For example...I know it's unrealistic but I wrote an F4AF profile for the Warthog such that if you held both ENG OPER switches in the IGN position, and pressed the LGWRN button...it would run a ramp start macro.

Well, you could always map the slew switch onto keypresses and get 2 axes back that way. That said...I've not flown BS. What's the "switch syn" problem?

Yes. The TIR pro clip needs nothing but a 5v source with very low current requirements...only like 20ma or something. It gets this from USB but isn't "talking" to USB. I simply picked up a battery that has a USB plug on it intended to be used as a "spare gas can" for ipods/phones/etc. Something like this: http://www.amazon.com/Duracell-Instant-Charger-Compatible-Devices/dp/B0016Y9R6C

Generally I've been running game sounds through onboard sound, and voice comms through a headset (that has its own sound controller). This lets me change the relative volumes of each...or flat out mute the game sounds with a touch of the keyboard 'mute' switch... Flying formation, there's few things I find less useful than sound. :D

I picked up Metalnwood's extension kit. Very easy to rotate grip. :D

About what? You've said the same thing, over and over... As I keep trying to tell you, this is exactly 100% the way it is supposed to work. OLD (pre 18) firmware: Plug in throttle 5 LED come on until handshake, then 5 LED turn off and rest of stick turns off NEW (18+) firmware Plug in throttle. Get quick flash from 5 LEDs. Once throttle is recognized by windows, backlight LEDs come on. With 18/20 firmware, it will not behave the way it did before 18. It will not "remember" the LED settings from an actual power off (d/c computer from mains or unplug throttle from computer) - when you do this the above sequence (new firmware) will always occur. If you leave throttle plugged into a powered hub (or a motherboard that keeps power on the LED), then the throttle will "seem" to remember the last state because the throttle isn't actually getting reset like this. What's confusing?

No. Unless you turn them on yourself, the 5 will only come on very briefly (quick flash).

That's what I'm trying to say - that _is_ the way it works and there's no way to get it to do anything different.

A realistic campaign would be pretty boring in most cases...at least in Falcon. North Korea has ~ 35-40 MiG-29 and they're concentrated around pyongyang. How interesting would that really be in Falcon? Instead, in falcon (at least in ACE where most campaigns got flown online) they had ~ 150 or so, all in perfect working order with top notch pilots. ;)

Are you running firmware 18 or 20 in your throttle, and have you physically unplugged, paused, and replugged your throttle since installing TARGET 1.0?

Many motherboards still provide power to the USB ports even when they're "off" - that's why you can have a keyboard power-on. Thus, your throttle is never being "rebooted" even though your computer is. That's why I suggested you physically unplug the throttle, wait 5 seconds, and plug it back in and see what happens.

Well...you could always not reboot. :) (seriously, I only reboot every month or two.) I use S3 sleep when I'm not using the computer so power use is nil...but it doesn't reboot the throttle so the lights stay however I had 'em set. In fact, my script stays "running" in S3 sleep so when I come back to it I'm all set to fly....all, of course, assuming the throttle is plugged into a powered hub.

The behavior is entirely determined by firmware, not target or anything else you can do.

I suspect bumfire has his throttle plugged into a port that remains powered on even when the computer is rebooted. Try physically unplugging your throttle, wait 5 sec, then plug it back in. I'm guessing you'll get the main panel at full brightness with the 5 at the top "off".

When you plug in the throttle, the 5 LEDs will turn on until the device does its USB handshaking, then they turn off. (With latest firmware - earlier firmware they stayed on). The main body LEDs are off until handshaking is completed, then they turn on. When you use TARGET to change the on/off/brightness states, that only remains until the throttle loses power (ie power off reboot or unplug / replug). There is no (to the best of my knowledge) way to "save" the LED configuration on the throttle or adjust the brightness without using TARGET (unlike the MFD panels which will let you tweak the brightness using the buttons)

DCS is set up to run without TARGET. It has predefined mappings for the "hotas warthog joystick" and "hotas warthog throttle". When you execute a TARGET configuration, as you've noticed, those two devices get replaced by the combined controller, for which DCS has no default setup. No need to uninstall target...nothing's broken...just if you want the standard DCS mappings, you need to halt the TARGET profile. There's no easy way to do 1-2 things in TARGET and leave the rest of the stock functions in place.

That's the way they behave in recent firmware. With launch firmware, the 5 would stay on all the time.

No, but to an airline pilot at 12,000 feet back in those days....seeing a glint of sun off something 50,000 feet higher would look pretty strange indeed.

"I'm looking for the nuclear wessels. Nu cle ar.....Wessels...."

I doubt there was any (intentional) change in the units between yours and mine. Seems the first couple thousand at least were on the market on day 1. Entirely possible I had mine before you had yours. As to Hondo...I don't think there's much you can do to influence whether your Warthog has issues out of the box. I think it's probably a good idea to run later firmware, but I don't have any info on changes that were made. Just seems I haven't seen (m)any crashed units with 18 or 20 firmware in the throttle. Programming isn't that tough. There's a GUI to do most things that most people will want to do, easier than it was for the Cougar back in the day. When your needs get more advanced, the script engine is extremely capable. Hard to offer 'tips' though until you decide what you want to do.

Without a dynamic campaign engine to rival F4AF...it's just a game.

Heh. Falcon 4.0 still isn't finished. Why would A-10C be? :D