Tango3B

See, that´s my problem, too. I had it happen to me two or three times on Growling´s server when I was close to a bandit and selected dogfight mode to employ an Aim-120 from pretty close range. As I said it is a very rare occurance. After the engagement I was stuck in that mode which didn´t make any sense to me - just like you might have experienced it. And that´s about it. Currently I can´t contribute anything more helpful than that. I´ll also try to get something useful on that issue.

True. But as you know you can trim out the jet reasonably well and the OP seems to have problems even with the basics of doing that. So, all I'm saying is that the OP needs to put in a little more effort and practice a little more with the wheels to get a feeling for the jet and what works best for him. Training is key to success.

Yup, the trim hat isn't working correctly which is kind of sad. The only advice one can give to the OP is to go and practice using the those trim wheels. It is pretty inconvenient for sure but you will get a certain finesse after you practiced a little, I promise. Really nothing else you can do about it at the moment, I guess.

That´s a negative on your first question. The "NO RAD" dogfighting mode is not implemented yet. You will have to manually cycle the radar emission switch as desired which is let´s say a little inconvenient. Concerning you sometimes being stuck in EEGS mode. I had that happening, too. But it is a very rare occurance, though. I haven´t been able to recreate it so far and thus record a track or a short vid of it happening. If you have a track or by any chance made a video while it happened to you please upload it here as I strongly suspect this to be a bug. There a two ways to get out of this: either press ACM on your radar display and select CRM which puts you back in RWS or set the dogfight mode switch briefly to DOGFIGHT OVRD and then back to CTR position which does the same thing. That´s how I do it and it works for me 100%. Again, if you can provide a track or a vid go ahead and do it.

Right, and this is how it should work. So, there is no bug as the OP had initially suspected.

Thread should be renamed. It is just not true that the Aim-120 is useless right now. Support till active works most of the time without the missile going crazy. And it is certainly still able to deliver the kill if you use it right and this goes for PvP, also. There are other more severe problems related to the current implementation of ECM, though. These problems are potentially game breaking stuff. In the "weapon bugs" section you can find more details on what this is actually all about. Bringing more attention to the overall issue concerning that missile is a good thing, though. I fully appreciate that and I fully agree with the OP that we need a solution a.s.a.p. in the upcoming big patch.

I just had a quick look at the F-16. Nothing has changed in any perceptible way. The jet handles like before. It is most likely a placebo effect that you are experiencing and/or it is probably you becoming better at flying the aircraft.

This could be one possible quick fix solution. But I guess it would make more sense to change the missile tracking logic in the way that it switches between HoJ and STT tracking. For the time being it should fix our "little" problem and it should not be too hard to implement or alter this in the "missile code".

@ uboats: Man, you guys really fixed this? Jeeez, I cant say how grateful I am you guys did this. Just saw it was moved to the "fixed bugs section". Big thank you to you guys working so hard for us at DEKA. Uboats can you please elaborate a little on how the avionics behavior changed with that recent fix?

Yup. Something needs to be done to address this a.s.a.p. because on a certain very well known PvP server certain gentlemen in their Mirages are kind of "invulnerable", recently. I do understand that these gentlemen do take advantage of the current situation but it is certainly no fun anymore as more and more people use this "exploit". And it gets to a whole new level fighting Tomcats sometimes. I mean, I can handle it fighting these guys but the problem here is pretty obvious. The question remains, though how difficult it is for ED to address this "bug" in the quickest way possible as there might be more to it then we know...

Sadly, that is not implemented yet. LaBise is totally right. Currently, there are quite a few things missing like NCTR print readout and so on. But we will get there eventually...

Seems more like a feature to me because it has worked that way since DEKA released the JF-17. But you´re absolutely right, I also think that it is really incovenient the way it currently works. I am also one of those guys who like having the radar screen on the left MFD. I always wondered why one would design modern fighter jet avionic systems to be intentionally inconvenient to operate. Especially since the the JF-17 is really quite intuitive and easy to understand looking at most other systems. And you do not see this behavior using the F-16 or the F/A-18, for example. You want to have a display showing a certain function - there you go. You are free to configure your displays and they stay that way unless YOU change what you want to see on the corresponding MFD. I think it would be nice to have a special menu option to configure the MFD behavior if the current avionics behavior is really intentional. This is actually the only thing I don´t like about the JF-17. Can we please have a statement by a DEKA member if this behavior is by design?

@DoctorVixen Yeah, I will make a short vid this evening. Actually, I do fly on GS's Caucasus server, too. I'm that Viper81 guy, by the way. Infact, I did fly there yesterday evening and it worked quite well to say the least. I am just curious does "your" TWS also drop the lock when auto-scaling? "Mine" does not and keeps a stable lock unless the bandit isn't notching or in certain other unfavorable aspects for TWS which would then be normal, expected behavior. Just asking because I heard that a few guys on GS's server see the same behavior in TWS as in RWS-SAM when auto-scaling occurs which is strange. So, basically what I am asking you here is might that problem with your TWS lock have been aspect related like the target is maneuvering hard, is notching, you having bad closure rate and so on? Or did the target even break the LOS because you mentioned those guys low in the mountains? As I mentioned before be aware that TWS in the Viper has it's problems in that scenario. And that is correct behavior. TWS is by no means that glorious silver bullet that many guys want that mode to be. So, if you loosing lock in TWS is aspect related then you would need to go back RWS-SAM, lock the target in RWS and switch back to TWS. Basically, you would need to repeat that procedure every time.

@diegoepoimaria01 No, I won't give any more details on that issue. But if you read GGTharos post right below yours you might actually find what you are looking for. Concerning that "fatter" pylon type your describing I guess you mean the one with Raytheon's glorious ALE-50 off-board towed decoys? Pretty helpful little buddies and part of the legacy IDECM suite. And yes, you are right these count as expendables.

No Spartan, what you mean is the EF-18G Growler. The Growler carries it's dedicated jamming pods on the pylons. That is a totally different airplane, though. The Growler is a dedicated electronic warfare aircraft though it can perform several other roles pretty well. Our F/A-18C has the ECM equipment installed right behind the cockpit. Ever noticed those two horn-shaped antennas behind your canopy? These are for your ASPJ. And no, what we see when jamming is in progress is no radar mode that performs some kind of interference but a certain self-protection function of the radar when using your own onboard jammer. I will not go into detail with that and why that is but keep in mind that some jammers are actually so powerful that you would also jam your own radar when transmitting with your SPJ.

Yeah, you're still good to go with that workaround. Just tested it with the recent patch and the workaround is still applicable. Let me know if I should post a short YT vid to showcase these steps in case you've got any questions. Sadly, as I suspected, though the recent patch did not include the long awaited fix for this bug so we have to deal with this a little longer. I hope BN keeps us updated on the progress made by the team. Fingers crossed for the next patch, I guess.

This! And check that the backup matches the main instrument if you reset it in flight. Then you're good to go.

@DoctorVixen: Well, BN said they could reproduce the bug and will work on a fix. They obviously had other priorities in the past few patches, though and apparently it took their team some time to understand what caused this problem. Again, I have absolutely no doubt this will be addressed in one of the next patches. I wouldn't hold my breath for Wednesday, though. And yes, the process of actually fixing this major bug is indeed painfully slow considering how much of a problem this actually is when flying in a competitive environment. For the the time being please use the following workaround if you are not already doing so. Briefly lock the target in RWS (quicker target detection / less problems with target aspect) before RWS auto-scales and then immediately switch to TWS while keeping your target locked and see if TWS can hold the lock. If yes then continue the engagement in TWS if not then repeat until TWS is able to hold the lock. This DOES work and you won't constantly loose lock. You also don't need to STT your target. Again, this is a bit inconvenient but you'll get the desired result.

It has to be the vertical maneuver component that causes OP's problem. I see the same thing when flying maneuvers in excess of 9G. Then the backup attitude indicator tends to develop drift. Wouldn't say this is a bug. This is more like a feature, I guess.

Well, I just tested this against the M2000 & F-15 in PvP and the same thing happens. And I would absolutely agree with you on the jamming effects if I didn't know that in DCS jamming is modelled rather basic and unless this hasn't changed recently it shouldn't really have any effect on an Aim-120 fired from close range. And then there is HOJ, of course. I guess, I need to try to get some useful trackfiles to showcase...

Yesterday evening I flew some sorties on GS's Open Conflict server and I can confirm your observations. And I also think it is related to the AMRAAM/SD-10 updates that came with the recent patch and that this is not a Tomcat bug. I had a situation where I was flying an F-16 and I was 2.5nm behind a slow, non-maneuvering but jamming Tomcat and fired 3 Aim-120Cs at it. Every missile did really weird maneuvers and in the end they were unable to intercept the Tomcat. I was literally fuming. Later on, I had a similar situation with the JF-17/SD-10 combination. Same thing happened. I did not run into any problems using other missile types against Tomcats, though. So, I strongly suspect it has to do with something that got broken with the Aim-120's/SD-10's guidance/tracking logic last patch. Another recent observation is that "my" Aim-120Cs seem to have problems tracking targets or guiding to them properly. All shots were supported till active and in correct parameters but the hit rate is abysmal even against guys that don't know how to defend properly. I don't know if this is a server sided problem or a general AMRAAM bug, though.

Thanks man. I'm already glad that you still have that bug on your radar and have not already forgotten about it. Let´s hope for next year then. And above all, enjoy your well-deserved vacation.

Guys, I really hate having to revive this thread, AGAIN. This incerdibly annoying bug is sadly still present in the current DCS 2.5.6.59398 Open Beta. Meanwhile, we had three OB patches since it was confirmed by BN that their team of testers has been able to reproduce that bug. This is a major issue and a real p.i.t.a. in Pvp fights, guys. The radar scan centering is completely borked and needs fixing. Apparently nothing has been done so far. Can we please have an update on this by BN or 9L? Can we hope for the next OB patch?

It depends, though. If you are deeply into A/A then by all means go for the Viper. In my opinion there is currently nothing in DCS that beats the Viper in A/A. But the F-16C is very limited in A/G at the moment and clearly lacks the system depth of the Hornet at this point in time. So, if you are more of a multirole or A/G guy that wants to fly a fast jet and on top of that likes carrier ops then by all means go for the Hornet. It´s a jack of all trades, sort of. You can´t go wrong with the Hornet if you look for a rather "complete" and complex module. But I strongly advice you to get the Viper, too. At least think about getting it. It pays off in the long run. Plus it is a ton of fun to fly and feels like a real fighter when compared to the Hornet. There is also a third module I want to recommend to you. It is the JF-17. It is absolutely worth looking at and it can do everything the Hornet can except for carrier ops, of course. Choose wisely and have fun flying in DCS...

It is a bug. And it has already been reported. I heard there is already a fix for it that currently undergoes testing in the development branch so we should probably see a fix for this very soon.