84-Simba

If I can add something to the bug situation : M02 : Enable GRCV on AUX (radio 2) only. The guard receive does not work and PRI (radio 1), it is a Hornet bug that has been reported. AAR : AI aircrafts (leader or wingman) completely dry off the tankers when they refuel before you (except M01). Be mindful that you'll have to hit another tanker, refuel in first or just ignore the AAR completely.

Definitely. For some reason I reach the idle in the plane just before the levers reach the idle detent but the AB detent seems to be on the right spot. What bothered me was the enormous lag in the AB ; when I go full gate and I switch to the external view I can see the plane takes quite some time to pass every burner stages to reach the full burner, and the same when going down. Other than that, the lag between idle and MIL did not seem strange ; I know that the Hornet engines are very laggy. Would it be possible for you to share the amount of time the engines shound take to go from MIL to full burner just to check ? Or is that somewhat a sensible data ?

Allright. It is just my impression then, or maybe I used curves on my Orion 1 and I can't remember. But that comes from my side anyway. Thank you Regards

I hope you figured it out yet but something was missing I believe : DO NOT look directly at the basket Pick a reference cue on the tanker itself. I personnaly like to use the refuel pod for that, and depending on the plane, I fly to put it where I want. Always use your peripheral vision to control where the probe and the basket are ; maybe a quick flash eye control. With practice you'll know your visual cue and you'll be able to fly much more smoother. Just remember to not fly by looking directly at the basket

Hi there ! Has the engine lag been tweaked lately on the Hornet ? I find the transition from MIL to fullburner quite long - 5+ sec (and the other way down also). Is there maybe an official duration or timing I could check ? I just switched from a Winwing Orion 1 to 2. I think everything is calibrated and the AB detent is right where it needs to be. I'm not using any curve (and I can't remember if I had some on the Orion 1) Thx guys.

I would agree for the TDC priority ''bug'' ... I can't see why the pod would stop tracking. But ... I'm not sure for the Mav. When you switch from tgp DDI to Mav DDI and uncage, the system will handoff the position of the target from the tgp to the Mav and its seeker will snap to that position. But during that process, the target will move and I'm not sure the system can continuously handoff the position to have a tracking. The way I see it, the mav seeker will look at the position the tgp was looking when you initiated the handoff and then you have make the mav seeker track the target on his own. So, your mav seeker will end-up behind the moving target anyway. Don't you think ?

Before the merge I don't think so, at least before the pods were good enough. That is why there are interception tactics and scenarios. Add to that, the visibility is poor in DCS in general. I don't think you can VID much earlier but you can actually see something coming way easier IRL. When I'm travelling by plane I'm always amused at how I can spot cars and details on the ground much easier at much higher altitudes than in DCS. Using the ''dots'' labels is a good compromise. It doesn't spoil too much but it really helps.

At least you did try, thank you for that. It was a limited description because it happened in a constant and widespread scenario (a mission from an official content ; you see the idea ?) I'm not fighting you on that, I strongly disagree on how you manage your customer support in general. I made my point and as I said in another post, I won't go further. Best regards.

As I said ... I advise to test that way because it is an official content and since it happens right at mission start, there is little room for the player to do something that induce the bug. And when I discussed that problem on the campaign section, all the numerous people impacted pointed out to a bug we all know very well because it has plagued the game for a loooong time now. You want infos to be supplied ''as you want'' but still, the bug is here. I would have assumed that trying another approach would be advised, but nevermind. ''On good tracks it is (fixed)" Well, good job then. Thank you very much.

I'm sure you guys work hard but it is constructive to let you know that those kind of bug is basically making the solo content unplayable. Feel the sens of urgency ... Did you even try what I described ? Maybe being constructive starts with trying to understand what the customer is reporting without automatically asking for a track. I won't argue on this in every post, don't worry. But if you guys continue to just ask for tracks without even looking at stuff I'll just not report and maybe just lose interest in the game in the long run ... Understand that you ask customers to waste time to redo something that is intended to fail and so, consume time in NOT enjoying the sim. The very least I would expect is ''sorry, can you post a track because I tried what you said and I cannot reproduce ?" I understand that it is time consuming on your end. Sorry but hey, that's the job and that is what I paid for ... That's all I have to say on that matter. I won't go further. Regards.

Litterally 3 answers above Mods, too long, too large, something this or that ... I feel that everytime we report something the automatic answer is ''track'' just to get it dismissed later and the bug report thrown under the carpet until someone else digs it out. I said ''just start Dominant Fury M5 and see''. Did you do it ?

The problem is that most of the time you'll end up saying that the track is too long. What I found interesting in pointing you out to an official campaign mission is that we are sure we have the same test base. I have no mods. In this particular case the AI is doing this right after its cat-launch so very little margin for the user to do anything that would create the problem. You spend a lot of time looking at bugs but we waste a lot of time being screwed up by bugs. So maybe when someone is pointing you to something you could first try what he's saying (or acknowledge you actually did) before just ask for a track. Thank you.

As I said, try the Mission 5 of Dominant Fury campaign ; the wingman is acting like that right after his launch. Tried 3 times in a row, even with a complete game restart between tries. Just a question though : You keep on asking for tracks. Are you suggesting a user input could induce this AI behaviour ?

Allright ! Thank you mate. I'm sorry that your hard work is plagued by bugs from the sim. Best regards

It has been acknowledged as a Hornet bug by ED Team

No it's not fixed, as I just said ...

Hey there. I discovered that now, AI Tomcats will spread their wings when they startup from cold on the carrier (did not tried on land though). And of course, if you are on the slot beside them, you get crushed and damaged. Try the Mission 6 of Dominant Fury. It is the second mission in a row I have to pass because bugs will kill the progression ; well, I cannot even finish my damn startup !!! Get your stuff together ED, you are killing the game !!

Hi ! In the beginning of mission 6, AI Tomcat is spreading his wings on its slot so it damages our Hornet. To be honest, with the bug on M5 this campaign is becoming unplayable. I know that's on ED side but it is killing the experience ...

Damn Blade has the perpetual stall syndrom again. @baltic_dragon, you may want to think about a failsafe for that particular problem because ED is missing the point almost everytime. One patch and it's fixed and the next one will re-introduce the issue.

Happened two times in a row today when flying Dominant Fury M5 ... so it blocks the progression. You guys really need to do something about this !!

Hi ! After trying the mission 2 of Dominant Fury I wanted to know why I did not get the distress call since I had the habit to put the PRI radio (radio 1) in GRCV. The reason is simple, it doesn't work on PRI, only on SEC (radio 2) You can use Dominant Fury mission 2 where there is a long dialogue with someone on guard to try different combinations and see by yourself. Thx.

Got it to work properly with Zulu time. Thx mate.

Well, got it. GRCV is not working on PRI but on SEC.

Damn I never thought about that !! I tried in Raven One for the Missing Man formation ToT. I stand corrected and will try it shortly. Thank you very much !

Try Dominant Fury Mission 3 and set the ToT on WP 6 ... and see how it doesn't work at all. I had to use the HSI timer and the clock to be over the target on time. I doubt that thing ever worked in the Hornet ...