Santi871

It's a bug related to aligning on a moving carrier, I've already reported it a little while ago. I'm not sure how to fix it exactly if you it happens other than maybe trying a full realignments once in flight.

Moving carrier CV alignment produces invalid alignment

It's unrelated to the acq point cue. The L&S jumps to the #1 track on TWS entry even when it already existed before entering TWS. You may have not noticed but it's always been a bug.

I reported this quite a while ago. This bug was introduced together with TWS almost a year ago, it's not new.

Reported, thanks

All reported.

Currently the dot always shows inside the segmented diamond, even on the HUD. It shouldn't show if the TDC isn't assigned to the HUD/HMD.

Others is F/F and SURV. Donors is other PPLIs.

No worries. Will keep an eye out.

I have, several times. You press the MK# button and the designation still exists. The same happens when I do it. Undesignation only happens when you change waypoints, which is correct.

Your track doesn't show such behavior. The designation continues to exist after creating a markpoint. It further continues to exist if I take control and create more markpoints.

Any tracks? With a good INS alignment CCIP should work fine with or without GPS.

it's reported already

On a side note something that needs to be reported is that CCIP symbology should only be displayed if the TDC is assigned to the HUD.

As for the EW symbols, the refresh rate matches known footage that can be found on google/youtube/etc. For the MIDS symbols, the refresh rate is already reported.

Reported, thanks

The previous way was the incorrect one and it was corrected to be this way. They should always show upright.

Seems to be working correctly here. Make sure you remember to upgrade your TWS tracks to system tracks so you can cycle through them. You can do that individually by TMS fwd short over each, or if there are no system tracks you can upgrade every track on the FCR to a system track with TMS right short. Also, I've never heard of any automatic cycling feature when a missile is fired, do you have a source for that? viper-tws-stepping.trk

Reported

It is a bug.

Yes, because previously it would only enter TGT steering mode when pressing WPDSG and not when designating via other methods, which was wrong. Changing the waypoint causes undesignation. The only reason it didn't before with designations other than WPDSG is what I mentioned above.

It's not related to the FLIR. Changing waypoints undesignates, it's always been like that. The only thing that's changed is that FLIR designations correctly make it enter TGT steering mode.

Yeah, if FLIR is tracking it should create and drive the designation. I'll report it.

There should be a WIND option in the stores page which shows a wind table to manually enter winds for bombing calculations. I was mistaken to bring it up in this thread though, wind tables for bombing are unrelated. It's also possible to manually override the wind calculated by the INS IIRC. Steering cues being wind corrected like klarsnow said is something absolutely basic and it needs to be addressed. The INS is already "aware" of wind because of the velocity vector on the HUD and things like the heading vs track in the HSI. So correcting the steering cues to account for it shouldn't be a problem.

You cannot "unselect" WPDSG. Pressing WPDSG initializes the designation to the currently selected waypoint (or markpoint) position. That is all it does, it's not a mode or a state, it's just an action. You can then do as you please with the designation, including moving it around with the targeting pod or with other methods.