636_Castle

Seems like everyone is on the same page here then. Russian ATC normally gives pressure reports in QFE, all four numbers, millibars. It would only make sense that since the A-10's altimeter doesn't have a millibar window, the ATC is being kind enough to give us western USAF FOB pilots the QFE in inches, which you'd probably request IRL anyway. Now the question is, why isn't the report given in the standard ICAO format in DCS? I don't think anybody knows for sure. :P:pilotfly:

I swear I can't get a report other than 29 or 30 when changing the QFE in the mission editor. That sounds interesting though. I decided to listen to some Russian ATC too, just to get an example of what they report. At 2:47, "QFE 1034" mb I'm guessing. So there must be a trick to ED's ATC, like the low/high pressure assumption you mentioned. Don't know.

Oh I didn't mean to. We're just talking about a lot of different countries here, and I wanted to be loud, lol. It's especially funny, living in the United States I too can see why there's confusion going on. Controllers in America give out QNH as "altimeter 29.92". That tends to drive home a point of "your altimeter should be calibrated this way", which is unfortunate. It varies by country and operation. :) Still though, as mentioned, QFE isn't being reported the way I understand it. Currently in DCS you hear 29, or 30, which are the first two numbers, but we're not getting the rest.

That's what I'm talking about, in that last video. Certain maneuvers have safety parameters that need to be met in order to ensure the safety of the pilot. For example, the advised apex for a half cuban 8 in the A-10 is 3,000 feet AGL. However, you have no AGL reading at extreme attitudes from your radar altimeter. Also, quoted below is from AFI11-246 And, you guys are missing the point that QFE (zero'd altimeter) is the standard way of altimeter calibration in Russia. And, seeing as how there's no other theater available to fly in, zero-ing out should be SOP for every DCS pilot.

I guess I can't Google videos for you guys to show you all, because I'm getting this from witnessed accounts. Obviously it's not a matter of turning away when it's a directly going to impact you, or if it's flying straight at you below the horizon. But if you're alert, looking ahead, and spot a goose or seagull on the horizon, you might only have between a half second, to a full second to react, yet still, a quick snap roll can save you, or position the airframe between the bird and the engines, so you don't lose one, or *it*. Just like you can jink out speeding bullets in the form of tracers. HUD cameras don't do the human eye justice, so no point in comparing those anyway. I'll just live with it I suppose. Maybe start a DCS:NTSB to find out the cause of certain power failures. ;)

It's not. Maybe I came off wrong. :P I shouldn't have said SOP. There are situations, such as IMC, where a QFE setting wouldn't give you appropriate obstacle clearance info. Or, if traveling above transition level, in which case you need to set QNE, no matter where in the world you are. Or when SLP is going to be changing frequently, during long distance flights. But in VFR conditions when you aren't going to be going through transition level, I personally have been advised to stick to QFE when possible, in the United States. :) Not the case for DCS's AO though. QFE is the norm all the way up to transition altitude.

It isn't mandated, but it's common practice and should be used when possible, especially when operating in close proximity to the aerodrome. It's a safety precaution, because exact field elevation isn't always known, and TDZE isn't always taken into consideration. See accident, occurred due to forgetting to set the QFE, and, "objects being closer than they appeared." ;) It's vital for aerobatics as seen in that Thunderbird's clip. You lose your radar altimeter during inverted flight, and pulling 6 Gs while flying upside-down isn't the best time to start doing math. :P In eastern Europe and Russia, especially in the Royal Navy/RAF, QFE is a common setting used.

QFE = A setting used to determine your altitude above the Field Elevation. It's SOP in the military to zero your altimeter at your departure field. Do not set the barometric pressure setting as per civilian training. Be advised ED doesn't set QFE in the default cockpit state, they set QNH.

I'm trying to see if there's a way to use THESE awesome textures in DCS: A-10C. Can anyone think of a way?

Sorry, no. :( I think the website that put it out was http://www.rogerdodger.net/diyflightsims.html though.

I saw a DIY video on Youtube where a guy got one of those plastic keyboard protectors that fit his keyboard, and he labeled the inside of it. That way you could just lift it off and you wouldn't have to do anything to your keys.

in 720p. Not only does it seem to stay free of errors, but it's logic when you roll is different, like it falls with gravity. /thread hijack.

The small round button is the engage/disengage for the LA autopilot. The EAC switch is two switches over, to the left of the radar altitude switch. It's hard to see, and it doesn't have a key command by default. It's under the "LASTE Control Panel" category for your control settings in the sim. EAC Arm, and EAC Disarm.

I've been simming since Jane's F/A-18 released in 99, and I've never had rudder pedals. :noexpression: Planning on picking up a set in the next week or so. Having brakes set to a tiny button on a Saitek stick is extremely unsafe. :mad: Plus pedals let you be hands free. :) I'll need to find a way to keep my office chair in one place though.

Nooo way. Not game friendly at all. // What about XFire though? I don't use it myself but I've heard it's compatible with just about everything. That'd be cool. Just LEAVE GAMESPY OUT OF IT, PLEASE, PLEEEASE!

After watching the latest video Wags put out, seems they adjusted it in one of these upcoming patches. Both it's error accumulation and it's modeling. Anyway, yeah left click the knob and scroll your artificial aircraft back to the top of the gauge, then release. :)

Negative Ghost Rider. Not to my knowledge. Use a modifier if you want though. Shift, alt, control, windows key, and any combination of those. ED even defines the differences between LEFT modifiers and RIGHT modifiers. So L ctrl+c doesn't do the same thing as R ctrl+c. The pinky switch is an example of that. Alt+P, Shift+P, and Ctrl+P. You can even use a joystick button as a modifier. You can even map it according to keyboard logic. ie the alt key is closest to you - aft, ctrl key is in the middle of the two - middle, and shift key is on top of the two - forward. Orrrrrr you could look for a profile for a joystick. Sometimes community profilers can be really clever. For example my boat switch is set to the scroll wheel on my throttle. Scrolling back is aft, forward is fwd, and clicking the scroll wheel is center. Never would have thought of that. :P Lots of options.

Indeed. Plus who really has the mental capacity to be an ace in all of these aircraft? I prefer to stick to one jet and go from there until something better is released ( *cough* Hornet! *cough* ). I've already forgotten how to use the shvkal after having to learn the Warthog. :joystick: As long as they're multiplayer compatible, it's still the best air combat sim on the market for me.

Let me see if I can get a first reply in. :P Edit - Grrr Lucas ;) First off, make absolutely sure you're flipping your pinky switch in the right direction. One direction uses a generic lighting set that you are unable to change, and the other direction uses lighting based on your right aft console settings. The pinky switch needs to be AFT in order to set your lights manually. Check your key commands for that. I think it's ALT+P, but do not take my word for it. Does that help? If not, explain in more detail what you're switching. Remember formation lights and ACOL aren't going to do anything for your position lights. Post a track if that doesn't sort it out.

That'd be kinda cool, to have a single DCS launcher. But I imagine that might be inconvenient for devs and testers when trying to narrow down a bug. Especially when you've got different theaters/maps and additions like HDR and mods to the graphics engine with each release. Sounds like one big mess when something needs a patch. Solid point though, DCS isn't plural. ;) I just it'll be rather impossible until the entire simulator/map becomes set in stone - which might get boring after a while.

I've seen it done more than once ;). (Although, only by Navy pilots). :punk: But I'd like to at least see something in the debrief, if not outside/on the gauges.

Agreed. TARS is awesome. Built in VOIP on the radios would obviously be the best solution. Nothing wrong with TARS though, it'd just be easier.

lmao!! Imagine him going through the mountain passes. "Hawg 2-1, requesting tire chains." I'm curious as to the AI logic on that though. Did he actually intend on landing out? Seems that way if his gear went down.

@ED, is .7 still too early for the self shadowing? Progress on it seems to be moving quite fast. Really looking forward to this patch.

I was doing some simulated strafes (simulated attacks in a simulator:P) and when I planted the stick rearward to rapidly climb away, my right engine failed. I tried an in-flight restart, but no joy. I figured it must have been a bird ingestion. When I looked at the debrief, it didn't show any events other than takeoff and land. I was wondering if we could get some sort of an indication on whether or not there's engine damage. Normally you'd either be able to dodge the bird (as long as it's not a massive flock/murder of birds), and if not - be able to see the engine run quite rough and sputter, accompanied with some sparks and thumps, with visible blade damage when looking over your shoulder, indicating a restart would be unsafe. It's a shame not being given the cause of engine failure and no visual cues of bird ingestion - and it also makes it impossible to make a decision whether an in flight restart is necessary.