Jak525

One of the very early screenshots of the JDAMs posted by Wags actually showed this https://forums.eagle.ru/attachment.php?attachmentid=203512&d=1548943369 https://forums.eagle.ru/attachment.php?attachmentid=203511&d=1548943369 https://forums.eagle.ru/attachment.php?attachmentid=204781&d=1550594992

[W.I.P]FLIR FOV and Maverick FOV button Track attached. The FLIR FOV button, whenever the MAV DSPLY format is up, changes the FOV of the AGM-65F. I believe it should only function as such when TDC is assigned to the MAV DSPLY. As demonstrated in the track, this conflicts with the FLIR FOV function. Thanks! MAV and FLIR FOV button bug.miz.trk

Whenever the HARM is selected as the current A/G weapon, the HARM Sequencer button always cycles emitters (both Self Protect and Target of Opportunity modes, although I forgot to showcase TOO in the .trk I tested and it is the case as well). This proves a problem with using the FLIR, as even when TDC is assigned to the FLIR the button still behaves in this manner to cycle the emitters. I believe for TOO mode, the HARM Sequencer button should only act as such when TDC is assigned to the HARM Display format, like the Cage/Uncage button does for handoff. For SP mode, the devs hopefully have an answer... perhaps TDC should be able to be assigned to the EW format, or it will function so long as the TDC is not assigned to another display using the HARM Sequencer button (e.g. FLIR FOV, later on radar RAID mode). Track is attached. Thanks! Harm Sequencer FLIR FOV button bug.miz.trk

Track attached to this reply Cursor overing offboard-only track.miz.trk

D/L frequency is and will not be simulated per the latest update to the manual.

What he means is, on the RDR ATTK format, when hovering over a trackfile that is offboard-ONLY (for a F/F, bottom half of HAFU only; for PPLI or SURV, a full shape but a bit smaller and no small dot in the center), you don't get the altitude and Mach on either side, unlike for an onboard or onboard+offboard track.

Definitely get what you mean here but it seems like, now I guess this is subjective, this is sort of a common sense thing that one can reasonably assume is correct because of the fact the radar while in STT shows a HAFU which is supposed to be a universal symbol that is the same across the SA / RDR ATTK, so there is no reason, unless ED's info specifically states it, that it would change when going into STT on the radar format. Keep in mind on the SA format the MSI element remains for the HAFU even while in STT. You guys did the same for the STEP box going away when the cursor is moved on the SA, no? Said it wasn't in ED's information but it made sense (of course again whether or not something makes sense is subjective I suppose, I tried to make objective points above though). The reason it'd make sense to show on the radar page IMO is so you could quickly cursor over and see the altitude and then change the antenna elevation according so you can pick up that offboard trackfile with your own radar. Going to the SA is an extra step, having to switch TDC priority and whatnot.

Spotlight also doesn't acquire into STT and can be slewed. I agree. It seems odd you have to reference the SA for it.

I reported the fact MSI was NOT in STT a bit ago, it got marked not a bug, then in the next patch MSI is now in STT (with some inconsistency as part of a larger problem with trackfiles). Basically the patch added what we were told was not a bug just a bit before it came out, so I'm quite confused. Frankly I highly doubt the MSI indications go away in STT in the real system... just makes zero sense.

Page 220, Figure 127 HOTAS TDC Control Zones -- does not indicate the fact you can control the scan azimuth setting with TDC. Page 219/220 Weapon Select Switch -- still says "no function for this Early Access version" for AIM-7 and AIM-120. Page 220 Undesignated Button -- it's Undesignate, not Undesignated.

Ahh I see what you mean, Beam - although, I think it could work either way in the real aircraft (unless you're speaking from actual information); your description of onboard bricks and offboard HAFUs would still work, but I could see it being programmed IRL to not work that way. I assume what NineLine hears is based off ED's info though. Still, no MSI in STT seems exceptionally odd to me, and in the last patch it actually shows in STT (just only if you use AACQ).

I believe the command heading line on the HUD heading tape (the pipe or diamond thing for waypoint, TACAN, or TGT) should be wind corrected so as not to indicate the direct heading to the steerpoint but rather the correct heading as to be on a direct COURSE to it. In other words if the wind is coming from the right, your velocity vector is going to be offset to the left of the heading caret. Thus the command steering line should be corrected to the right so that when the caret lines up with it, the velocity vector is on a straight course for the steerpoint. Here is some proof: See how the TGT diamond and the heading caret are basically lined up? In DCS, the diamond on the heading tape would also be lined up in this instance because of the fact it is not wind corrected. Now see the velocity vector; it is offset to the left. Now look at the heading tape command steering diamond. It is offset to the right. If the pilot turned right a tad, this would place the heading caret over the heading diamond. This would put the actual aircraft heading to the right of the TGT abut the velocity vector headed straight for it. Thus, the command heading should be wind corrected. Thanks! (Image from: )

Pretty sure this is correct. MSI only works in RWS with LTWS on

I read that the HUD tape's steering line (for a TGT/TACAN/waypoint) should be wind-corrected. It isn't however in DCS. Does ED's information support this? I feel this'd make sense as with any wind the line becomes quite useless. You can line the velocity vector up with it, but there's quite a bit of distance between the VV and the heading tape.

Heard a CF-18 pilot say they could in a YouTube interview. Whether or not the computer outputs it to grey rather than green on the AMPCD, I don't know.

I'm just using the DCS settings to make my bindings. I use the Warthog stick. My Sensor Control Switch depress is bound to TMS Left.

Can confirm this happens for me too.

The FLIR TRK (ATRK/PTRK) is cycled whenever TDC is assigned to the FLIR. I believe it should only cycle when the Sensor Control Switch is bumped in its direction AFTER assigning TDC assignment. Track bug.miz.trk

Ah right. Not sure; potentially could be supposed to be able to cursor over and display the Mach / altitude for offboard only tracks.

It does when you cursor over the trackfile or designate it as the L&S or DT2.

I have done some further investigation and I've determined that the HAFU is uncolored/no MSI indication is shown when STT is obtained via TDC depress on the L&S or by an ACM mode. It does appear, which is how I believe it should, when acquired into STT by Automatic Acquisition instead. I think the underlying issue here, which has been a thing for a bit, is that two 'trackfiles' exist: - One, with the MSI(bottom half etc) indication and all proper symbology (e.g. no rank for a friendly) - Another, without the MSI indication and no color in STT, as well as improper symbology (e.g. friendlies still ranked) The first one appears in the following cases: - SA format - RDR ATTK format for a trackfile not cursored over or designated as L&S or DT2 The second appears on the RDR ATTK when: - Designed as the L&S or DT2, or is cursored over, or is put into Single Target Track via TDC depress or ACM. What is odd is that when you acquire the trackfile into STT via AACQ, it appears as though graphically both of these trackfiles is displayed at the same time. You can see the uncolored one "peaking" from behind it and also the Mach / altitude readout is uncolored which seems to be part of the 'improper' trackfile.

Just curious what this "MEM" indication precisely means on the FLIR format when moving the camera.

Well yes, but it's missing a key factor: where the line of sight from the TGP to the ground ends. That differs whether or not a hill is there, or a house, etc. Hence, where the laser comes in to determine that.

You can designate a Target point even without the Laser Target Designator/Ranger on/armed. I am pretty sure this should be impossible... the targeting pod needs to briefly shoot a laser out to actually know how far the point out is that the FLIR is looking at. Hence the "Ranger" part of the LT Designator and Ranger.

In the new update, the HAFU is sometimes colored in STT (donor info and other donor tracks are also displayed, cool!) -- but not consistently. Track attached. EDIT: SEE 1ST REPLY. I've changed the name of this thread to cover the general problem with trackfiles but it doesn't seem to want to update on the main forum page. HAFU STT bug.miz.trk