Zenra

+ another 1

There is no ILS mode on the HUD, but the instruments are laid out nicely for instrument approaches. Just adjust your view so you see the HUD with the velocity vector readable and so you also see the ADI and at least the top of the HSI. Fly the needles, cross-checking airspeed and heading at intervals and adjusting power and pitch as needed. Once you have the plane settled with the velocity vector at about -3 degrees on the pitch ladder (and centered on your touchdown point, once the runway becomes visible) make only fine adjustments. You'll land like a pro every time.

Me too! Great work, Ghost - thanks for all the effort. This is going to really boost my enjoyment, and success, with this sim.

I'm trying to get mine to start showing signs of wear. That way my wife may not realize it's not my old Cougar throttle until it looks "old" enough to have been around a while... @Mule: Congrats on the purchase - you won't regret it!

it's easy to check whether you have wind (i.e, the mission brief was wrong). Several CDU pages, such as the STRINFO page, will display the actual wind calculated by the EGI system.

It will align, but it takes time, just like after initial power-up. Once fully aligned you need to select NAV as the source, again just like from a cold start. Your screen shots certainly do look like some kind of INS alignment issue...

Does the ALL ORIG DATA (L3) option on the CDU SYSTEM / DTS page NOT do the same thing? I can't try it right now, so am mostly just curious...

Easiest I think is to use the SYSTEM / DTS Upload sub-page from the CDU (or using the UFC with the CDU displayed in one of the MFCDs, as Mower suggests). From that page select ALL ORIG DATA (L3).

Here we go again... Gotta agree, though, that's quite a piece of detective work :book:

Thanks, guys, I'll try some more (must not be holding my tounge right or something...)

Does anybody know if the Standby Attitude Indicator can be re-caged? The tool-tip that appears when you mouse over its knob suggests that you can by doing a simultaneous mouse click and scroll wheel, but I cannot get it to work. The manual says the SAI is caged by "pulling" the knob, but I cannot find a way to do so. I know the SAI is basically useless now since it becomes hopelessly out of alignment after just a few minutes of even mild manouvering, but wondered if caging and uncaging might help (as it should IRL).

The arrow indicates the Total Velocity Vector display has reached the limit of the HUD view. From page 361 of the (English) manual:

This is my bet - icing is usually the problem behind IAS and VVI issues, and most often occurs when ascending or descending through fog or cloud.

Furia set up a nice mission template that you can download here in which he's set up a database of mission waypoints corresponding with many of the NAVAIDS in the area of operations covered by DCS A-10C. I do not have time to put together a mission right now, but with a couple of SID, STAR, APPROACH and ILS plates it wouldn't to too difficult to set up a flight like the one in Red Dog's venerable instrument tutorial for Falcon.

Believe me - I still feel like a blind man in a dark ally with most of this. I am just thankful for all the people who aren't afraid to ask the questions, and of course for the many who take so much time to post authoritative and detailed answers. I am tempted to start listing names, but afraid I'd miss more that one, so let me just offer a big thanks to you all - this community is fantastic and what makes it possible to come to grips will all this sim has to offer. Edit: seriously, WarriorX, I appreciated it, but what I really appreciate are the guides and explanations you have offered in so many threads here - I have learned so much from members such as yourself, and as I said, it is that kind of involvement that makes these forums great.

The coordinates are the same. The first set, from the CDU, is given in Degrees and decimal Minutes. The second is in Degrees, Minutes and Seconds.

Very nice - thanks muchly for all your work on this:thumbup:

Each campaign mission is a separate entity, so the kind of persistance you asked about is not there (like it was in Falcon, for example). The campaign designer sets the linkage between missions and determine criteria needed to progress. Using the campaign and mission editors it is possible to set up branching campaigns that would not require you to replay a given mission until achieving some level of success. There are a lot of good missions being posted by the very creative members here but I haven't seen anybody make good use of the new campaign editor yet. I've only played around with either of the editors so far, but they appear very capable and a step up from their equivalents in Black Shark.

You can also convert mark points to waypoints and give them a name in addition to their assigned number. That way you can use the CDU to search for (e.g., Shilka, ZSU,...) and call them up later rather than keeping a separate list. Real A-10 pilots often write coordinates and other notes on the inside surface of the canopy with a grease pencil...

Unfortunately I have not found any particularly good deals on the TM Warthog - I think I ended up paying around US$475.00 for mine through Amazon. In addition to the manual there are a number of other documents you will probably want to read, most of which can be found through the sticky manuals and documents thread on this forum. I use an iPad to read the manual and other documentation, and I recommend the approach if you have access to nearly any e-reader (e.g., Kindle, Nook, iPad, etc.). Many people get the PDF manual printed through Kinkos or a similar print shop. You can save some cost, size and weight by having things printed in a "booklet" format, which is double-sided, half-size, so you get four pages printed on each 8-1/2 x 11 sheet.

Another thing you might want to check is to ensure you do not have an axis mis-assigned to the rudder. Getting the rudder off to one side by very much without coordinated aileron input will cause one wing to drop precipitously, leading to a spin.

No speed indication could mean icing on the pitot tube. Did you have icing conditions, and if so did you turn on Pitot Heat?

I've been using WarriorX's cold start checklist (see here). I don't think there is anything missing(?).

This would indeed be cool; reminds me of all the discussion over laser burnout in DCS Black Shark. I do not know what the real behavior is, though. Does anybody have a reference to authoritative info on how long the Mav can be powered up before bad things start to happen? It is cool that ED models the timeout, so it seems that adding realistic failures if you choose to ignore such warnings would be straightforward, but what might constitute such "realistic" failures? EDIT: Geskes' post appeared as I posted mine - thanks for that info - I had not tried / noticed that before. Nice to know the detailed realism continues!

See this thread also...