Tholozor

That also matches documentation I've read that specifies the INU is updated "continuously" by the MMC Kalman filter through GPS data. Curious. Too bad we don't have INSM implemented yet as a sort-of "debug" we could use to monitor simulated data.

My understanding of real-world documentation that I've read (outside of the DCS manual) is that the system nav solution is raw INS info, plus master nav filter delta. If the delta exceeds 300 feet, it will then apply an update to the INS position. Based on this, I would assume that position errors should never exceed 300 feet provided SYS ACCUR and GPS ACCUR are both listed as HIGH on the NAV STATUS page. If GPS ACCUR is HIGH, estimated horizontal error for Precise Positioning Service or Standard Positioning Service for the GPS satellites should be less than 300 feet (if at least four satellites are tracked).

It's in the -1 manual. The A/R DISC button check is noted as only being applicable to D models.

Not at this time.

The Hornet doesn't use the MXU-648, they use the CNU-188 baggage pod.

I haven't seen the circle mentioned in the M4.2+ tape guide regarding the Sniper pod's functions.

Already reported:

You could always set the CMDS programs manually in the DED, the DTC just makes it easier to set it up ahead of time.

Pressing FCS RESET in combination with the Paddle Switch is supposed to clear BLIN codes from the FCS display, AFAIK the full functionality of BLIN codes is not implemented. Disengaging NWS should only require the Paddle Switch.

MGRS coordinates can only be used on steerpoints 21 through 25.

Please provide a track replay we can look at so your issue can be diagnosed.

JDAMs on the F-16 currently don't have absolute targeting modeled (directly on STPT coordinates), and only use relative targeting based on sensor data at the moment. This has already been reported as WIP.

Did you set the ACQ source to TADS? Also, by chance did you have the FCR installed and selected as the pilot's sight source?

It's also possible that previously we had the ability to set the codes with non-octal values (this would make sense for a 'rejection behavior').

Ensure you do not select the 'All' option when changing laser codes on the F-15E, this will bug out the laser codes and you will be unable to change them (the kneeboard will show all laser codes as 0000). If you accidentally select the 'All' option, you can restore the laser code functionality by rearming the aircraft. To prevent the codes from bugging out, change the laser codes for each station instead (i.e. 'Left CFT,' 'Right CFT,' etc). This issue has actually existed for quite some time:

A track replay would help us get a look at the process to see if anything is missing or user error.

You have to manually swap missions (PP or TOO) for smart weapons loaded on BRU-55 racks, it doesn't assign them to a specific weapon on the rack.

You released the missiles below the FLT setting; they don't climb to the flight setting. So if you release them below it, they'll cruise around the release altitude. You also released from an incredibly low airspeed, meaning the missiles had to expend more fuel/energy to reach their cruising speed.

Hi, welcome to the forums! This option was mentioned here, and marked as under investigation:

These are listed in the controls list as: - Transmit Switch - IFF IN (this would be right for "inboard") - Transmit Switch - IFF OUT (this would be left for "outboard")

Even if we wouldn't be able to support 120 midcourse off an offboard L&S, it would certainly speed up radar acquisition by being able to command STT on an offboard track via Fast Acquisition.

Your second waypoint is set to 20,000 feet MSL instead of at the target elevation.

AFAIK yes.

This will happen if you try to change the laser code for "All" stations (just opening the "All" option bugs it out, but you can recover from this state by re-arming the aircraft). The current workaround is to change the laser code per-station instead (e.g. Left CFT, Right CFT, etc), this will not bug out the codes.