Hulkbust44

That's not true. ATFLIR and LITENING actually do have different logic. First off, terminology. The LITENING has INR, AREA and point track. ATFLIR has INR, SCENE, and AUTO track. Area can not be slewed, but SCENE can. Each time SCENE stabilizes after slewing, the target designation is updated. If you were to TDC depress with an AREA track I'm pretty sure the offset cursor would appear. AREA, SCENE, PTK, and AUTO should update the designation automatically. TDC depress is needed to designate a point in INR. I also believe that in DCS if you were updating the designation via a different source and castle to the FLIR, you would need to depress for FLIR to be the driving sensor. ATFLIR in point track will continue to extrapolate the target position when masked. ATFLIR zoom and FOV is all on the radar elevation control.

No, that would be incorrect. There is a lot in the jet, but almost every system is missing a good chunk of it's significant functions. If every system that has already been worked on was full and correct, I'd say the aircraft would be 85% complete compared to real life based on available documentation. To those out of the loop, the module looks and feels decently close to completion. This is partially because it is already the most capable DCS module by far. People can find bugs, but very few can identify the incorrect implementations. Just throwing that out there first. Until you know what's missing the incompleteness is not apparent and will not hinder your enjoyment in anyway. There are things that are more difficult than they should be, but to you that's just how it's done in DCS. I love flying this module, I have thousands and thousands of hours of virtual time logged. Incredibly enjoyable and to be honest by the time you are proficient in the aircraft most issues would be fixed. There's a ton to learn, and it's still a fantastic module.

That last bit should be default anyway.

I notice FLBIT is boxed, any chance the advisories are residual from the BIT? Best I got until we get a trk. Edit: missed Swift's comment

And you claim to be an Archangel that's not from around here. You have a history of being delusional and wrong, as you are here.

No issue here. Track file is being remembered by the computer and can still be designated in that time. As you turn around the radar is able to extrapolate the track as it picks up the target again.

No an A/A track as AZ/EL is exclusive to A/A, but the "HAFUs" it uses are A/G...

I know issues are supposed to be kept separate, but a few of these things go hand in hand. On the AZ/EL FLIR sublevel, first off A/G L16 ID symbology is being used for the MSI trackfiles. AZ/EL it the only format that is only available in A/A yet for some reason its the only time we see the A/G symbology. TDC depress over the MIDS only trackfile elicits no change, yet additional data is supplied when TUC'd. (L+s should be set to that trackfile) The issue here is that the FLIR LOS cue will not track to the trackfile without radar contribution. With radar contribution, the cursor can be depressed at the edge of a trackfile and the FLIR LOS cue will surround the HAFU and track it without L+S. SLAVE on the right of the display will be boxed. With a trackfile lacking radar contribution, FLIR LOS will not SLAVE. See track below. AZELHEX.trk

I've known that this feature is supposed to exist for a while, but until now I hadn't found a useable, detailed enough description of its function. The official name is the acquisition gate. As SCS toward the FLIR format is held, the auto track box expands until an object can be tracked, or until SCS is released and a track is commanded. BIGNEWY, PM sent.

With TDC over a feet dry track and RECEE event mark pressed to command SA EXP, the position of the tracks(s) on the map are clearly wrong as they are being displayed well over the water. (In the trk I take a little while to set up my example) EDIT: After further testing it appears that the EXPand map view is centering around the player aircrafts position at 5nm and not the TUC's. EXP_BUG.trk

I noticed that tracks identified properly on the AZ/EL aren't being ID'd on the SA format when TUC'd. The AZ/EL will tell me LINK-16 SU-27, but that same track on the SA is UNK. Earlier I had an A-10 take off infront of me. On the HMD I could see the friendly A-10, but when I went to the SA it was UNK. acftid.trk

Circa 2005*

In ODS the most employed weapon was the CBU-99/100 mk20 rockeye iirc.

Eh, I was decently close lol.

I'm going to say automatic power control

Shouldn't happen. If you just jettisoned something, that's why. It's a new bug.

ED allocates resources *elsewhere* Heatblur who made the Tomcat has less projects to work on and can make the work to a higher level of completion. (And quality) So the answer to when? Is eventually...

It's telling you the the witdth in altitude of the radar scan at the cursors range. In this case, at the cursor range part of your scan is looking at the ground. The radar isn't this one thin beam that is perfectly directed. At closer range you do need the antenna at some extremes, those altitude numbers are only part of the picture. It really helps to know the actual antenna elevation angle. In the attack format it is hidden by declutter 2 by default.

Are you talking raw performance numbers? In BFM the Hornet should win, but it's a close one. The Hornet has better at turning in every situation, better BVR weapons, and better avionics. The MiG can Fly faster and higher but has poor fuel capacity. In DCS BFM vs AI you should destroy a MiG.

Cage/uncage. TDC depress was incorrect logic and has since been fixed.

No, there is no barrage jamming for the ASPJ. It is a range and angular deception jammer utilizing range gate pull off, con-scan deception and other techniques.

Once active the AMRAAM will just search for the first thing it sees, your aircraft no longer has *any* input.

This is true, however the F-15Es in desert storm claimed that they could identify an any aircraft on the ground and determine if it had fuel tanks... at a range of 30 nm. It was a very powerful tool in the desert supposedly.

There is no real correct behavior here. The wings must be spread completely before being locked otherwise you will destroy the mechanisms. Unfortunately this is not modeled in DCS, but the bug you described feels like a decent alternative...

It should work, whole point... What band? Mobius708