some1

That's F4.

The bearing and range in the upper left corner of TAD should be relative to the cursor, not the ownship. Unless the cursor is over ownship of course. Source T.O. 1A-10C-1, chapter "TAD format". The one easily found on the internet. Basically like in other DCS jets, the bullseye-cursor position should be visible on the screen without much action from the pilot, so it is easy to make and resolve bullseye calls.

I played this mission yesterday and can confirm that this happens. AWACS is constantly spamming about "pop up targets" somewhere in the distance, and this blocks custom messages from other parties. These messages appear in the message log, but no audio and no text on the screen. Very easy to miss. Also the DCS JTAC, he's useless, he just said "no further tasking available, you can depart" right from the start. There are coordinates for the bunkers on one for the kneeboard cards but not anywhere else in the briefing documents. Anyway finding the bunkers is not hard, destroying them with the limited amount of HE weapons is. I've passed this mission only because I've saved my wingman for this task. Meanwhile, I was busy hunting Iglas hidden between the tents, that need to be destroyed to advance the mission.

I've just finished this mission and the jtac worked fine. Make sure you talk to him on the FM radio, which is comm switch aft. Trying to contact him on the other two radios (comm switch forward or down) probably won't work.

So here's another public reference, a cockpit video from one of the Shaw's F-16C Block 50s which is as close as we could possibly get to DCS model. The resolution may be too low to make up numbers but they sure look to me more like ".5" and ".6", not ".5" and "1.0". You can see during high speed dive at 6:10 that he goes between two thick marks on the scale which correspond to .5 and .6 Mach, That's ~330 kts and ~400 kts respectively at low altitude, the math checks out. The indicator in DCS does not look and does not behave like that.

Look at the cockpit diagrams in the -1, they show the gauge spacing on a picture.

T.O. GR1F-16CJ-1 that's everywhere on the internet and probably every other dash 1 manual will have this gauge drawn in detail on every cockpit layout diagram, with the scale as I described. You can check your existing reference too, it's already there. It's a common gauge type, used in many USAF aircraft.

The mach gauge below mach 1.0 should show the speed on a scale in 0.05 increments, not in a single 0.5 increment as it is now. It's correct in DCS F-5.

The FFB trim offset option in Special Settings has the same problem as in F-15E. This is not how FFB should work in the sim.

Yeah, I know you're not in EU, that why I don't know how the shipping works in your case

I can only speak from my experience with my throttle, but I don't have such issues. Well, throttle(s), as I have F-15EX and I had the first Orion with Hornet grips previously. - no issues with Windows not recognizing the hardware - idle detent can work exactly like in Thrustmaster Warthog. No problems with buttons other than some games like IL-2 not recognizing those above 32 or 64. Not DCS though, here all work, and it's easier to map them than with Warthog because every switch position reports a separate button. - no quirks or noises in throttle movement. You need to adjust the tension from time to time. The old Orion I was a bit less smooth than my Warthog, but Orion II feels better. I'd say if Warthog is 9/10, then Orion I was 8/10 and Orion II is 10/10. Who knows, maybe I just got lucky twice. Yeah, ordering something from China directly you kinda have to assume that you're on your own if something breaks. The distance, language barrier and high shipping costs make it really hard to get support. They now have a distributor in EU, but I don't know how it works for Switzerland.

Ok, so it looks like for VOR the CDI is correct, but the HSI bearing needle is not. These two needles should align as I explained in the first post. The bearing needle should point to 200 on the HSI, yet on your screenshot it points to 188, which is neither magnetic nor true bearing to station. The GPS showing true bearing to waypoint (BRG 211) also contradicts what's written in IndiaFoxtEcho's own MB-339 manual:

No, VOR is equally broken. You can test it in the attached mission by tuning into 116.90Mhz McCarran VOR. AHRS is not an INS. It cannot sense true north and it is not doing any calculations related to that. The only sensor it has to orient HSI is magnetic. GPS has a built in magvar database (it can even display magvar to the pilot) and is perfectly capable of displaying magnetic bearings and course deviation. In fact, it already correctly outputs magnetic waypoint bearing for the HSI needle, but not the course deviation for the CDI. It makes absolutely no sense to steer CDI using True as it does now. mb339_fail.miz

In DCS F-16 the arrow-shaped hand is counting seconds, and the thin needle is counting minutes on the timer. They should be swapped, so the arrow-shaped is counting minutes. That way the minutes hand of the clock can't be confused with any of them. It's correctly done with the same clock type in ED's F-86 and F-5. Only F-16 has this issue. Here's a video of a real clock of this type. https://www.youtube.com/watch?v=_W0SDdSjrnU

And it shouldn't. VOR and TACAN radials are oriented to magnetic north. No HSI in real life behaves like that.

It should, at least in theory. DP is backwards compatible.

5800X3D. DCS won't benefit from the extra cores on 5900

Display port 2.1 is not a requirement for 4k high fps gameplay, because most high FPS monitors on the market support DSC compression, so even DP 1.4 can do 4k 240Hz.

The Elapsed Timer hand is missing, and the timer button on the bezel has no function, should be stop/reset/start. The seconds hand should be used by the timer and not the main clock. You can also check how it's done in other USAF aircraft in DCS, F-86, F-5, F-14 and F-16 have it modelled correctly.

The HSI should have two long lubber lines that extend from the top and from the bottom touching to the compass card. They should be visible from any angle. In DCS the marks are tiny, the same length as the short marks at 45 degrees. In fact the top mark is so small, it's invisible from the default seating position, making it impossible to tell what is your current heading precisely.

I wouldn't read too much into it. Sure, ED may have the final word and decide not to release two modules in a single patch, but none of the modules you've listed are ready for release. F-4 is not delayed because F-15, it's delayed because development took more time than HB initially estimated and now they tentatively declare "this winter". A-6 module is not even on the roadmap for 2024.

That's magnetic declination (aka magnetic variation). Compass deviation is from the interference from metal aircraft structure and other equipment surrounding the compass. It's unique to the aircraft, not mission date.

It's less about the cable itself and more about how much power can your motherboard or hub provide on the USB port.

Thanks. TACAN equipped aircraft should be able to receive DME readout by tuning to the channel corresponding to the ILS frequency (for example 40X for 110.30). Not every airport has DME combined with ILS, but most civilian airports do.

Bump. The game still does not support ILS DME, which means most ILS approaches on all new maps are badly coded and don't match real world charts, as most approaches in real world use ILS/DME. For example: