_SteelFalcon_

yes you can deselect classes on the HAD page. click on THRT and then disable classes. actively selected classes have a white background. by default all 11 classes are selected, which makes the search time pretty long. if all you look for is red sams, classes 1-3 are sufficient. class 4 for EWRs (which can no longer be targeted by the harm anyway) and class 5 for red ships. 6-11 are western systems and ships this does not affect the HARM HAS mode, so if you use HAS, deselecting every emitter that you dont want to look for on the WPN page speeds up the process there.

Without watching the track: did you press CZ after designating the mark point as your active steerpoint? You‘ll have to do this, else it keeps the slew delta alive that you created by moving the tgp from its previous SPI and designating the mark point

Also keep in mind, currently the f-16 doesnt synch time with gps. It‘s been reported already somewhere here. Example if the mission start is zulu 10:00am and the jet spawns cold, your clock will not run until it you have power. so if you power up 10 min after mission start, the clock will run 10 min behind. It will never synch. You will have to manually do so on the time DED page. that happens even with GPS active in missions.

The RWR seems to pick up Sams much faster than the HTS. it does take some time for stuff to show up on HAD, but you can speed it up by deactivating threat classes in the HAD threat page. the fewer you select, the faster it completes the search

You could add a curve to both radar slew axis. That‘s how i did it when I was using a TM Warthog

well, a short test showed this: 10 min time have passed from mission start. miz attached. Active pause, time accelerate was used. Default FLIR contrast, gain and level from left to right: 1. drove about 2 min, arrived and turned engine off. 2. Alert state red, engine is constantly on and in idle. he didn't move at all 3. alert state green. engine is off, cold 4. stationary, but shooting at a point for 10 min. 5. "Static" unit MG2.miz

No. In the description.lua of your skin, you have to rename the material name at the beginning of the line to F_16_Tank_370 instead of „Tank_370“ You do not have to rename the file itself with the texture. Only modify the description.lua lines accordingly

If it‘s a custom skin, make sure the tanks are named correctly. The naming in the lua file was changed recently:

litterally 2 posts ago. Issue is known and reported

Reported already

The IFF panel on the back left console works for SRS / LotAtc. The UFC IFF stuff isnt in (yet).

Rws -> bug guy 1, move cursor to guy 2, tms up on him too. Now swap primary target back and forth with tms right. if target gets within 5 nm, guy 2 is dropped and guy 1 will be STT‘d automatically

it seems that it is being looked at according to this post. The HAFU comment was false, yet the bug reporting false symbology on the HSD and FCR as described in my original post is still valid.

i think it's not fully there. it seems to work for aim9 but not for the 120

Virpil T50CM3 throttle and using the "FLAPS" lever axis for the radar elevation

track below. in TWS and RWS, HAFU is shown fine until the Radar generates a Track File. then it's all just white. upon bugging a track file, the HAFU reappears on the HSD but is still absent from the FCR. HAFU_Symbology.trk

As per title here's 2 screenshots to show this issue. after zooming out a certain amount, the numbers get replaced with 000 This also applies to default skins that come with the module, not just custom user made liveries

All i said was „make sure the mav is in PRE mode and i suggest doing it mid flight on a ground object.“ according to the bug linked in my first post, it doesnt even matter if you lock up the same object with tgp and mav to BSGT them. But then again, i dont suggest using wrong workflows cuz they eventually will be fixed and wont work anymore.

i think you misunderstood. watching your track, your maverick is clearly set to VIS mode. in this mode, the LOS is slaved to your TD Box in the HUD, and before designating a Target through the HUD, the TD Box is slaved to your FPM. As said before, for this to work you must be in PRE mode. then designate a Target with the Targeting Pod, Slew the Maverick to that SAME spot the TGP is looking, lock up the Target when in range (8nm or less) and when a solid lock is obtained (Crosshair narrow, shaking a little), press BSGT and wait until the BSGT text is no longer highlighted. only then you should undesignate the target, switch to the other mav station (MSL Step button or using the OSB buttons on the MFD) and repeat the steps above.

you shouldnt boresight them on very close objects, it'll never be spot on when you undesignate the target again. by the sounds of it, you seem to do the steps correctly, make sure the mav is in PRE mode and i suggest doing it mid flight on a ground object. you can also take off, then overfly the AF again and use any building you like to BSGT them. at the moment, it doesnt even matter if the mav is even looking remotely to where the TPOD is looking, according to this report:

Apparently the UNCAGE button. But ED needs evidence for that, hope they get some from somewhere, it'd make life a lot easier.

I think it was mentioned in a video of wags about Dual Target Track a while back. The manual isn‘t up to date as of now, but they stated they‘re working on it. So eventually it‘ll be in.

Are your flight members within 5nm? If so, a SAM contact closer than 5nm automatically becomes an STT track

There was a stable update yesterday, not openbeta. Also maybe check your URL, changes show correctly for me. https://www.digitalcombatsimulator.com/en/news/changelog/

Yup. All you got is the RWR and the Mk1 eyeballs