Nlaw - Update to use Missile Guidance Framework

[TheCandianVendingMachine]

When merged this pull request will:

• Update NLAW

Merge Strategy

you know the drill

Follow #10019

IMPORTANT

• If the contribution affects the documentation, please include your changes in this pull request so the documentation will appear on the website.
• Development Guidelines are read, understood and applied.
• Title of this PR uses our standard template Component - Add|Fix|Improve|Change|Make|Remove {changes}.

[PabstMirror]

it's pretty good, but maybe a little sluggish to make turns as expected?

[PabstMirror]

var not used

[TheCandianVendingMachine]

it's pretty good, but maybe a little sluggish to make turns as expected?

So this error has been present ever since the rewrite and I have been trying to determine why since. Right now, my thinking is that there is an accumulated error in the autopilot.

Although, in the limit, the real turn rate will equal the calculated turn rate, because this rate is achieved off-path it will not turn as desired. My current thinking for a solution would be to calculate a new target turn rate each dt so it can follow the predicted path.

Why don't we just set the yaw and pitch rate to be the calculated rate at launch? Good question! This was the idea in the first implementation, but (and forgive me for not remembering specifics) it would not follow the path still. I think what happened was that the missile would fly into the ground eventually due to no altitude holding correction, and this bug was present in the yaw as well in some scenarios.

The bug you showed is the only reason this missile has "known bugs", and I don't know the correct route to solve it; my vector math skills are very slow