Harzach

Ah, different control set in CA. Have yet to purchase, so I'll refrain from commenting on it any further!

You'll find NVG gain in the "Sensors" section of the controls menu. Default keybinds are: Toggle Goggles: H + RShift Goggles Gain Up: H + RShift + RCtrl Googles Gain Down: H + RShift + RAlt

You can change it on the CDU Waypoint page, the same way you enter the coords. Enter "37T" on the UFC/CDU and select OBS17 on the right MFCD. *edit* - sniped. As for the error message, just clear the scratch pad before entering your data.

Of course, it all boils down to the situation - threats in the area, weather, whatever. Don't take anything I say as gospel! And if you can put enough energy into the LGB on release (that is, drop at high airspeed), you should theoretically be able to overcome that long-lase problem. There is certainly enough anecdotal evidence to support that in this forum.

That is what auto lase does. A 10-second lase time means "turn laser on 10 seconds before estimated impact," not "turn laser on for 10 seconds on release." The problem with long lase times is that rather than optimizing its ballistic trajectory, the LGB guides straight to the target: Dumping that much energy right after release can often mean not having enough left to get to the target.

Looks like you released far too low - @4430 and 10 degrees nose down - so the bomb falls well short of the target because it doesn't have enough fall time to get there. Time of fall was just over ten seconds, in fact. What's the correct way? Everyone will probably give a different answer, and a lot of them will probably be right. I prefer to drop LGBs from 12K+ and no more than 5 degrees nose down. An 8-10 second lase time is enough to get on target from that altitude. You really don't want to get above 12-15 seconds, though, or you'll increase your chances of missing due to loss of energy (but that's a different topic.)

A bullseye call? Yes. If you slew to that point, you won't necessarily see the bad guy right there, but he should be reasonably close. But bullseye calls are not really intended to be used this way, I think. They are more like situational awareness cues. "There's bad stuff here, here, and here. Watch out."

Same here, head tracking plays back as expected. Don't recall ever seeing an option to disable this (not that I've ever looked for one) - is there a checkbox or something somewhere?

Get up in the air and kick the rudder around for a while. Get used to how pedal input relates to yaw. When you are on the ground, the relationship is the same - visualize ground steering as being a result of rudder deflection, not nose gear orientation. Good luck!

Ouch, yes. Why render 4:3 to a 16:9 display, Sceptre? Or do you like 'em short and stocky? :D

I'm guessing you've never played any Mechwarrior games? :joystick:

Good point, shagrat!

Perhaps a second programmable keyboard, like something by RAZER or the like? I use a pair of Genovation Controlpads for UFC/CDU and a few other functions, which are a little expensive, but you could get a single full-sized programmable keyboard for $70US or less.

Options > Misc > Synchronize cockpit controls with HOTAS controls at mission start

Agreed - as gear monkey mentioned, the sound design is pretty bad, and the whole thing feels kind of hacked together and dated. Which it may be - no idea when this was actually made.

It's been on Youtube for a while, it seems. Full program (low res): http://www.youtube.com/watch?v=ZjW4FYHhYm8

SAM Triangulation

Could you post your computer specs? Also, Activation and Installation Problems is a better forum for issues like this.

Check out Stuka's templates: http://forums.eagle.ru/showthread.php?t=82161

Sorry, Panzertard. Just refreshed and saw your post. I'll stay on-topic from now on.

You said bananas were more radioactive and I called you on it. http://www.iaea.org/newscenter/features/du/du_qaa.shtml#q3 DU is 14.8 Bq/mg compared to a banana's 0.00013 Bq/mg, making DU only 113,846 times more radioactive. So, yes - the IAEA does not agree with your assertion. This was my sole point, beyond which I was implying nothing.

Not sure where you got that information, but the IAEA disagrees. Regarding the relative dangers of DU, however, the general consensus does seem to be that the chemical effects are of an enormously greater concern.

Odd, I have no problem mapping the TMWH to Teamspeak3 directly.

It feels as though the ~35 years I've been gaming have been building to a point that is getting so close I can taste it. The final step will be the complete merging of the vehicle sim and infantry sim worlds. Very exciting!

Getting close, Depth: http://www.engadget.com/2012/05/25/leap-motion-gesture-control-technology-hands-on/ And no gloves necessary!