Mr. Wilson

The task of the test is to determine in which modes the FCR transmits information to the HSD page (A2A mode) Test conditions: One jet scanning and designating air targets and the other observes the situation on HSD page. Target consists of two jets. Result: - In RWS SAM mode: attack aircraft after designate does not see the targets on HSD page; observer aircraft sees only one target. - In TWS mode: attack aircraft sees only one of two (from FCR) target on HSD page which is designated by the FCR; observer aircraft sees only one target. Before today's patch: - In RWS SAM mode: attack aircraft after designate sees the targets on HSD page; observer aircraft sees targets. - In TWS mode: attack aircraft sees all targets (from FCR) on HSD page without designate ; observer aircraft sees all targets too. As you can see, this is a very significant change, if in the previous version everything was configured correctly, now there is a big error in the work of the FSR connection with the HSD and Link 16. Track

Great offer) If my free time is enough, I will definitely do additional research ... But it would be nice that you write down this bug because it has been confirmed experimentally with evidence.

I am not an F16 pilot, I cannot prove) I find differences from the already made Jets and it is also not clear if all systems work, why should this one not work? Do you have documents confirming that it should not work from external power supply?

Test - creating a Mark point using the PVI-800 and I-251: 1 Case - creation of a point through the optics of the I-251 complex. The point is created successfully and in the right place. 2 Case - creating a point manually by entering the same coordinates in PVI-800. The point is created but in the wrong place, while it is not static and "creeps". In both cases coordinate values in PVI were the same, but the locations of the points in I-251 - different. In 1 and 2 case we are talking about the same target and the same coordinates but in 1 case test passed, in 2 case - no. https://drive.google.com/file/d/17nc0jeXwXUucNFuTZHCtB6IIBAkzJr8L/view?usp=sharing

Test conditions: -the plane is at the airfield with the engine off; -but with the electric power supply connected; -included power toggle switches to all systems. When connecting ground power at the airfield, the TGP does not work, at the same time, the AGM-65 missiles received power and worked normally. TGP starts working only when the engine is running... https://drive.google.com/file/d/17nc0jeXwXUucNFuTZHCtB6IIBAkzJr8L/view?usp=sharing

Thanks for the track and excuse me for the pause. I have already received a correct result of the radar and found several reasons that bothered me earlier, but I am waiting for the next patch before writing new reports

If we switch the radar to FTT mode while there is a page with mark-point on DED, pressing the TMS back command will reset the active sensor from FCR to HUD and also reset the FCR page on mfd and with the complete loss of the previous location... Is this the correct behavior or not?

The point that the radar generates does not coincide with the one that we see on the FCR page and TGP

I watched your track. But he doesn't show anything... You didn’t show the accuracy of the point, you didn’t even use the zoom, you didn’t use the weapon, you didn’t look into the TGP at the created point, you did not check the place where you put the point. I showed in my track that the radar creates points in the wrong places with a very large error

thanks for the track, I'll watch and write

I was mean CZ too )) sorry)

I pressed CZ but it didn't fix the situation

This test shows how the weapon misses the aiming point of the FCR. The distance of the error is very significant. Perhaps for the same reason, the mark-point is not being generated correctly... FCR EROR.trk

you can do it on your mission and see everything ...

The mark-point is not created in the place indicated by the radar, it is created with a very large error, it is very clearly visible on the track. FCR MARK EROR.trk

1) TMS UP not worked (a lot of cases of inability to capture the yellow contact) 2) Сhaotic mode switching EOM, PB, RUK (at some point what happened is not clear why) 3) Switching between targets TMS Left / Write not working (always) TRACK

On the HAD Page, all SAM contacts disappeared during the mission...TRACK FILE Yesterday the cursor disappeared on the HAD page, but i have not track of this situation

Definitely, the development team has much more tasks and issues that require urgent solutions... F16 is not in the active phase of development now, so you shouldn't constantly ask this, I'm sure F16 fans could also ask a lot about the timing of the implementation of systems... But now there is an urgent task of DCS 2.7 and you just need to wait until f16 will please all of us with new features and show its enemies new sharp fangs))))

Что в итоге? Получилось поменять резюк?

oh thanks i understood

Found some problems with the operation of the Harm missile: - HARM does not see "S" in HAS and POS mode (search mode is not important) - And also, as previously stated, the reset button really does not work Hopefully these cosmetic fixes will be included in tomorrow's patch...)) thanks server-20201222-131754.trk

I tested AIM120 missiles on an F16 aircraft (F-15/F18 this problem is not noticed): - If you lock the target after that off the radar, then it continues to guide the missile - but if you dropped the target lock he stops guiding the missile (doesn't matter radar off or on) The problem is that the radar, in any case, when stoped work should stop controlling missiles... radar bug.trk

Ok , thanks )

When switching the active sensor HMD to TGP and TGP to HMD and pressing the command "TDC depress", this causes the following problems: - TGP does not slave the HMD (sometimes yes sometimes no) - TGP does not stabilize at the point of the earth, that is, it slowly floats in some direction test.trk

Why does the brightness drop so dramatically when exporting displays to a second monitor? Earlier it was announced that the dependence of brightness on the environment was added, but why is it then not taken into account when exporting displays?