Morskoul

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.

In transonic and supersonic, trimming versus speed can be inverted due to aerodynamic effects usually known under the name of "Mach Tuck". I cannot say if the behavior is representative of the real Mirage F1, but it can be explained by the center of lift moving backward on the wing and/or a decreased efficiency of the horizontal stabilizer. It is very noticeable on the Mirage F1, I agree. I think the worst is between M0.9 and M1.2. I guess that if this is too far from the aircraft the flight model will be adjusted.

At which speed/Mach & altitude did you notice that?

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

Correct, this is part of flight tests done to caracterize aircraft stability and recovery capability. I am not qualified to say if the FM is realistic or not,but such behavior appears with the Aerges F1. Usually you will enter it at high altitude and pulling hard the stick in a turn (dynamic stall). You can see that one test is done at 45'000ft (when you can see the backseat stick moving on its own). It looks easier to recover in the video that the feeling I have in DCS (in fact it may depends if you quickly release the stick when it happens). And it is said "In some case the engine can stall and flameout". Right now, the stall almost always happen for me. That being said, the module is early access and the flight model changes with every release. I found the first F1 release very tolerant (you was able to pull whatever you want on the stick, the wings were stalling without entering any spin). The last time I tried was before 2.8 release.

On my side, I have checked twice : - If radar is in stby, I can lock a bandit but no symbology on the sight (fixed reticle and no yellow square on the bandit) - If radar is on, I can lock and have the gun reticle that use radar telemetry to help aiming (and the yellow square on the bandit) The radar should not emit in stby so we should not be able to lock at all. Despite that I also lost the gun reticle at one time and have to switch to magic+gun mode to recover it.

I had this problem if I start from cold (I only tried gun, no missile) starting from ground cold, but it seems to work (again only with guns, no missile) starting a mission already in flight. I did not spend more time on it yet, but I wonder if there would be a command to do in the cockpit I forgot. Did you try both from cold start and already initialized in flight?

Thanks, I tag this thread duplicate then. Hoping will at least get the info it is not functional yet, so we stop trying to have this working

Hi all, Based on the Aerges flight manual P 85 (§8.A.1 "Preselection Authorization (APS)") : the F1CE radar is able to do some kind of TWS. Did someone already manage to use this feature? I tried several times to activate APS button (keeping it pressed as it is unstable) and never manage to have the alidade going horizontal instead of vertical. This is not listed in WIP, but maybe it is ?

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

Hello, Did you remove the safety pin (pin with red tag "Remove before flight" near the bottom ejection handle, between your legs) ? Try by clicking on the ejection handle (over your head or between your leg. If it works then but not with the Ctrl-E, check your inputs settings.

@Flappie, same for me that will do the trick. Thanks! My "finger's muscle memory" finds the Ctl-E on my keyboard with the headset on. Never use the clickable handles to eject. But that means there is a feature in the quest2 that activates some control when looking at it? If yes, it may be something that could be desactivate in Quest2 configuration? I'm new with Quest2 (and DCS by the way).

I would also appreciate to have this big tank available, event if it is not realistic for spanish Mirage F1. I love the look of the F1 with this tank. So big and close to the ground, you think it will never take off! As big-foot, no urge for that. That could be a small bonus after the 4 versions release.

Thanks @Don Rudi!