777coletrain

I agree, but I think until that stuff is implemented it would be nice to have the clock actually be useful.

If this is the case, wouldn't it make more sense for the clock to just always show the correct time instead of simulating what it would do on start up and just always being wrong? Seems like showing the correct time when its not supposed to is the lesser evil of the two options.

This is correct, here is an image from a HUD tape video on youtube where it indicates 0 kts. When he takes off the correct wind is shown null

I agree @Hummingbird, I just wanted to make a bug report so they knew. It's a pain to throw around the pattern now so the sooner it is fixed the better

I'm fine with this if it is accurate to the actual jet, although I have noticed the rudder is very strange when below 300kts and there is a lot of adverse yaw when rolling

A high AoA roll when going less than 300kias will pull the airplane out of the slip stream. I'm able to do this rolling to the left and the right. F16 Spin 6 08 22.trk

The tadpole in the HUD seems to just sit directly above the waypoint when the waypoint is within its range of motion. I'm linking a closed thread where Frederf went into the movement of the tadpole in way more detail than I would be able to. He has pictures of what it does in the real jet, I'm going to include one of the pictures here and one from the track I'm including as an example. F16 Tadpole 6 06 22.trk

+1 here also

List 6 will show ground speed if you really need it.

This would be an incredible addition to DCS

The manual states "Positioning the ROLL switch to STRG SEL allows the autopilot to steer the aircraft to the selected steerpoint using roll commands. The roll command does not exceed a 30-degree bank angle or a 20-degree/second roll rate." The important part from this section is "to the selected steerpoint". When an aircraft needs to go to a specific point on the ground (a steerpoint), crosswind will needed to be accounted for. This is because if the pilot (or autopilot) doesn't and points the nose of the aircraft at whatever they are flying to, the aircraft will home to that point. This is common in NDB navigation. This is not preferable because it is inefficient and will require constant heading changes as the aircraft is constantly being pushed sideways. Currently this is what the STRG SEL switch does in the F-16. If the pilot (or autopilot) was to actually fly "to the selected steerpoint" they would account for wind by setting a wind correction angel. I could go into how that is calculated and done in other aircraft, but effectively for fighter jets it would be accomplished by putting the flight path marker vertically above the steerpoint. By doing this the pilot (or autopilot) would account for any crosswind that exists and would actually fly "to the selected steerpoint". I will include some pictures to illustrate what I've been talking about below. The bottom depiction is what STRG SEL is doing.

The F16 bomb fall line does not account for wind when using JDAMs. It is modeled correctly for all other types of munition, including WCMDs, but for JDAMS specifically the bomb fall line doesn’t account for wind. This causes the aircraft to home to the selected steerpoint instead of tracking to it like it should. F16 Bomb fall line 2 11 22.trk

Correct, which is why when "steering select" is being used the flight path marker should end up over the steer point. When there is a crosswind the aircraft currently doesn't actually go to the selected steer point because it simply flies the heading to it instead of the track.

Hey, this is actually correct (its a confusing labeling scheme). More info can be found in this thread.

Has there been any update with this?

so... There is a naval Phantom being made

I haven't seen anything however the term 'bearing' is used correctly in other parts of the manual. I wouldn't be surprised if they do mean it in that way, however I think ED would need more evidence to change this to match the HUD tapes.

The bottom picture is set up like that although I can try to find another instance of it

Yeah the wind is what is causing this to happen. My confusion is from the top and bottom pictures being different. The top (DCS) is doing exactly what the manual says it should do, but the bottom (actual F-16) is not following what the manual says. It appears that in the actual airplane the "bearing" is based off of the flight path marker instead of the actual bearing of the aircraft.

I've also noticed this, adding a track file. F16 HMD Align 1 19 22.trk

Sort of, the steering cue seems to be pointing relative to different points though. In the top picture it is pointing right because the steerpoint is to the right of the nose of the aircraft (like stated in the manual) while in the bottom picture it is slightly left because steerpoint is slightly left of the flight path marker.

That thread is about the lateral displacement of the tadpole, I'm talking about the direction the line is pointing from the tadpole.

I recently noticed something strange with the tadpole in the F-16. In HUD tapes the line coming from the tadpole seems to direct the FPM to the selected steer point while in DCS it directs the nose of the aircraft. The manuals state that the line indicates the bearing to the point. So the tadpole in DCS would be indicating exactly what the manual says where the real aircraft doesn't. Is this something that changed with block numbers or is the manual saying bearing in relation to the FPM? It could also just be me not understanding something, either way I'm including some pictures to show what I'm talking about.

I've talked to a few people that have flown the F-16 and they've said that the flight path marker should point at the steer point. Please just ask the SMEs about this.

I agree, I'm currently trying to find any documentation on how this mode should work. However I find it hard to believe that it would just point the nose since that wouldn't actually bring you to the steering point when there is a lot of wind. If I'm wrong so be it but I would be surprised that the F-16 could input a GPS coordinate but not fly directly to that point.