Coding

No, I just was expecting the values also being converted like different positions are also converted and not just used plain. but if that is correct, I have to get used to it

nope even with datalink,iff,tacan turned off and shooting down the awacs I get pinpoint accurate position with radar in silenced and standby mode for a few seconds only if radar is completely turned off, it behaves as expected new trackfile attached bugflight.trk

at around 08:23:30 ingame time I plan an approach to an airfield with an 122° magnetic course, setting up autopilot to hold the course, then decide to change the aircrafts degree mode from magnetic to true wich results in an immediate right turn and the COURSE NOT ALIGNED WITH THE RUNWAY ANY LONGER!!! the aircraft tried now to fly 122° true heading which is a complete different approach bugflight.trk

at around 08:17:55 I select some waypoints on the hsi page which have names attached in the mission editor: wp1: 122° wp2 "NO NAME SELECTED" wp3: 302° wp2 was inserted in the mission editor after (in terms of time) wp1 and wp3 but wp2 has the same name as wp3... bugflight.trk bugflight.miz

at around 08:16 ingame time I shoot an enemy with 2 aim120c. the first - despite the shoot "dot" centerd perfectly - immediately violently climbs up, the second which I already nosed up is better but still not good. bugflight.trk

at around 08:07:40 ingame time I silence my radar but it keeps updating the target position, distance, closure speed... after a few seconds it normally stops bugflight.trk

at around 08:05:40 I fiddle with the hsel option from the hsi page. when changing the aircrafts heading mode from magnetic to true the hsel value is not changing and it stays in magnetic mode. bugflight.trk

At around 08:03 ingame time I fiddle with the tacan options. It does not work in a/a mode. but when treating it as a ground station it works. bugflight.trk bugflight.miz

In the Hornet manual, the exp function from the sa page is not mentioned at all.

In the Hornet manual, the step function from the sa page is not mentioned at all.

At around 08:02 ingame time I use the step function on the sa page and select the tanker as "target". It multiple times resets to other aircraft without being commanded to. bugflight.trk

No, I do not have evidence about anything but I thought it is very counterintuitive in respect to the LatLong conversions: If you set a coordinate format and decide to change the format, the displayed numbers CHANGE and the positions DOESNT CHANGE . (as expected) With the heading and course on the bottom left/right corner of the HSI it is the other way round. The displayed numbers DONT CHANGE and so the executed course CHANGES. (not as expected) Imagine there would be a conversion between feet/meters. Would you assume the autopilot changing height because you wanted to see another format? me not!

How large the detection cone/range/volume is of a SU-30? It was tracking an E-3A at 30.000 feet at 90 nm when I started and switched to me at 62 nm. I was beaming at 50 nm and it still was tracking me. My radar was silent and ecm was receiving only. gci.trk Tacview-20211215-071209-DCS.zip.acmi

To be honest in the mission linked here I managed to get it right for the first time. All other times it is more like in the attached track where I engage atc approach mode when on a stable glideslope. But it just wiggles back and forth all the time. I feel WAY MORE SAFE when I control speed myself. atc.trk

can not reproduce in modern dated mission ignore my not so awesome ending... bombing.trk

Batumi runway is 306° true / 300° magnetic. When approaching Batumi with 300° magnetic and then switching aircraft degree from magnetic to true its heading and course settings stay the same resulting in a wrong approach angle. I would assume when changing the degree mode that the displayed course/heading would also be adjusted to stay on course/heading... hsi.trk

I have studied informatics, wrote a few mods for ArmA 3, wrote some Android-Apps, code for fun and just did not get involved in coding with DCS for a single reason. I do not want to offend someone personal but the documentation of the (MissionEditor-)API is a joke. Avionics plugin is not even mentioned. The path to the .lua file is wrong. AND... You have to read that twice. (or more) I do not know what you mean with "described"... This is what the "description" actually looks like: I had to guess multiple times to figure out what the "ELEM NAME" was. Let me tell you something. You might ignore it if you want to but this is my feedback which aims to improve your product. Eventually I might have reverseengineered some websites. But coding for DCS feels more like hacking than actually hacking. Hacking is just coding. coding for DCS... Just dont do that.

Jet was set up to start "from runway". The attack begins around 05:22 local time (22 minutes into the mission) Around 05:22:40 I checked the GBU-38s were aligned. My altitude was 35000 feet and I was flying with mach 0.89 At 17 nm range to target I got "in range" and at ~16.5 nm I got "in zone". At 16 nm I dropped the first bomb and dropped 2 other GBU-38s on other targets with very similar conditions. The 4th GBU-38 was dropped much closer to the target. The result was all first 3 bombs were falling way short, only the last hit the target. How can this be? When a targeting computer tells me that I am in zone I expect to hit my target with a GPS-guided weapon. tacview.zip.acmi trackfile.trk