bartleby

Try using the left throttle button (I think the default binding is Q) to engage autopilot and see if that works.

If it has a global profile applied and you've set it up to use keystrokes, that'll happen.

You can also make a waypoint using the offset page of the CDU (OSET) and choose the bullseye as your initial point. Check out page 246 in the manual. Edit: too slow.

As everyone's said, practice is the key. I've found the Georgian Cross campaign to be pretty good for this: set infinite ammo, call up JTAC and start practicing your Maverick flow. It also might be a good idea to think of things in terms of tasks. Don't just try to memorize every key, ask yourself "what is required to acquire and engage a target with this system? what are the steps to receive and prosecute a target designated by a JTAC?" Once you've got a foundation, everything else will make a lot more sense and you'll find yourself using the tools intuitively.

Are you using the pinky switch? Aft = settings via the panels Middle = all external lights off Forward = default external lights

There is a separate anti-collision light switch on the lighting control panel. Top right switch. Here's what I've seen recommended: At start until take-off: Position FLASH, anti-collision OFF On runway: Position STEADY, anti-collision ON Then off at fence in, of course.

You should be able to. With Mav as SOI, hit TMS up long, then china hat forward long to slave al to the SPI. I'd recommend working the other way around, though. The TGP's resolution is way higher than a mav's.

It's a .psd file, so you'd open it with photoshop or gimp or something similar.

Are you sure you're pressing TMS up short after you slew onto a target? IIRC, if you order "slave all to SPI" the maverick doesn't lock. You have to tell it to first. It could just be that you're too far for the seeker head to see. Their resolution is a lot less than your TGP's.

There aren't separate controls to start the engines. Moving them from off to idle (L Alt + Home for left, L Ctrl + Home for right) starts them.

I don't think you can just enter a name and have it show up (good idea, though). There are skin templates that you can edit here: http://www.digitalcombatsimulator.com/en/downloads/misc/a-10c_model_templates/ Then you can select your custom skin in-game.

Lack of parking break or chocks can be annoying. Someone posted a good idea on here: set "wheel breaks" to an unused axis on your stick (you've got one, right? :music_whistling:) and use that for ad hoc chocks.

Pretty much. The only thing I can see that might not be necessary is step 4. I don't think you need to change SOI before slaving all. That might have changed in the new patch? One issue - china hat aft long slaves the TGP to the steerpoint, not mavericks. If the TGP is SOI and the mav is slaved to SOI, that would work. Or you can hit TMS aft long to set steerpoint as SPI, then use china hat forward to slave the mav. That way you can step through your points on the hud and the mavs should slew to them.

Ah, you must have forgotten to safe the self-destruction device during startup. Better study the manual some more.

Yeah, the four digits in the altimeter are the altimeter setting. The setting the ATC gives you is currently broken, but that is how you set the altimeter. There are a couple different ways to set it. There's QFE (field elevation), which is what the ATC will give you. This is basically setting the altimeter to 0 on the runway There's QNH, which is elevation above sea level of the runway. This is setting your altimeter to the runway's elevation (above sea level) QNE is a standard elevation - "pressure elevation" - 29.92. This won't necessarily give you an exact reference to the ground, but it's useful when you're trying to maintain separation from other aircraft or other such things. Wikipedia has some more on the subject.

The errors come up in the game after applying the patch or during install? You could try checking the MD5 of the downloaded patch. http://download.cnet.com/MD5-Checker/3000-2092_4-10410639.html

One issue with masking constraints is that in reality they can be changed for different loadouts. In the sim they can't, so I don't know if it just applies one that might be overly constraining or it automatically calculates masking. Yup, that's it. Or, you could follow my style and flop the plane around while mashing TMS fwd until you're unmasked, but I doubt that's the best practice.

It isn't! The TAD and CDU stuff seems really daunting, and the organization of the manual doesn't really help, but it's not that hard at all.

Page 319 of manual Assuming you've already set your SPI with some sensor: Set TAD as SOI Slew cursor over wingman's plane TMS short forward to actively hook it. You'll know you've done this as the HUD changes to show a pair of dashed lines to the hooked ship. One of the right side OSBs will say send and display the plane's net ID. Press send to give the tasking. You do not need to be broadcasting your SPI

There's a dial at the bottom left of the altimeter. Mouse over it and scroll up/down to change the pressure setting.

I was lucky enough to not have too many problems before, but definitely enjoying the datalink stuff. I've noticed that alt-tabbing seems to be a lot slower after patching, though - related to the texture loading, maybe?

Remember to turn down the symbology brightness, too. I was missing that for a little while and it was annoying.

Also, are you making use of the alt-hold autopilot to set up orbits? That way you can contact a JTAC and set up an engagement without focusing on flying the plane.

Hi. I have a Logitech G940. It's in great shape, works fine and plays well. I think I have the original software around somewhere, but the box is gone. I've got the change bug, though. I'm sure you know how that is. I've been eying the Warthog...seems to be an excellent piece of equipment. Would anyone be interested in trading a G940 for a Warthog? Obviously the prices are a tad different, so I'd make up the difference with some amount of money. Alternatively, I guess I'd be interested in buying a Warthog and/or selling a G940 separately. Thanks.