Gronank

If you create your own scenarios, you can put down a steerpoint on something lockable along the way and you can get the boresighting done in less than 30 seconds with minimum hassle. You still have to do it, of course, but it isn't a massive pain (compared to trying to get it done on the ground, for example)

I've run into this recently. The missile doesn't maneuver until it is burned out consistently when is launched at 15k feet within max range but outside the no-escape zone. Notably, the missile is not lofting when it doesn't work. When launched inside the no-escape zone, there's no problem and the missile tracks as it should. It is unclear if it's also a problem when the missile is lofting when fired at higher altitudes because the AI only starts maneuvering after the missile is burned out, but I've never noticed a problem. Mirage_misssilebug_nottracking2.trk

I actually managed to get MOOSE and the native script api running in VSCode a while back with live debugging. Attached is an instruction for how I set it up: VsCodeSetup.pdf There's also a script file needed for debugging: remote-debugging.lua The script is an amalgamation of devcat's debugee script and its dependencies The instructions significantly based on some instructions I found somewhere, unfortunately I forgot where so I can't give credit where it's due.

"Longest" would work as well.

In the manual, on the topic of Rocket/ Gun pod attack profile, there's this description: The word "latest" usually refers to a time, not a range. But because the plane is a moving object, I parsed the meaning to be "closest" because that's where the plane would be at the latest while travelling through the firing range and that therefore the shooting que was also somehow also the pullup que. "Furthest" would be much more clear here.

That must be it, thanks! Sorry for the false alarm.

Reproduction: 1. In navigation mode, press OBL on the PCA. Radar enters TAS mode, target diamond and range que appears on HUD, all expected. 2. Trigger the fix using the "Magic Slave/AG Designate/INS Position Update" button. VAL and REC buttons lights up as expected. 3. Select pho/theta on the PCN =>The display shows the offset from the original waypoint to the aircraft at the time of the fix. Expected: the offset should be from the original waypoint to the point pointed to by the diamond. In the attached track file, the expected offset is 500m at 262 degrees. I see in the documentation that the Magic Slave button is used to do a positional fix. It certainly does this but the problem seem to be that "OBL" is simply ignored, making radar fix impossible. oblBug.trk

This passage had me scratchinng my head: What is the significance of the P.CAB light to the ejection seat?

AP disconnect is generrally a button you want mapped anyway, easily accessible too

Sure, start by installing this mod: https://github.com/Quaggles/dcs-input-command-injector tobe able to place custom binding in your dcs saved games folder. Then unpack this in your dcs saved games folder: InputCommands.zip

I ended up creating custom bindings for radar range and mode select (and a few other things).

Tables are available in the kneeboard

This module really needs a special option scale bar to increase the hud text size.

I recently discovered that the script necessary for setting a AA tacan on a tanker has changed. It used to be that you set the tacan frequency and now you set tacan channel and mode. I think this is an definite improvement in usability, but it would be good if this change was listed in the change log. I believe the change was made in the patch from 17 march ("Inconsistent A/A TACAN behavior fixed. Tankers in old missions now get correct TACAN frequency at the beacon creation.") A line such as "BREAKING CHANGE Scripting. Activate Tacan command now requires channel and band properties to be set" with a link to (updated) documentation for details would have made life easier.

"That M163 VADS over there looks like a smooth ride"