Mr. Wilson

How to disable pedal trim? all helicopters have this item in special settings, but I didn’t see it in Apache

ясно, спасибо.

какой имбой оказывается является возможность отстрела одной ловушки по нажатию кнопки) Как вообще народ умудряется падать постоянно летая с такими преимуществами, не понимаю )))

очевидно для увеличения количества факелов в отстреле, что позволит в "сегодняшних условиях этой игры" повысить шансы в борьбе с тепловыми ракетами как не странно)

@PilotMi8 Здравствуйте, подскажите пожалуйста можно ли на 24ом добавить одиночный отстрел ловушек по нажатию кнопки (по мимо программ)? Я допускаю возможность того, что в то время в тех реалиях могло этого не быть, но для сегодняшних условий этой игры это "маленькая поблажка" крайне не обходимая вещь, спасибо

Every test for me, even without maneuvers, shows that the CZ button moves the TGP in any case at all flight altitudes... if you watch this track and you see that negative trend again CZ2.trk

What values are considered normal? the problem is that before with a value of zero there was normal work

Everything related to points and focusing of TGP on them is broken now... playing at low altitudes with TOS bombing is not possible at all.

In the last patch, it was written about fixing problems with the CBU97 bombs not hitting, but there are still problems, as you can see on the track, the bombs chronically fly over the target. The tests were carried out at different heights and with different modes of pitching, about 50 drops (before the track) were carried out and for the accuracy of the hit, you always had to aim at the place in front of the target... PS: CBU105 works absolutely fine and hits the target in all cases. TRACK file: https://drive.google.com/file/d/1qMgQ6riHPk4o_x7WLiWx3pFL7KnyTa1M/view?usp=sharing

Pressing the button next to the CZ function causes the point to be shifted, moreover, in different aircraft maneuvers, the point shift can sometimes change in a very bad way... Initially, the point in the editor is ideally located in the center of the object. This problem also applies to operational points. CZ.trk

yes this is not a bug but a problem, as well as a status error in the system list.

The AGM-154A bombs have been released for a very long time since then in the list of aircraft systems they are painted green as if they are ready, but this is not so... At the moment, the CNTL settings page is still blocked, because of this it is not possible to edit the canister opening height parameter, Is it possible to fix this in the next patch? Or fix its status from green to blue so this system is not ready. PS: Оn the hornet, changing opening height was available from the very beginning. 154.trk

Yes, you are right, it seems that the properties appear in other bombing modes as well, but I have not seen this problem reported before

When using the CBU97 bomb in toss mode, the bomb release point is incorrectly calculated... CBU105 in the same conditions does everything correctly and an accurate hit occurs. I also want to note that it is this method of bombing that is most relevant at low altitudes, so I would like to have the correct resolution for dropping a bomb in such conditions. CBU97.trk

Thank you very much I will try this tomorrow

I sometimes face the problem of disabling the helmet-mounted targeting system when I press a lot of commands on HOTAS, can someone tell me what I press that causes such a side effect?

It's good now to understand from the developers in their version of the game the same or not

Сould you write how much your data differs from my data from the tests? Are there any problems already identified in the course of the research?

@BIGNEWY I created a new track file much more abbreviated to make it easier for you to research... The track file is based on 2 test cases: CASE 1 - Fighter h=1 000 ft / Target h=10 000 ft CASE 2 - Fighter h=10 000 ft / Target h=20 000 ft In the first test case, we see an extremely small target detection distance and the second test case was chosen to show the delay between target detection distance and target lock distance. The delay between target detection distance and target lock distance is present in all test cases and also in all situations when you are trying to lock the target.. For example, in the second test case, I managed to press the TMS forward button 4 times before the radar took it to the lock. It is worth noting that there is no such behavior of the radar for any aircraft in dcs I want to summarize everything that I wrote earlier, I see two problems: - extreme reduction in the radar detection distance at low flight altitudes of an attacking aircraft - delay between target detection distance and target lock distance server-20220731-015954.trk

Ok I will make a track with a few test cases to make it as short as possible, your data is very different from mine ?

Yes, this is a detailed bug report that shows what is between Detection range and Lock range. Also there is a strong drop in the detection range at low altitude of the attacking aircraft The track file was very large and because of this I did not publish it, because earlier you made a remark to me that large files do not need to be published because the team does not have time to devote so much to analysis... To do this, I will most likely need to create a separate track file that will be much smaller...

18.06.22 I've done radar tests, task of the test is to determine the dependence of the detection and lock range on the altitude of the target. 24.07.22 re-testing was carried out related to the last patch in order to understand how the radar has changed again, it should be noted that all tests were carried out under the same conditions. 18.06.22 Test conditions: The two jets converge face to face at different altitudes. Attack aircraft F16 target aircraft also F16. FCR mode - RWS (SAM). Result: CASE 1 -- Fighter h=1 000 ft / Target h=1 000 ft / Detection range=13 nm / Lock=11.6 nm CASE 2 -- Fighter h=1 000 ft / Target h=5 000 ft / Detection range=14.2 nm / Lock=11.6 nm CASE 3 -- Fighter h=1 000 ft / Target h=10 000 ft / Detection range=14.4 nm / Lock=12.3 nm CASE 4 -- Fighter h=1 000 ft / Target h=20 000 ft / Detection range=13.7 nm / Lock=11.3 nm CASE 5 -- Fighter h=1 000 ft / Target h=30 000 ft / Detection range=13.2 nm / Lock=11.8 nm CASE 6 -- Fighter h=30 000 ft / Target h=1 000 ft / Detection range=26.5 nm / Lock=22.7 nm CASE 7 -- Fighter h=20 000 ft / Target h=1 000 ft / Detection range=26.7 nm / Lock=23 nm CASE 8 -- Fighter h=10 000 ft / Target h=1 000 ft / Detection range=27.8 nm / Lock=23.6 nm CASE 9 -- Fighter h=5 000 ft / Target h=1 000 ft / Detection range=27.1 nm / Lock=22.6 nm CASE 10 - Fighter h=20 000 ft / Target h=20 000 ft / Detection range=41.8 nm / Lock=35.7 nm CASE 11 - Fighter h=10 000 ft / Target h=20 000 ft / Detection range=37.65 nm / Lock=32.3 nm CASE 12 - Fighter h=20 000 ft / Target h=10 000 ft / Detection range=27.85 nm / Lock=23.6 nm CASE 13 - Fighter h=20 000 ft / Target h=30 000 ft / Detection range=38.5 nm / Lock=32.5 nm CASE 14 - Fighter h=30 000 ft / Target h=20 000 ft / Detection range=27.1 nm / Lock=23.2 nm CASE 15 - Fighter h=5 000 ft / Target h=20 000 ft / Detection range=37 nm / Lock=31 nm CASE 16 - Fighter h=20 000 ft / Target h=5 000 ft / Detection range=27.92 nm / Lock=23.2 nm 24.07.22 Test conditions: The two jets converge face to face at different altitudes. Attack aircraft F16 target aircraft also F16. FCR mode - RWS (SAM). Result: CASE 1 -- Fighter h=1 000 ft / Target h=1 000 ft / Detection range=14.33 nm / Lock=13.5 nm CASE 2 -- Fighter h=1 000 ft / Target h=5 000 ft / Detection range=14.35 nm / Lock=13.3 nm CASE 3 -- Fighter h=1 000 ft / Target h=10 000 ft / Detection range=14.35 nm / Lock=13.3 nm CASE 4 -- Fighter h=1 000 ft / Target h=20 000 ft / Detection range=14.63 nm / Lock=13.8 nm CASE 5 -- Fighter h=1 000 ft / Target h=30 000 ft / Detection range=13.22 nm / Lock=12.7 nm CASE 6 -- Fighter h=30 000 ft / Target h=1 000 ft / Detection range=27.23 nm / Lock=25.9 nm CASE 7 -- Fighter h=10 000 ft / Target h=1 000 ft / Detection range=27.69 nm / Lock=26.3 nm CASE 8 -- Fighter h=5 000 ft / Target h=1 000 ft / Detection range=27.76 nm / Lock=26.3 nm CASE 9 -- Fighter h=20 000 ft / Target h=20 000 ft / Detection range=41.85 nm / Lock=39.2 nm CASE 10 - Fighter h=10 000 ft / Target h=20 000 ft / Detection range=38.66 nm / Lock=36 nm CASE 11 - Fighter h=20 000 ft / Target h=10 000 ft / Detection range=27.38 nm / Lock=25.8 nm CASE 12 - Fighter h=20 000 ft / Target h=30 000 ft / Detection range=38.31 nm / Lock=36.7 nm CASE 13 - Fighter h=30 000 ft / Target h=20 000 ft / Detection range=27.84 nm / Lock=26.4 nm CASE 14 - Fighter h=5 000 ft / Target h=20 000 ft / Detection range=38.16 nm / Lock=36.6 nm CASE 15 - Fighter h=20 000 ft / Target h=5 000 ft / Detection range=27.91 nm / Lock=26.5 nm As you can see, after the patch, the situation has become somewhat better but in all cases at all altitudes we see a delay between Detection and Lock range, Why ? we did not have such an effect before and on other jets there is no such effect either... And also very confusing losses in the detection range in CASES 1-5... I believe this is the effect of wave reflection from the ground, but why does it break the detection range so much? perhaps there is an error here?

@BIGNEWY @NineLine in this topic AGM154A and are marked in green, that is, they are considered ready, but in fact at the moment their settings page does not work. Is it possible to fix this or update the status of this weapon in the list so that it can be seen that it is not ready? Thanks

okay, thanks