lukeXIII

What are the exact coordinates you are trying to enter? Currently only the "DDDMMSS" format will be accepted, so it's possible what you are entering is not valid.

From the video the distance changes as he moves off target

Looks like it's not fixed to the designation in IRL hud footage (although this a RAF harrier and not an av8b) null

The "Position Marking" section in the NFM-000 states that upon pressing the TOO button, the point beneath the aircraft or designation is stored as a markpoint and you are then given the option to also store this as a targetpoint.

Markpoint offsets do not work currently, I reported this a while ago

Values 0-100 are in nautical miles, values >100 are in metres. The UFC will display either "NM" or "M" to show this.

Intended behaviour. The base AGM-65E does not support self lasing, unlike it's later versions

With the manual fuel system turned on, throttle position should be directly related to fuel flow (with max flow of 260 lb/min at max throttle) and should not contain any limiters. At high altitude you might only reach half throttle position before exceeding recommended max RPMs. Currently in game the RPM becomes limited at about 111.5% after which the fuel flow at max throttle starts to decrease with altitude, which is not correct behaviour. MFS.trk

Engine life count, max JPT and OT time are randomly generated at mission start and have no effect on engine performance. IMO RAZBAM should change max JPT and OT time to start at zero so we've got a better idea of what we're doing to the engine. Can you upload a vid of your VTOL issue?

Try dumping the water before you start and also turn on combat thrust. EDIT: Reread it and it says he was using the manual engine control. As far as I can tell this isn't implemented correctly which could be why the numbers are off

(With no designation) Pressing the markpoint button on the EHSD creates a markpoint in the air instead of on the ground Markpoint 0 range is not updating correctly in the HUD (it is currently using the range of the last selected markpoint) Unable to create markpoint offsets Pressing the TOO button should automatically create a markpoint (there shouldn't be a markpoint and waypoint ODU option in TOO) markpoint.trk

@BIGNEWY any updates on this? The A/A Tacan PROX function in the AV8B has not been able to work with tankers due to this change.

Was having this issue as well, updating graphics driver and repairing dcs world fixed it for me.

It was with fuel tanks and aim9's, similar to what was in the video as pointed out by Ramsay. Same conditions but clean you can sustain 460 knots whilst pulling up to 6g.

How much fuel does he have? Is he using combat thrust?

1) The video doesn't show what the ambient conditions were, the rpm reached or the gross weight. Not enough information to compare turn rate. 3) Trim should be set to 2 degrees nose-down, for shore procedures. That being said trimming nose down is also not working well. Rotating the nozzles down should result in a pitch up moment which doesn't seem to be modelled.

From the 2008 NATOPS 23.10.2 The last digit input should be flashing on the scratchpad When ENT is pressed the scratchpad should flash momentarily then display the new entry if valid If entry was invalid, then the scratchpad should continue to flash until cleared

A couple issues I noticed when pressing undesignate: With TPOD unselected; pressing undesignate is causing the selected waypoint to disappear and reappear off the HUD. With TPOD selected; pressing undesignate is causing waypoint to disappear off the HUD and will also leave DESG boxed. With LMAV uncaged; pressing undesignate causes the seeker to float off to the side and can become unusable. undesignate.trk

It looks like the ODU menu for quick access is incorrectly being used for TOO. Only targetpoints should be available in the ODU/scratchpad and markpoints should automatically be created upon pressing the TOO button.

@AlphaJuliet Looks like this isn't fully fixed as consuming water is currently causing the Max F+W to increase. To show this the above calculations can also be written as: Max F+W = Max hover weight - base aircraft weight - stores/pylons vrest_water.trk

From what I saw of that track you were able to uncage and get a lock fine. Only issues I could see was that your nozzles weren't fully aft which would prevent a launch and you weren't getting the INRNG que (probably going too slow). EDIT: As said above, you are late getting a lock because you weren't pointing the cross pattern on the target.

In theory in order of preference: CCIP/AUTO is used if a target has been locked in the DMT and there is sufficient angle rate RCIP/RAUT is used if the above is invalid, "BOMB" has been colonised and radalt is less than 5000 feet GCIP/GAUT is used if the above is invalid, "GPS" has been colonised and GPS signal is available BCIP/BAUT is used if the above is invalid In game however there is functionally no difference between these modes so it doesn't matter what you have selected. The HUD will also show CCIP/AUTO whenever you have DMT selected, regardless of if you have a lock or not. That's not quite correct. Slant range is derived from true velocity, line of sight angle and angle rates. Height above target is then derived from slant range and line of sight angle

After some more testing I'm fairly confident that the extra waypoint that gets added is what's causing all the issues.