Tango3B

Felixx75 you do not need datalink or any fancy stuff like that for this very feature to work. It actually just works like this: you lock a contact on your radar and thereby you STT the contact. Then you open your Comms menu and go to the AWACS/GCI menu item. There you would see an option called "Declare" which is only available if you have a locked contact present and then the AWACS/GCI "magically" interogates this contact for you (3rd party EID) and either declares it hostile or friendly. No fancy stuff involved. And it only works with that contact in STT lock. If you want to "Declare" another contatct you would have to STT this contact, too. Also, it is game related and not an actual part or an avionics funtion of the F1. Also, this is already available as a menu item in the Comms menu of the F/A-18 or the F-16 so we should theoretically be able to see this in our F1, too. Hope that clarifies, what that function does.

You´re my hero. First, you made the HUD readable and now this awesome mod. Great work, dude!

So, my understanding of the APS trigger function is, that you should basically hold down the said trigger like you would do to command an APC STT track, right? The difference for APS is that in this mode the alidade (TDC) should, as the manual cryptically says, transition to a horizontal position to indicate that it actually has achieved a lock while maintaining the ability to scan a certain volume of airspace. Apparently, the radar display should not change function and stay in the normal search display format. Ok, this never seems to happen, right? Right. Well, then the manual also cryptically mentions alleged mandatory conditions in the following way: "In this function, scanning ± 60° in 1 line is imposed. The target square is present but undergoes fluctuations due to the resetting carried out at each scan." Mmmkay...so, I tried all possible combinations in a 30°/60° degree scan combined with a 1L/4L scan while staying absolutely level and co-alt and nose on with the F1 to give the Cyrano IV perfect conditions. Nothing. I tried HA and 1C modes. Nothing. Maybe someone from the Aerges staff may try to explain how this mode is intended to work? Please?! Quick edit: I mentioned 1C mode. Personally, I see zero difference to HA mode. Can someone from Aerges please also explain the advantages/disadvantages of this very mode?

Is the APS mode (TWS) already implemented or is it one of the radar modes still being worked on? If it is already implemented has anybody been able to get it to lock something? And if so how do you manage to lock something in this mode? I just can´t get it to work. Sorry if this has been asked before or if it has already been clarified that this mode isn´t working, yet but I am old and probably also stupid so I really need your help here, guys...

Exactly, you need to lock or bug your target before this very menu item is available in the Comms menu. I think, this is also how it works in the F-16 which is kind of logical because otherwise there wouldn´t be something to interrogate for the 3rd party source, right? Anyway, we really need this...

Dear Aerges team, since we have no IFF interogator in the F1CE, I would kindly ask you to provide us with the "Declare" option in the AWACS/GCI Comms menu. That would be tremendously helpful in SP/MP and it shouldn´t be too difficult to add that menu item, right? If it is unclear what "Declare" does, that would be the 3rd party EID way of interrogation via AWACS or GCI. We need that...like really!

Aerges, you did it. The F1 is superb. The flight model is truly excellent and the same applies to the simulation of the Atar 9K-50 engine. Flying this aircraft to the very extremes of its performance envelope reveals all the work which has gone in this module. Again, simply excellent. I love what you guys did, there and since this is just the early access version of the F1 the things to come will most likely only add more awesome stuff. Yes, this module is a winner.

And exactly this is my problem with the current implementation of the APG-68v5. These scenarios are simply illogical and against every form of radar theory which can be found in an academic context about newer radar systems. Since my last post got deleted for apparently quoting Hobel´s statement including that infamous document I still want to see ED´s white paper. We were promised to see how ED implements radar techology and how ED justifies these measures that currently affect the APG-68. I think at this point it would only be fair to have a better understanding of ED´s train of thought. I think there is no breach of any rule in this post and I want to politely ask for an ETA on the above mentioned white paper. Thanks.

Wait, that´s unfair, I wanted to have the first kill in the F1...! ;-D Anyway, one Backfire down in flames...

Awesome!!! Thank you, Aerges.

+1 for the manual

Ah, ok. I understand. Well, in this this case I am totally with you and hope for the best. Thank you for your quick clarification.

Uhm, you know that there was a Magic I (rear aspect) and a Magic II (all aspect), right? The latter is currently used by the M2k, so what exactly do you mean by your statement if I may ask politely? Is there any module (C101?!) that already uses the Magic I which I am not aware of?!

Dear Aerges Team, you made me very happy today. The Mirage F1 is, apart from the F-4, THE cold war module I always wanted to fly in DCS and now it is finally going to happen. I saw the F1 at an airshow back in the 80s when I still was a kid and I remember I was immediately amazed by its sleek and sexy appearance. And this holds true until today. The F1 has something to it which only the F-4 and the F-16 manage to awaken in me. Remember back in December ´21 when I said I expect the F1 to be released in July ´22? Well, apparently I was dead right. Guys, great work. This will be an instant purchase on release day. Oh, by the way: can you guys at Aerges already tell us something about the pricing for all the different F1 versions or aren´t you allowed to talk about it, yet?

Exactly. This seems to be a "thing" with the AI logic in SP sometimes but it is surely not a bug and the observed behavior is not a regular occurrence. Also, in PvP this problem does not exist when fighting against human players as far as my observation goes. So I can safely confirm the ALR has certainly no degraded performance as I can normally pick up Nails from F-14s which are still 150nm+ away from me.

With all due respect BN, this is not enough. The behavior described above was not there before the patch on the 28.04.2022 and the observed behavior was also reported and marked as a bug by at least one or two ED team members - and it clearly is a major bug. Saying we should wait for an explanation in the white paper, if there is any, is not really helpful in any way. Did you even read the above scenario I described? You just cannot leave us hanging in the loop with something which is so annoying and so wrong that I barely find the right words describing it. Thanks.

Ok, so the problem with the APG-68v5 not being able to bug targets flying lower or higher than 4000 ft below or above your own altitude and ranges of greater than 24nm under certain conditions, although the APG-68 has already generated a valid track file still exists in DCS Open beta 2.7.15.25026 as described in the following post from 28.04.2022: https://forum.dcs.world/topic/299740-dcs-f-16cm-apg-68v5-look-down-issues-and-also-weird-aim-120c-behavior/ I attached a track file and a vid of what happened on my radar while I was trying to bug two contacts coming in hot at roughly 40 nm. The first bandit is nearly co-alt with me, the second bandit is several thousand feet below me at the start of the engagement. A track file was created more or less immediately on the first bandit flying at co-alt at roughly 40 nm. The second bandit who now climbs slowly up to my altitude stays undetected until around 30nm when he is at roughly 15k feet. My own altitude at that moment is 25490 ft. So we have 10490 ft altitude difference, my scan settings on the APG are set to cover both bandits as you can clearly see on my radar display. Also, a track file is created rather quickly by the APG-68 on the second bandit, so in theory I should be able to bug him, right? Well, no! Only when the second bandit climbs up to 22k ft and 23.7 nm range am I able to bug him on my radar. Is there any explanation for this weird behavior because the same behavior is true for a bandit flying higher than you? So, let´s imagine a scenario on a well-known PvP where, say an F-15 is hot on you, flying at 42k ft and you are at 30k ft. The range is 40 nm. You know what happens? Right. You catch an AMRAAM right to the face because you can´t bug your bandit and shoot back until the exact same conditions are met. Is this fun? Hell, no! This is a major bug, guys. Easily reproduceable for everyone, I guess. Also, easy to see. So again, why is this? I mean, I know there is a white paper coming on the APG-68v5 but seriously, I am really curious as to what the scientific justification behind reducing the engagement range of a very capable Gen4 multi-purpose radar with good A/A capabilities to basically crude and illogical behavior might be and also why there has not been any hotfix on this stuff, yet. And please don´t get me wrong, I do not want to argue about the maximum detection capability of the DCS APG-68v5, so let´s keep the topic solely on the behavior described above. Link to vid: https://youtu.be/HmkQlR87sJk F-16CM APG-68v5 look-up or down problem still exists.trk

Capoti, is, in your opinion, what you are seeing the issue kind or like the issue described in my thread: "DCS F-16CM APG-68v5 look-down issues and also weird AIM-120C behavior?" If so, we can merge these two threads because there is an issue. **And yes, by any means please try to include a track and/or a vid backing your bug in the future. Only then is ED able to take care of your issue and/or understand what you are tying to tell them. This is really crucial...** No, it didn´t. And 9L, please have a look at the "APG-68v5 look down issue" thread which I started yesterday and you´ll see what he means. This is actually a very seriuos and sadly a very big issue. If you guys need someone who can provide you with his professional opinion than feel free to contact me. I try to help where I can but this is definitely not right. I have a Typhoon background, by the way and "some" F-16 experience. Just so you know.

@Koozie Thanks for the information, Koozie. One thing to add to my list of potential bugs mentioned above and this is directly related to the AIM-120C5 performance. This might have to go into the weapon bugs section but I don´t know if this is only related to shots from the F-16. Ok, so in one of the above YT clips you can see me using a certain tactic shooting an AIM-120C5 at my target at quite a large angle off (35-40 degrees off my nose) from around 5.5nm, thereby gaining a significant angular advantage for any evasive maneuver on my part. It´s a legitimate and working tactic, by the way. I actually tried this several times, now and noticed that with our new patch most AIM-120Cs fired under these conditions are not even guiding on the bugged target whereas before the patch this tactic normally worked. I am currently not at home so I can´t provide you guys with any TACVIEW files but there is definitely something wrong with the guidance logic as the missile just seems to fly straight out without doing anything. Sure, the missile should have some room to maneuver but 5.5 nm is certainly enough (2 - 2.5nm should be enough) to recieve DL information and make the turn to the target. Can you please also look into these guidance problems and forward this stuff to the team? I´m home on Monday and then I will try to add some TACVIEW files to show what I mean. @Koozie **EDIT** Also, at 3:08 in YT clip 1 when I switch to DGFT mode my AIM-9X should go to AUTO COOL. It stays at WARM, though. New, potential bug. Please check.

Unfortunately, after today's patch 2.7.12.23362, various problems with the APG-68v5 and the ability to lock onto low-flying targets (a MiG-29 in this case) have also surfaced. The ability to lock onto a low-flying target with your own aircraft at medium altitude appears to be reduced by almost 50% (target cannot be bugged before roughly 20nm range). Weird thing is you can clearly see the radar already "sees" the target at a much greater range but you simply cannot not bug the target until you are at around 20nm range. Apologies for my language, but this is just plain ridiculous, as it has been explained numerous times and amply enough why this should not be the case when looking at a modern pulse-doppler radar like the APG-68v5 or the APG-73 and instead of an improvement in this patch, we're apparently getting an even more drastic increase of the infamous "look-down penalty". In addition, the AMRAAM apparently now also seems to have serious problems hitting low-flying targets under otherwise largely ideal parameters. This can also be seen quite clearly in my track and the attached video. I'm afraid that, despite a really good approach in this patch, there is still a lot of work to be done here. Please take a look at my attached track and I have also attached two YT clips to showcase the problem more graphically. vid 1 https://youtu.be/65NsUQyCKe0 vid 2 https://youtu.be/LH2UXreWmQA F-16CM APG-68v5 look-down problem.trk

Hey, Andrei. I know you were only forwarding the message that you have heard from the official side but the point is that the factor which reduces the detection performance is currently way too big. Modern A/A radars do all have certain means of reducing unwanted clutter and/or noise by very capable digital data processing in a way that it barely impacts your detection range. This applies not only to look-up scenarios but also to look-down scenarios. And please do not get me wrong here, I do not argue that there are "some" negative effects on the ability to detect a target under these conditions but in no way in this world was a hard-coded reduction of your ability to detect a target with an APG-73 (or an APG-68v5) in a look-up scneario ok which only yields you a detection range of barely above 15nm. This is simply not justifiable and much too drastic as we do not fly a MiG-23 with some kind of ancient analog signal processors here. It is very nice to see that ED is already aware and will adress this problem in a future patch. Let´s see how this turns out, then.

I think we can safely assume that a potential release is imminent as soon as we see the radar in action. So, as soon as Redkite releases a video of it on his channel, we know it probably won't be long...

Ok, so I did some tests, myself. I purposely use a similar radar setup as Grimes323 and I ran into the exact same thing. From low altitude I am not able to lock my targets in excess of 20nm range. 15nm seems more likely. This cannot be right as we are in a look-up scenario here and the radar should have absolutely zero problems finding the targets. Also, we are talking about a very capable modern radar, so... *EDIT: HI PRF shows the same results in the low altitude/look-up scenario.* My second test is a a verification of INTL PRF working correctly at co-altitude with the same radar setup. It is able to detect the targets in excess of 40nm in this scenario which is about right, I would say. So, the problem is clearly the low altitude/look-up scenario. There seems to be some kind of "penalty" for flying down low which drastically reduces radar detection range in an extremely exaggregated way which is simply not right in this scenario. @BIGNEWY @NineLine Can you please forward this to the team to have a look into this? Also, please move the thread to the bug section. F-18C APG-73 look-up problem low alt.trk F-18C APG-73 look-up problem co-alt example.trk

Apart from the fact that you really should be using HI PRF on a hot target I cannot see any mistake on your part, actually. Also, you correctly adjusted the radar elevation setting and as your targets are already close to 20nm it should not pose any problem to the radar to detect the targets in Interleaved PRF. Very strange, indeed. Gripes, can you please post a track of your mission here, so that other guys can try it out? Most importantly, this would surely help ED to see what possibly went wrong...

Glad I could help you. And yes, I also find "force trim up" to be working just fine with these settings. The Apache now feels quite stable during transition to hover and landing and I think I do finally get there with my skills. Man, I can tell you I was also struggling really hard with that part of flying until I got my head around the proper settings as I was literally all over the place before...