_SteelFalcon_

it does drift, but dunno how much tbh

Did a quick test, air spawn, took screenshot, then powered mav down, powered them back on and took another screenshot. now guess which is which I might add: in OPs screeenshot distance shows 3 nm and no WPN cross is anywhere on the MFD. is it possible the mav lost track of the target due to mav seeker limit and was trying constantly to stay on "target"? Mav_Screen.trk

That‘s done on the SMS page, not the WPN page. Make sure you have the correct weapon selected (sms page right row of OSB buttons, 2nd from the top button i believe)

Currently L16 Symbology is displayed wrong when wingmen lock up Air targets, then switch to AG mode without dropping the lock first. Even turning away from the bandit outside of radar gimbal keeps the shot lines on the HSD and the last known position of the bandit is stuck in place. Mission setup: 2 client F-16 1 AWACS 1 Hostile Hostile is set to dump altitude from 20k ft down to 5k ft right over bullseye (so you have a visual reference where that should happen). Flow: Wingman locks up bandit at 20k before the bandit reaches the Bullseye and drops down. once lock is established, I observe the HSD and FCR with the DL symbology and the shot line of my wingman. My wingman then switches to A-G mode without dropping lock. he turns away so the bandit is out of his radar FOV. Result: Shot line remains to a target at 20k ft. I no longer get updated DL info about this bandit, despite awacs being present. i cannot find the bandit below 20k ft despite the radar elevation being correct. i can visually see the bandit within 15 nm... setting the MIDS filter to NONE didnt get the bandit to show up, so i have to switch to DGFT mode to get a lock. My wingman changes to A-A mode again now and suddenly i get correct DL info again. Thanks @Moonshine for testing See tracks attached from both player aircraft and the MIZ + Tacview Link-16_WingmanTrack2.trk L16_Lead_track.trk Tacview-20221120-132953-DCS-Test_L16.zip.acmi Test_L16.miz

Did you power the mav on? Go to the SMS page, power on the mav and wait til they are warmed up. You wont get video on the wpn page until they are warmed up

If you shoot 2 mavs at 2 targets very close together, it does sometimes happen. If targets are so close to eachother, i usually wait about 3 sec before launching another mav, just to avoid this situation

I use this icp and all the rotary axis work perfectly fine out of the box. Axis options are there in dcs to bind them correctly too

yep in a certain manual from 1997 it says 10nm for all acm modes. but the m3 from 7 years later contains a specific topic adressing this with increased range to 40nm for the BORE setting

good catch! hope this gets adjusted.

Yep, only the SPIN option for the CBU105 doesnt do anything. for the CBU103 it actually changes, not so for the 105. BA can be changed on all CBUs

See track attached. Creating a TGP MARK when HARM is selected weapon sets the mark on the previous Waypoint instead of at the TGP point track location. Doing the same thing when in NAV and TGP in A-G setting, the TGP MARK is set in the correct place where the TGP is in point track. TGP_MARK.trk

With todays OB, the dynamic numbers were fixed for LOD 0 and 1, which is nice. But not 2, 3 and 4. will they eventually be adjusted too? it does look goofy taking screenshots of formations where the furthest planes show 000... and it is well within distance where one can read the number.

i think currently the only thing not showing when on SAFE is the Gun pipper in STRF mode. the rest seems all there

If you scrolled a LITTLE bit down... :

What‘s your MFD display resolution? Could that affect it?

CCRP_3.trkCCRP_2.trkCCRP_1.trk CCRP_1 -> Level flight. Pressed WPN release as soon as the pull up cue lines appeared and held it down until the DLZ cue reached the bottom of the DLZ and the Bomb fall line crossed my FPM at the same time. looks fine as far as i can tell. CCRP_2 -> level flight, pressed WPN release AFTER the Pull up cues disappeared. Same as above, Bomb fall line crossed my FPM as the DLZ cue reached the bottom of the DLZ. CCRP_3 -> Pull up delivery with default bomb release parameters. pulled up as soon as the circle started flashing, constant 4.0g to 45° and right then, the Bomb fall line crossed my FPM as it should. Note, for the toss i startet at 10k ft, the others i flew at 15k ft it works best to toss them if you're fast.

@TobiasA you brought me on an idea and indeed, if MIDS is off, setting the filter to "none" or "tgts" does not remove raw hits (so technically correct) but as soon as i turn the mids knob "on", bricks disappear... see mids_v2.trk attached Then i ran the test again, this time i deleted the AWACS in the Mission editor and flew with MIDS knob to ON, and the tracks didnt get removed (technically correct again). (mids_v3_no_awacs.trk) Seems like the bug only occurs if DL info is being fed into the cockpit from some DL donor aircraft. if you either manually turn DL off (MIDS knob OFF) OR no DL donor is present, the MIDS filter dont affect raw hits. but turning it on, suddenly the filter removes the raw hits too, and not just the DL info. @BIGNEWY maybe this helps narrowing the bug down. i would add it there, but cant, since it's locked. mids_v3_no_awacs.trk mids_v2.trk

As mentioned, the MIDS filters technically only affect datalink info and as such, to see any effect, you would need at least an awacs in your mission to see DL symbology on your FCR. currently, not only does DL info get removed with the 2 mentioned MIDS filters, but also raw radar bricks. keybinds as skywalker mentioned. iff in (short press) cycles the filter options. Iff out (short press) toggles from selected filter to none and back

Your tests are faulty. Dont look at stuff at 100+nm. The DL symbology getting removed is correct. BUT it also removes raw radar hits/bricks (NOT DL!) which it should not, even with MIDS to „TGTS“ or „NONE“, according to a very often referenced document about a certain tape. The function is well documented there. the OP says RWS shows no more contacts, which means raw radar data disappears. He‘s not talking about DL symbology, which disappears anyway when the mids filter is set to NONE or TGTS. i suggest you take the time and watch the tracks in my linked bug report.

Maybe test again then. Cuz this report was done using 2.8 latest ob and it can reliably be reproduced and has as such already been reported.

Are you sure you didnt accidentally switch the MIDS filter on the FCR to TGTS or NONE? currently there is a bug that removes raw radar hits when either of those filters are active

Nah dont worry, i figured it wont be seen in a post with that tag already. The function of the mids filters can be found in some of the frequently mentioned documents about the viper and none of the descriptions there say that raw radar data should be removed. They only affect DL information i got u

yup, can be recreated. and it doesnt matter if you have the HTS equipped or not. it's simply the HARM. if HARM is the selected weapon, stuff's weird.

When the HARM is selected as weapon, the TGP does not move to the new SPI when the waypoint is being changed. it doesnt move with HARM in HAS nor in POS mode. EDIT: only after a CZ, the Pod jumps to the new STPT/SPI. but with the CBU87 the pod moves instantly. Switching to any other weapon (here a cbu87 set to CCRP), it does. changing back to the HARM, it doesnt. When HARM selected and steerpoint is changed, TGP stays fixed on previous STPT (1). The HSD SPI cross however is at the new STPT (2). BUT: when moving the Pod around STPT 1 and even entering point track, the SPI on the HSD still stays at STPT 2. It seems to work fine in NAV mode with TGP set to A-G, as demonstrated in the beginning of the first track. Tracks added. TGP SPI issue with HARM selected.trk TGP SPI issue with HARM selected_2.trk TGP SPI issue with HARM selected_3.trk