Machalot

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:

You think this source refers to the Phoenix?

Sure!

The key point is that it doesn't attempt to scan the waypoint, it just scans at the same range as the waypoint.

I think it's more accurate to say an INS is by definition inertially-referenced, not Earth-referenced. The accels and gyros measure motion relative to an inertial reference frame, and the Earth is decidedly not an inertial reference frame by virtue of its rotation rate of 15 deg/hr. It's easy enough to convert to Earth-relative motion for navigation purposes using a few equations in the software. My guess would be "rate gyro" since the outputs of the "moment gyro" in the block diagram are angular rates. Update: On the other hand In pretty sure the Viggen has a stable platform gyro system, so ignore this. (This is my opinion as an engineer, and I'm prepared to defer to you if you know otherwise.) My understanding is that the rapid start is because no alignment is performed at all. The runway heading is just taken as the initial heading of the dead reckoning process. The relatively poor accuracy of this method is tolerable because of the use of visual/radar nav fixes and ternav fixes to keep the drift under control. Perhaps the Viggen's gyros aren't sensitive enough to perform a gyrocompass alignment, which requires that they be able to measure the Earth's rotation rate significantly above their own measurement errors over time in order to find north. In principle any INS could be initialized rapidly like the Viggen's, by just supplying the initial attitude (azimuth, elevation, roll). In fact that's how the Stored Heading Alignment mode is initialized in modern jets, although they typically follow it with a gyrocompass alignment for 90 seconds or so to make it more accurate. But you could skip the gyrocompass step if the nav drift is tolerable or you can do nav fixes.

Yes. But there's also some weird toggling behavior. I don't remember exactly, but it's something like this: If you pull the breaker and hit the emergency trim again, then replace the breaker, your trim will be disabled. Then pull the breaker and the trim will work. That might not be exactly the right sequence, but I was able to get the breaker to function backward somehow.

We discussed several issues in this thread, only one of which was a loosely related bug if I remember correctly. Can you be more specific?

I would guess the altitude grids are 10,000 ft and the Mach grids are 0.5.

Are you within valid landing parameters with that much weight on board? I.e. maybe the jet is not designed to land that heavy.

Maybe the sticker was getting worn and unreadable so the ground crew slapped another one over top of it.