tom_19d

Hi Dave, that math looks great to me. And correct, doing it that way, when you land your altimeter should indicate field elevation, 1840 feet MSL in this case. You should be able to practice this in game by flying into the Russian fields where they give QDE and checking your work in good weather, I have tried it a few times myself since this thread started without issue, so if you have any problem in the sim let me know. PS: at least in the US we transistion to QNH as we descend through 18,000, but I don't think anyone in the sim will complain if you switch over at 15k haha. Plus different countries have different rules anyway.

PDF Here https://belsimtek.com/news/1643/

Hi Dave, please stop trying to do anything with hPa or anything that involves dividing anything by 27 or 30. You have the math correct in your above example. The problem with the scenario you pose is that if a field with an elevation of 1000 feet had a pressure setting that low it would be in one of the worst hurricanes ever recorded- that is the only way to get that low of a QNH setting. If you try your math again with a more reasonable QNH like 29.50 (QFE 28.50 in this example) you will see that you are doing it correct, you just chose an unrealistic QFE as a base point for that airport.

The OP never asked how to make the altimeter show zero when the aircraft is on the ground. He asked how to convert QFE to QNH, just look at the very title of the thread. "DAMN IT. I JUST DONT GET QFE 2 QNH SETTINGS in F-5E" Also from the first post... No cartography department so that means we have no plates? The 476th would disagree with you. 476 vFG Flight Info Pubs Their TACAN approaches and SIDs out of Vaziani are a riot. Plus you don't need charts, even on a server with no own ship on the F10 map you can always see field elevation of the field you will be landing at. To convert QFE to QNH there is an easy solution. Dolfo and I have both covered it. Field elevation in MSL of landing airport divided by 1000. Round this number to two decimal places, add it to QFE. Put this in the Kollsman window, you have QNH. Not simple? Move a decimal point three places left and add. I can do that in my head and I am terrible at mental math. Two people have answered the OP's question and shown the math using the scenario posed by his original post. Our work is visible, if it is wrong please explain how. I'm not trying to be contentious but much like 33-DFTC I am floored that this thread can possibly still be going on.

Thanks for linking to my post Dolfo, I was starting to think no one actually read it haha. Rep inbound for the PHAK reference. And +1 to not worrying about hPa in this case.

Imacken, I feel like this thread is slipping into a QNH v QFE discussion; while that is no doubt valuable and I am guilty of helping it go in that direction, it is missing the point that in the scenario posed by the OP QFE is not a valid solution, it is physically impossible to use. Regardless, I certainly didn't intend to talk you out of a technique that clearly works for you and many others and if that is how I came over, rather than just stating why I prefer QNH, my bad.

Yurgon, you do indeed have me on line 8, I was incorrect there. Never let it be said I am not gracious even in defeat haha. Safe flights!

Also for the OP, Dave, I think you are making things much harder on yourself than you need to by keeping your F10 map in metric. The only device on your aircraft to show your altitude indicates feet above mean sea level. The only device on your aircraft to measure distance for the purpose of radio navigate indicates nautical miles. The idea that metric units are somehow related to a JTAC/CAS call (outside of adjustments like drop 50, left 100, etc) is incorrect. The Army and the Marines use the same 9 line format to call for CAS. Line 3 of a fixed wing CAS request is the distance from the IP to the target in nautical miles. Line 4 is the target elevation, given in feet above mean sea level. No where in a 9 line fixed wing CAS call is a metric unit used. If you are just flying the F5 I can’t see any reason to use metric units on your F10 map at all, maybe that could help reduce some of these headaches.

Imakan, lots of people (me being one of them) have no use for QFE having spent whole lives/careers/ etc using QNH, as outside of Russia the entire rest of the world uses QNH. Additionally, as has been mentioned, all of the published instrument approaches for the Caucus and Nevada are written to use QNH. Finally, as has already been covered in this thread multiple times, most western aircraft aren’t made for QFE. For example, the F5 altimeter only rolls down to 28.10. This means, given ISA conditions, the F5 CAN NOT use QFE at fields above ~1800 MSL.

Okay right on. Poor assumption on my part, I was stating all altitudes in feet, pressures in inches of mercury as are used in the F5. My DCS map displays altitudes in feet. I don't know if it is possible to actually make it show meters, but maybe it is. Regardless, I doubt an F5 could ever use any runway at 4446 meters MSL. That is 14,500 feet, you would have to measure the F5's runway at that elevation in miles not feet. What airport are we talking about here? that might be a good start.

Are you referring to my method Dave with your questions about units?

Give this a shot. Find your field elevation using F10 maps, TERPS, whatever. Divide field elevation in feet MSL by 1000. Round to 2 decimals and add this number to the QFE you are given. Put it in the window. Unless I am wrong this should get you close enough for shooting a TACAN approach to mins in the F5. EDIT I never even read the first message of the thread but this works to with 10 feet in your above example. Field Elevation (4460) / 1000 = 4.46 QFE (25.23) + 4.46 = 29.69 (Within .01 in/mg AKA 10 feet of field elevation) Obviously there will be some variations here with large deviations away from ISA but nothing any of us mere mortals would be able to detect shooting said TACAN down to mins

Outstanding, happy to hear about the decision to drop own ship position off the map. On top of the improved realism, as an unintended consequence this could possibly make CGI controllers even more valuable.

+1 for Korea 1952!. It is a fantastic experience, just make sure you have Simple Radio running and read the briefing information.

Hi Dave, I haven’t read the book and I certainly don’t have a lot of knowledge on the F20 (other than that I sure would appreciate the extra 50% thrust or better that big GE 404 supposedly put out), but I just have always had the best luck in the F5 keeping my head on a swivel and out of the cockpit- at least in my experience by the time the radar can acquire a fighter sized target, if it is VMC they will be visible to the eye. I’m sure there are a few people that can play the radar like a piano and use it very effectively, but if I try I just turn into a victim for a MIG21 driver whilst I try to look at the little screen... Cheers

Not at all Sharkbait, if I came off as offended that was unintentional, I didn’t mean to sound harsh. Safe flying and good luck, I hope DCS provides you as much entertainment as it has me! Cheers

10 km away and you expect to see a piston single every time in every condition? That is over 5 nautical miles...you might get lucky now and then but even with a very timely traffic call from ATC most people won’t make that spot. One of the reasons DCS is great is because it gives a realistic depiction of just how difficult it is for one pilot to spot another in small aircraft moving at great speeds. In particular, fighting in jets without labels is humbling and it SHOULD be. There is a reason only a fraction of a percentage of the human population can do it for real...

Hopefully someone with more multiplayer experience than me will come in and back me up here...the issues with DCS AI have been addressed plenty on this forum. IMO the F5 really doesn’t shine air to air until you fight other humans. That said, the F5 is a day VFR fighter at heart. It is possible to craft carefully scripted scenarios with the ME that require the use of the radar, however, these have basically no resemblance to an actual F5 engagement. Without IFF or very specific GCI/AEW if you can’t visually identify the bogey you can’t shoot. The F5 doesnt have IFF and turning on your radar is a big flashing “here I am” for anything with an RWR. Join a good server, acquire visually (with POSITIVE assurance of aircraft type), and get into a fight. For me this is where the F5 is at its best; it seems like too many people want to get hung up on tertiary systems like the radar when the airframe itself and a good visual scan is all you need to be successful in a furball.

You are correct, range information will only be available with the radar on. However, I very rarely use the radar in conjunction with missiles because without an IFF, visual recognition is the only way to tell you are shooting at an enemy (highly scripted scenarios being the exception here). My experience over numerous online engagements is that if you are close enough to visually identify a bogey as a bandit and have a reasonable aspect angle, you are close enough for a missile shot. Turning on the radar just makes you more visible to RWR equipped aircraft.

Agreed with Comie- from what I have seen a lot of the server population depends on the time. When it is morning in the US/evening into night in Europe the Reds have a lot more players. At least generally... That being said, I haven't been able to see the server since last night, I'm not complaining, I just want to make sure it isn't just something on my end. Thanks all.

Hi Imackan, There seems to be a lot going on in this thread- it sounds like you obviously understand the systems so I can understand your frustration with the uncaged behavior. The only thing I can think of (maybe this is insulting but I don’t mean to be) - there are 2 cage bindings on the throttle. One is “missile uncage” and the other is “sight cage.” Missile uncage is the one in question here. And as an aside, outside of youtube videos I have never seen the pipper move outside of the reticle, as has been brought up here. Regardless of the method of lock I use (manual acquire in MSL or DM) I have never been able to duplicate this (at least in the latest build of 1.5). Outside of a binding mistake, I can’t understand why you would be having this problem with the uncage behavior.

One last thing with the ADF - depending on your personal feelings about the realism of the kneeboard, it does display down to a whole number the freq you have tuned. It isn't always perfect in the case of frequencies within one digit of each other but it gets you in the ballpark and can be a good training aid.

Working great here. Started up engines in MP, set manual and depression 10 for rockets and AG guns - pipper moves down. Set MSL mode, pipper recovers. The only way I could make the pipper not move with the depression knob while in manual mode was to have either DG or DM mode selected, but that is functioning as designed. Sorry, aside from the position of the dogfight switch I can’t think of anything that would cause the condition you describe.

Aztec, With regards to ADF nav, myself and many other players have been using it since the last game update, so the system itself isn’t bugged, unless like Art said it is related to the specific mission you are playing. I would just fire up the mission editor and put yourself airborn in the vicinity of a beacon, that would take the mission variable out of the equation. I’m not sure what you mean by “the switch to adf” as the ADF setting on the ARC 27 comm radio isn’t modeled. Just set the ARN 6 radio to “COMP”, tune the frequency, identify the Morse, and you should be all set. The radio compass will be indicating a relative bearing to the station. One other possible gotcha here, the F86 generator doesn’t keep system voltage high enough at idle to always keep the radios functioning - however, as long as you can still hear the ident you have enough power in and the system is working. Tom

I would second Midnightzulu, the gunsight symbology really shows you everything you need to know if you have the radar on. The "lock on" annunciator is irrelevant- if the range bar is in view wrapping the right side of the gunsight, the radar has a lock on something. The "in range" annunciator isn't needed - the diamond will appear on the gunsight's 2 o'clock if the radar decides you are in the missile envelope. All of this right through the gunsight, no reason to go heads down in a WVR fight. To answer the OP though, for missiles I rarely if ever employ the radar. Turning it on in MP is like a flashing "here I am" for any enemy with a RWR and it has been my general experience if I am close enough to identify another aircraft as a bandit visually, I am close enough for a missile shot. And I do uncage just before every shot - if the seeker is really looking at something when you uncage, you will hear the tone increase in pitch. About the only thing I will use the radar for is DG mode for a little help with holdover/ranging for a guns shot, but even then a snapshot from the fixed pipper is usually doable.