Machalot

You could dig through this thread to find the actual posts on this topic, including screenshots of the NASA report, but there were really only a handful of trajectories published in the report, at maybe 2 or 3 altitudes and 2 or 3 Mach numbers. And only some of them have the same mass as the in-service AIM-54s. Unfortunately it's not a data set sufficient for model validation across the flight envelope. It's a good spot check, and the HB model passed with flying colors.

Way back in the pages of this thread, we discussed the fact that there was no NASA test. NASA developed a simulation based on public sources, possibly the same sources HB ended up using. To HB's credit their independent model was shown to match the NASA simulation results very closely, even though they didn't intentionally refer to the NASA model when building theirs.

I think this isn't just a Kola issue. On roadbases on other multiplayer maps, I have always needed to enter the runway heading manually.

But who says the QA team has any spare time to test something like this when they're also incorporating massive changes to the F-4 on a tight cycle? Maybe working 10-12 hour days already, weekends, who knows. Accepting changes from a third party requires a lot of testing to ensure nothing else gets changed for the worse. We know from experience that changes to "only" basic weapon parameters can result in 58-page forum threads, full of complaints and debates, that still get new posts 18 months later. Again I'm only speaking based on my own experience writing software professionally, not on anyone's behalf.

I can't speak for anybody but myself. But there's a nontrivial amount of work required to incorporate code or script changes, even moreso when they are provided by a third party. Software QA, testing, repo maintenance, etc. I can only speculate they don't have the resources to spare, and this is one more little thing that is not a high priority compared to, say, shipping the F-4.

It's not that DCS doesn't have such a model. The particular parameters for the AIM-54 were set to use thrust adjusted to at a specific altitude and zero nozzle exit area, which effectively disables the effect of different altitudes on thrust.

It's somewhere in pages 3, 4, or 5 of the kneeboard. If there are more bases in the map than can fit on the page, you can scroll between pages using RShift + PageUp/PageDown. The font is different now compared to the one in TOViper's post.

If I remember correctly, the nozzle exit area was not modeled for the AIM-54 in DCS, so altitude doesn't affect the thrust.

The location of LS is roughly the center of the runway, which is where your nav system initializes to at liftoff. If you change BANA to a different runway and you don't have the opportunity to do a fix after takeoff, you should change the LOLA values of LS to the center of the runway you're using.

Hey Snappy, As I suspected, the comms channel settings for the missions all kind of got messed up when they redid the radio channels in one of the patches, sometime in the past 2 years. If you are comfortable looking inside the mission files (C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AJS37\Missions\Single\Hunting the Hunters_SP.miz\mission), you'll find two pieces of information to solve this issue. The assigned frequency for the Viggen flight is defined on line 1220: ["frequency"] = 123, There's also a section defining the player aircraft radio presets (lines 941-996). ["type"] = "AJS37", ["Radio"] = { [1] = { ["channels"] = { [1] = 123, [2] = 264, [3] = 265, [4] = 254, [5] = 250, [6] = 270, [7] = 124, [8] = 257, [9] = 255, [10] = 262, [11] = 259, [12] = 268, [13] = 269, [14] = 260, [15] = 263, [16] = 261, [17] = 267, [18] = 251, [19] = 253, [20] = 266, [21] = 305, [22] = 264, [23] = 265, [24] = 256, [25] = 254, [26] = 250, [27] = 270, [28] = 257, [29] = 255, [30] = 262, [31] = 259, [32] = 268, [33] = 269, [34] = 260, [35] = 263, [36] = 261, [37] = 267, [38] = 251, [39] = 253, [40] = 266, [41] = 305, [42] = 264, [43] = 265, [44] = 125, [45] = 121, [46] = 141, [47] = 121.5, }, -- end of ["channels"] }, -- end of [1] }, -- end of ["Radio"] At some point Heatblur reworked the radios to give us access to more presets, and in the process they reordered the way the array elements get assigned radio channels. Now elements 41,42,43 are Special 1,2,3, and elements 44,45,46,47 are channels EFGH. Elements 1-40 are assigned to channels 100-109, 200-209, 300-309, 400-409. So in order to talk to your flight on 123 MHz, you need to set channel 100, which is Grupp 10, button 0.

It seems the seeker model for Mavericks in DCS is not truly contrast-based. It seems to require the presence of a live unit, for example if you see a unit as a dark spot among similar-looking dark trees, you can only lock onto the units, and not the trees, despite having the same contrast. Maybe there's also a binary setting that says "it's night, targets are only visible in IR and not the visible spectrum", ignoring the actual contrast.

I have the same issue with a Reverb G2. Hoping somebody finds a fix.

The Viggen can land on carriers in DCS, I've done it many times. Have you tested different descent rates to see if the gear will hold up?

I thought that was fixed already. Maybe I'm thinking of the in-game tooltip.

The figures look correctly matched with the paragraphs to me. But the captions are swapped.

Ok. I had in mind the more general definition of height given on that IVAO page, i.e. the distance above any datum you choose, which is often the ground but not exclusively. Edit: Also the wiki article you linked to says altitude is not so rigidly defined either:

Can you provide a reference for these definitions of height and altitude?

And you're leaving the INS in NAV mode?

I have the same problem. There is no key or button I can find that returns to the steerpoint except to switch to the FCR.

I agree with RPY Variable, this sounds like a misaligned or noisy joystick axis. Any nonzero input will override the autopilot.

Are you possibly switching to ground power and shutting down the engine while you rearm? For some reason the Viper in DCS can't transition between external and internal power without messing up the INS. In general you don't need to switch to ground power when rearming, and the INS should maintain its state if you just keep it in NAV.

I don't know but I can try a guess. ADR seems to be available when the target is jamming. It may be a method to find an upper bound on the target's range by applying reasonable assumptions on its altitude. Since you get an angle measurement from a jamming target, and you know your own altitude, you can form a triangle between yourself, the possible target range, and either of two altitude planes (the ground and, say, 50,000 ft, pick your upper value). With this triangle you can find the max possible range. That would be my guess.

I speculate it has something to do with processing a "first" and "last" rocket so they sweep out a range of impact points. In single mode, maybe it's giving you a shoot cue for the "last" rocket only.

As the antenna goes to the extreme upper and lower elevations it is constrained by the shape of the round nosecone, so it sweeps a shorter left-right distance.

Pretty good. I think you should remove all the quotation marks. The last sentence about the four borders could be simplified too. I suggest something like: