bartleby

If you look at his hud, the active waypoint is 0 - init position. So he's just set his waypoint to where he started. That might not be advised if 0 is set on the ramp, though. The dashed box around the steerpoint box indicates that he's hooked that point in his TAD. Importantly, though, he's not flying with the hud. ILS bars don't come up there. He's using the steering bars on his attitude indicator. Try this if you want: using the CDU or UFC and repeater, go to NAV then click DIVERT. A list of the 5? closest airfields will come up. Select whichever you want (note: I don't think you can select further ones. So make sure you're within range if you want to do this). Your steerpoint will be set to the runway and some airfield information will appear in your CDU. If there's an ILS system, it'll give you the frequency. Then set it, unstow the steering bars, and fly the glideslope. As for the course, there's been some discussion of incorrect headings on here. I think it comes down to an issue with magnetic variations, but suffice to say, some headings are off by up to 6 degrees. Someone on here made a great set of airfield diagrams, try downloading those. They should have correct headings on them.

The chief yelling is a bug. Even if you turn off ground power and everything, he'll yell at you as you start to taxi. Don't know if it'll make the coming patch, but it's known anyway. It certainly shouldn't prevent you getting clearance. ATC bugginess is unrelated, as far as I can tell.

Make sure you run the script first and then map the axes within FC2. Target can't map them. Sounds like one of the throttles is mapped to your rudder.

Any chance you could wrangle firmer details out of ED? It'd be nice to be able to plan patterns and effects and whatnot instead of just flying on hope.

I have the same thing, LostOblivion. Just got my Warthog about a week or two ago. Mine came with the housing plate attached. Using the device analyzer, it appears to be a give from 0 to about -100 only in the x-axis. No play in the y-axis. Keep us updated on what feedback you get, please!

Yeah. The manual isn't organized well for learning. Better used a reference for someone who's already got a basic idea of what's going on. I've started trying to annotate the CDU a bit on the DCS wiki: http://www.dcswiki.com/index.php?title=Category:CDU_pages_(A-10) In my experience, the most common uses of the CDU are: Viewing waypoint information Adding waypoints based on JTAC data or whatever Using DIVERT to get airfield info Using OSET to create waypoints based on offset data If you know how to do those four things, you'll probably be fine in 95% of situations. I'd recommend focusing on those tasks. Once you have a good handle on them, the rest of the CDU will make a lot more sense.

Try multiplayer. Hop in an open server and start asking questions - you'd be surprised (or not) how helpful people are. Also check out some of the youtube videos people have made. There are lots of them for most aspects of flying and fighting the plane. I hope this thread doesn't get crapped on, because I'd rather have another more potential pilot instead of a disappointed gamer.

The plane goes up on jacks (in multiplayer you'll get a "Playerxxx has taken off from airfield" notice) and the panels open. You'll certainly know when it's happening.

SAS engaged? Radar alt in norm? Try downloading one of the startup checklists (I recommend paulrkiii's or WarriorX's) and following them. If you still can't get EAC engaged, then there's some kind of bug.

There is no engine start command, per se. The engines start when the APU is on and the throttle is moved from off to idle. By default, I believe the bindings are R Alt + Home for the left engine and R Ctrl + Home for the right one. And yes, make sure your throttles are all the way off before trying to move them to idle - they won't move otherwise. You might even need to recalibrate them or add a little deadzone at the end to make sure they get all the way to zero.

There were a couple good threads and some discussion on here recently about how to use the OSET page to generate offset waypoints. WarriorX made a good tutorial here, too: http://forums.eagle.ru/showthread.php?t=72101 The only thing is you'd need to make sure the waypoint was centered right on the runway, otherwise you might end up with a calculated threshold that's in the grass. Which might not be good for your aircraft.

Check out lobo's post above. Use the right rotary to set the CDU to Position. Then it'll display OAT.

Good work. I was just thinking about trying to figure this out. I was going to manually create a glideslope intercept waypoint using offset, but this is way better. Had no idea about VANGLE setting. Going to give this a try in a bit. Are the DIVERT waypoints centered on the runway? If they are, ought to be easy to use offset to make a threshold waypoint to use with this method. A little fiddly, but might make for an easier landing.

Is there a minimum alignment required for NAV engagement?

Pretty sure it's a stock thing and doesn't need to be added specially. That is odd, though. Are you on easy comms? Sure you're pressing the correct VHF mic switch?

You can just enter the UTM coords he gives you as a new waypoint. He'll give you remarks on nearby air defenses, usually, in the form of an offset from the target point. I usually just try to remember those, since they're usually close enough to consider right at the target, but you could do those if you wanted.

Tthe TGP has a way higher resolution and zoom. You'll always want to use that instead of the seeker head if you can.

I rarely directly slew mavs onto targets. Maybe I'll use the tracking gates in the HUD if it's an emergency, but as you noted it's difficult. Try using the TGP to lock up a target, setting as SPI with TMS fwd long, then slaving the mav to it with china fwd long.

For anyone wondering how to do that: http://www.dcswiki.com/index.php?title=Display_program_MFCD_page_(A-10)

Yep. Whenever your flight conditions change, you re-trim. Function keys. F1, F2, and so on. There's only one autopilot, but three different modes. 2, 3 and 4 select between them. 2 is path hold, which will attempt to maintain your patch as shown by the velocity vector on the HUD. 3 is altitude/heading, which tries to maintain your altitude and current heading. 4 is altitude, which will maintain an altitude given an arbitrary bank. It's used mainly to set up orbits so you can put your eyes on the instruments inside. There are also restrictions on when you can enter the modes, and you should be reasonably trimmed before engaging AP anyway.

Devil's Cross? Yeah, I've had tons of failures in that campaign. CADC, MFCDs dropping, lost the HUD a few times, gear problems...seems like Matt may have bumped up the failure rate in that one. Actually sort of fun.

You are correct that the data transmitted isn't a waypoint, but you needn't make it one in order to use it. On the TAD, hook the red triangle by slewing over it and TMS forward long. That will set it as your SPI. You can then slave your TGP to it with china hat forward long (IIRC). It will also appear in your HUD as a dashed box, I believe.

That is very strange, then. So, to make sure I have it right, the joy hat switch works normally with the modifier but without it acts as the pitch and roll axis? Hm. I don't actually use his profile, so a few general thoughts: Maybe it's trim? Make sure they're not assigned to the same key Try setting the A-10 profile to global in the Logitech profiler Are you using the throttle mode switch? Maybe you have a different assignment between them Try changing the TMS keystrokes and reassigning them Try resetting your joysticks as I posted above and redoing the profile Check axis assignments in-game and make sure there's only one assignment for pitch and roll Are there keystrokes for pitch and roll? Can't remember, but check and make sure those aren't what you're using Maybe post a quick track showing the issue, too, and we can see what's going on.

Currently you can't in single player. It will be added in the next patch. In multiplayer, hit escape.

Ah. That's strange, then. Make sure the key-binding is right in-game?