Santi871

There's no wpdsg mode, target steering is selected while a target designation exists and deselected when it doesn't.

It is.

This is not a bug. The only way to invoke the stored SET settings is to select a weapon with the weapon select switch that is different from the currently selected weapon while the radar is in RWS or GACQ.

Yes, I've reported it.

Look at the PRF. Target was detected on HPRF, radar was on a MPRF pass when STT was attempted so it uses MPRF. Target was far outside of MPRF range, so it fails (max MPRF range is/should be 25-30 miles or so). So the bug is that the radar is using the instantenous PRF to acquire STT instead of the PRF the target was detected on. For now, a workaround is avoiding INTL or waiting until the radar is in the PRF the target was detected on then pressing the TDC.

I'm not sure why this is in wishlist instead of bugs but it's reported.

Reported, please don't forget a track next time.

That's not normal, do you happen to have a track? Even if it's just 20 minutes sped up flying in a circle and it shows the issue, it would do the job.

Could you post a track or steps to reproduce please? I've been flying a while in IFA and couldn't get it to happen.

Manual is incorrect, ingame is correct.

This one is already fixed internally.

TXA DEGD is related to a selected JDAM having an incomplete alignment, is that what's going on?

Actually, it's user error. I didn't notice, but in your track you released the parking brake. The parking brake must be set during INS alignment.

Thanks, I've reported it. For the time being until it's fixed, if you run into this situation, you can try to perform a GPS alignment by placing the INS switch in IFA and leaving it there (I just tried it in your track and that works).

It was improved, but not totally fixed. The bricks can cause trails in certain scenarios at high ageout settings and (it seems) high LOS rates: This still doesn't happen in all scenarios though as you've noticed and still needs work.

Indeed, I reported this a while ago

Thanks, I just reported this last night.

Thanks, it's known - FRZ is still getting tweaks.

GPS is unavailable if the mission date is set before 1986 or the Hornet is in redfor. The second one can be bypassed with the "unrestricted satnav" option in the editor. So for most cases, you'll have GPS. One quick way to check is to put the INS switch in NAV after your INS is aligned. If you get a P/INS advisory then GPS is available and you should move the switch to IFA.

Hi all, We have introduced some fixes and improvements to the Hornet's INS modeling in the 2.5.6.53756 Open Beta. Here's an overview: Previously, in scenarios where GPS is not available, it was necessary to perform a fix (such as TACAN) to complete INS alignment. This is no longer the case - initial alignment position in GND alignment mode is provided by the position of waypoint 0 instead of GPS. Normally, waypoint 0 coincides with the aircraft's initial position at mission start, but it may be edited in the HSI/DATA subpage as necessary prior to alignment. In CV alignment mode, initial position is provided automatically via RF (CV SINS) or manually by the pilot (CV MAN). Previously, INS alignment was not complete after 0.5 OK status was displayed in the HSI, and it was necessary to wait a little longer. This has been fixed: 0.5 OK status now indicates a complete and successful alignment. Alignment times have been tweaked: GND and CV alignment take around 8 minutes now. Stored heading option has been introduced, which reduces alignment time to about 90 seconds. GPS alignment has been introduced which takes around 10 minutes and can be performed on the ground and in flight. The stored heading alignment option can now be selected in the HSI when the INS switch is in the GND or CV position. As mentioned above, it reduces alignment time from about 8 minutes to about 90 seconds. GPS alignment has been introduced. When GPS is available and INS quality is less than 0.5 OK, GPS alignment can be performed by placing in the INS switch in the IFA position and observing the HSI indicates IFA GPS and a countdown. This type of alignment takes about 10 minutes. If the INS switch is moved to the NAV position without a complete alignment (ie status less than 0.5 OK), a crossed out ALGN advisory will be displayed in the left DDI. POS/AINS (GPS aided INS) position keeping mode has been introduced. If GPS is available, once alignment is complete, the INS switch should be moved to and kept in the IFA position as per the normal startup checklist. This enables POS/AINS mode which can be verified in the top left corner in the HSI. In POS/AINS mode, GPS is used in conjunction with INS to provide the position of the aircraft. If GPS is not available, the INS switch should be moved to and kept in the NAV position. If the INS switch is placed in the IFA position before INS alignment is complete, in-flight alignment mode will be entered. IFA GPS (with GPS available) or IFA RDR (with GPS not available) will be displayed in the HSI. In the first case, once alignment is complete, the IFA GPS legend will disappear and POS/AINS mode will be entered automatically. In the second case, once alignment is complete the INS switch should be moved back to the NAV position. If GPS is available and the INS switch is in the NAV position, a P/INS advisory will be displayed. This notifies the pilot that GPS is available but it is not being used to augment the INS because the INS switch is in the NAV position, and that it should be moved to the IFA position to enable POS/AINS mode.

This one has been reported already, but thanks

Reported, thanks

It is fixed internally.

It was fixed but apparently it's broken again, so reported as a regression

Purely out of curiosity, what made you guys change your minds? Earlier on it was stated it'd have the Lantirn. I don't mind one way or another, just curious why it was cut if you're down to sharing