VKing

Issue still present in OB 2.8.3.38090, both ST and MT.

Yeah, it's this. When the CPG selects NVS, it makes the TADS unavailable as a sight. You can get almost the same effect by setting the TADS as the sight and slaving it to GHS.

My addendum earlier in the thread appears to have been caused by some slack in my joystick (the precision of the centering required before alt hold activates might be a seperate issue), and should be ignored for this bug.

What the preconditions mean is that as long as you're flying at less than 40 knots without holding the force trim or moving the pedals from the trimmed position, not yawing, and attitude hold mode isn't enabled, your aircraft will be in heading hold mode. It wouldn't be correct to say the modes change without the pilot's knowledge, since the pilot puts the helicopter into the different modes by what state he puts the helicopter into. E.g. if you accelerate to more than 40 knots, you know you aren't in Heading Hold any more but in Turn Coordination. It might be easier to think of it not as a mode you enter, but the default state your helicopter is in for a given set of conditions. E: Regarding the condition of time elapsed since heading hold was disengaged, I believe this means that if any of the other conditions are broken and then returned to, there will be a grace period before the system engages again, possibly to prevent oscillations or that kind of thing.

If a track designated TUC on the SA page, either by moving the cursor over the track or using the Step function, and then the SA page is no longer displayed, e.g. by using SCS to show the HSI page, the HMD icon for the track will freeze in space and no longer follow the track. When the SA page is shown again, the HMD icon will snap back to the track. This only affects the TUC. All other tracks shown on the HMD behave normally when the SA page is not visible. Version 2.8.2.35759 Open Beta. F-18_SA_DL_TUC_HMD-bug.trk

Changing those settings currently does nothing. Improvements to Link 16 functionality and setup have been announced, but exactly what it will be and when they'll get to it has not.

I already had problems distinguishing '5', '6', and '8', because of the font, and the symbols being smaller hasn't helped.

I can believe that's how the weapon is supposed to work after the sensor turns on. You would like the missile to continue towards the target if it turns on again, but this is contingent on the missile being close enough that it's actually flying at the target instead of still lofting. The problem seems to be that the sensor turns on almost immediately upon launch instead of when it reaches the target area it's supposed to search in. So instead of looking at a small area for a specific radar, it searches basically half the map.

Yup, I found that. I meant any documentation on the fuzes themselves.

Is there any information on the new bomb fuzes anywhere? Trying to figure out what they do and how they're different.

Same behaviour in 2.8.2.35632.

Not quite sure if it's the same issue since I haven't seen the oscillations, but altitude hold does indeed not work. Pushing either BALT or RALT hold does not bar the OSBs and gives a master caution. This seems like it was a controller problem, and should not affect the original issue.

The F-16's lat/lon format of DDD'MM.mmm has a resolution of 1-2 metres (depending on latitude), so plenty good enough to put JDAMs on things.

Is the RWR font correct? Is it really that hard to distinguish an 8 and a 6 in reality?

I agree. I guess my point was, there should be a "No Launch Warning" notification for the NASAMS system, and perhaps a note that the F-16 won't even see it by default. Although, it might be a special case since it's the only system that uses active missiles, so unlike the others with no launch warning, there is *some* warning before you die.

They can't in DCS. In reality? Interesting question. The missiles are just regular AMRAAMs fired from regular LAU-129 launch rails, so I don't know why they couldn't be fired mad dog-style.

One comment on the NASAMS: It's labeled as both a search and track radar, but the MPQ-64 never tracks (the F-16 RWR doesn't even show it unless the show search radars button is pressed), and as such it will also never give a launch warning.

If the HARM is fired in PB (or EOM in the F-16), the expected behaviour is that the HARM will loft and turn towards the selected steerpoint or target point, then dive towards the target area and start looking for a radar of the selected type to home in on. What appears to be happening, is that the HARM seeker activates immediately upon launch. If it doesn't see a radar, or if the radar is active the entire time the HARM is in flight, it will fly the correct flight path. However, if the radar turns off at any point during the flight, the missile will go dumb and forget its target position, and glide straight past it. In the first two tracks, which is the same scenario in the F-16 and F-18, to show there is no issue with a particular aircraft, there is one SA-6 radar at steerpoint 2. First one HARM is fired against a non-existent SA-2, and one against the SA-6. When the first HARM is about to strike the SA-6, a third is fired, also against the SA-6. Observe that the first two missiles loft and dive towards the target area as expected, even though there is no SA-2 radar for the first missile to spot. The third missile fails to initiate its dive, and as such will completely miss the target area. In the third track, the radar respawns (placeholder for a radar deactivating and reactivating), and since the second HARM does not follow the correct flight path, it misses the second radar since it is outside of the HARM's FOV when it activates. The fourth track demonstrates that the HARM seeker activates far too early. Even in EOM mode, which is supposedly the most restrictive in terms of precision required of the target location, the missile turns to seek onto a radar more than 20 nmi away from its given target position. HARM_EOM_Tracking_bug_F-18.trk HARM_EOM_Tracking_bug_F-16.trk HARM_EOM_Tracking_bug_F-16_radar-reactivates.trk HARM_EOM_Tracking_bug_F-16_activation-range.trk

At night there's no real reason not to have the TADS video up on the IHADSS, imo, but during the day it's distracting and not very usable.

With the HMD selected as the sight, press the BRT down button on the TADS seven or eight times. This will turn the video overlay on the HMD off when you switch to the TADS.

An anecdote from a friend of mine who's flown the A-10C for the USAF is that the Maverick is pretty terrible at seeing and locking things outside of 4-5 nmi. And outside those ranges the shaking of the rocket motor igniting and the missile falling off the rail is apparently able to sometimes cause the seeker to lose track.

I think it's how it's supposed to work, and it's not a flaw. The time delta is just a way to change the TOS on all the steerpoints at once. It's not, AFAIK, supposed to be an actual time difference with regards to some reference time. In other words, there exists no "active delta", just the current TOS for the steerpoints.

Both pilot and CPG have foot buttons for ICS and radio that they use when they're not the one flying.

Yes, it shows up when the ASE detects radars. It's possible it doesn't show up if the ASE autopage option is turned off, but I haven't tested that.

I had the same issue. When in free fire mode, George would more or less single fire the gun at wildly different angles. I know tacview recordings aren't the most accurate, but this one shows what was happening. https://i.imgur.com/i8eNN28.gifv