LazyBoot

Bx points are not relevant to the bk90 Just as a heads up, you can add the M2 point directly from the map, no need to add it as a B point and changing it later. That said, did you verify that you had WP 2 selected before releasing the weapon?

It used to be that whatever you put in the cartridge would only overwrite the currently loaded data... but at some point a little while back it was changed so that loading a data cartridge will clear out any previously loaded data.

Or alternatively, you can use SPA mode to mark targets.

What makes a helicopter different from a moving vehicle? (as seen from the missile)

just like with game updates: new preorders or releases don't tend to become available until the afternoon (UTC)

Mine keeps the first stage "button" pressed until the trigger is fully released. So both 1 and 2 are considered pressed during stage 2. I can't say if that is universal among them, but at least that's how the VKB NXT works.

On a 2-stage trigger, I personally find that using the first stage for unsafe is best. So depending on your setup, that could be somewhere you could "recover" a free button for TV or T1

Are you pressing T0 or T1 once done (before exiting A/A mode), or using one of the binds that resets to T0 on release? If not it could still be considering you as pressing TV which will do a nav/radar fix.

Have you looked into the Community Keybinds Project? https://github.com/Munkwolf/dcs-community-keybinds They add in quite a lot of the missing keybinds for the majority of modules I did check and they do have fixes for those exact keybinds you mention having issues with.

From what I remember heatblur having said, they were programmed as laser guided because at the time they added the missiles there were no other weapons with the right guidance in DCS, which is why they explode once the launching aircraft dies.

I'm not sure redoing the entire guidance for the missiles is a "super simple lua edit"

@widen76 So I noticed something a bit odd... The 1975 version of Part 2 has an entire chapter that's missing from your OCRed 1994 Part 2, with things deemed too secret to go into part 1. Is that something you're also planning on looking at later down the line?

We've had way too many issues with modded weapons being used for griefing in the past to allow weapon mods even if it is a PVE server. And we have been recently informed that weapon mods now lie under the "pure scripts" setting.

Having recently gotten myself a controller with rotary encoders, I'm also running into this issue now... while I would expect it to jump one step for each input, it will only take one input then ignore several unless I pause for a substantial time between each attempted input

Try pushing AI menu down

Just checking, but have you tried both settings for his ROE?

You want just the 3.0 download, not the one with "English" in the link Though as a small addition: the imperial version doesn't replace the metric readouts, it just adds feet and miles as extra. Though if you don't want those, then just don't download that extra one.

I've seen some reports that the latest version of the WH throttle comes with an improved slew by default now. Though apparently the default update rate on it is still the same.

I've been using the dark theme for some time, and I've frequently noticed some posts where text will have white backgrounds (see first image) or they will have text color as black making it blend into the background and making it really hard to read. (image attached) Is there anything you guys can do to make things better on the forum side?

Having IFF on or not as the target does not matter in DCS (with the exception of JF-17 vs JF-17)

If placed close enough to the FARP it will work Also, if using an invisible FARP you can set the "runway" heading by rotating the FARP in the mission editor to the desired heading in order to have it auto-populate.

probably a dupe of this one

Yeah, I would almost think it would be mentioned somewhere if it was supposed to be hidden.

Setting a waypoint by entering a popup point on it doesn't work... (without marking it with 9 first) Even though it should be enough according to the IRL manual.

Boundary (gräns) lines are hidden if set on a target point that also has a popup point set. Is this correct or a bug?