Morskoul Posted October 23, 2022 Posted October 23, 2022 Hi, I guess this part is still in development, at least the link between sight and radar telemetry. So Aerges team is probably fully aware of that. I tried this very simple gun firing mission to try the 300-600 reticle config. Shells goes well above the target at 600m-1000m range with reticle confiug in 600m. Looks better to keep the reticle at 300m whatever the target distance is. Hope the attached files can help in any ways. Or maybe I am totally wrong in the way of using 300-600. In that case, an explanation would be welcomed. This module is great by the way. Thanks to the team. I cannot wait to see further improvments and the other variants F1CE_Gun_Test.trk F1CE_Canon_Tests.miz Tacview-20221023-172921-DCS-F1CE_Canon_Tests.zip.acmi 1
Flappie Posted November 16, 2022 Posted November 16, 2022 Hi. Does this thread answer your question? 1 ---
Morskoul Posted November 18, 2022 Author Posted November 18, 2022 Hi Flappie I saw the problem before 2.8. But I've understood from the 2.8 Changelog that the 600m canon mode was not functionnal yet (2.8.0.32066 Open Beta) : Optical Sight and radar: Implemented Optical Sight target range display (except gun 600 m fixed range option) on the heading/range scale. The behavior has already changed since now the 600m is selected only when the switch is kept pressed. I guess this will have to be checked when Aerges will consider this feature as done. This topic should then be tagged as WIP, I guess. (or closed and to be reopened if needed) Thanks 1
Solution Flappie Posted December 17, 2022 Solution Posted December 17, 2022 Hi. It seems changes were implemened in yesterday's update. 1 ---
Morskoul Posted December 22, 2022 Author Posted December 22, 2022 Hi Flappie Thanks for the update, I did not notice the F1 part when reading the changelog. I have done a quick test and now the reticle seems correct for shooting at 600m. 1
Recommended Posts