Csgo GE oh yeah

It's going to take hours of searching through tacviews, but i'll do it just for you Missile was fired from 14 nm so quite close. I remember seeing 14 nails disappear, thinking "oh he did not fire" i can give chase.... Then 5 seconds later i get the RWR warning Because of this recent discussion where tomcat pilots were asking HB to make the phoenix go active on it's own, i figured maybe they had implemented it and was simply asking about it. The ability to set target size WAS mentioned very low key in a long list of changes, but in fact has enormous impact on how you must defend vs a tomcat from now on (you only get 2 or 3 seconds of RWR warning now, makes the phoenix WAY more dangerous) , so again i was just wondering if anything might also had changed regarding missile going pitbull on it's own.

In the meantime do some searching for the term 'sweet spot reverb G2' . There's some differing opinions about it, some say it's really small. Others say your eyes need to adjust. Others say that because of the high res, you notice the (small) sweetspot much more than with other lower res headsets. And some say that you need to get a bit lucky with the way the headset fits your head. As a G2 owner, i personally feel that : - Yes the sweetspot is small , and i think that is because of a combination of that it's more noticable because of the higher res, AND how the G2 fits on my face. *edited because triggered by grammar error.

I just asked two simple questions. I got an answer and that was that as far as i'm concerned. But then i'm met with insults , so you tell me who's not interested in any semblance of constructive discussion ?

ROFL , wow. You do realize that for every Tomcat there's at least x10 Vipers, AND x10 Hornets flying around yes ? If anything that graphic proves that the tomcat is doing extremely well in BVR. The only way you're going to lose a 1v1 BVR engagment in the tomcat is if you're unaware of the reach advantage, or if you're not afraid to get in range of the Viper/Hornet. Because the whole thing is, that you do not HAVE to get in range of the viper/hornet at all in the tomcat if you don't want to. You can safely attack them without ever putting yourself in any danger. At the worst case scenario it's a tie. Meaning if your enemy manages to defeat all of your 6 phoenixes. If he manages that, you are still way out of his reach so you can still simply turn cold and restock on missiles I'd still recommend the F16 though, it's more modern and there's still so much good stuff coming.

Well that really depends on what you call "minor bug" . I'm not going to list them all again because i'm not 'dead set' vs anything. I'm not biting.

Mine is also plugged into a cheap usb-hub, so i'm definitely going to try that.

It really depends on what's available and how big the jump in performance in gaming is. I really like upgrading my hardware, but i still have an intel 8700k , running 5,2 ghz , 24/7 . On average i probably upgrade CPU about every 2 years. Same for GPU (every new gen) , except the 2080 series i skipped that cause it sucked.

i remember now from a video i watched when i just got the module You do need a REALLY good track for that because it rarely happens. Thanks man !

No no, it's in TWS . The TDC will actually stick to a track but without me having bugged it.

Sometimes i seem to have switched to some 'auto lock' or something. My TDC will automatically 'stick' to a track , and then when i TMS-up only once, it will lock it in STT It appears to be some kind of memory function, because this only happens to a track i previously bugged and un-bugged. Anyone know what i mean ?

@Naquaii Forgive me being suspecious but there's been so many weird things around this missile and the F14. I honestly don't know anymore . It would be extremely weird if the -advanced- (amraam) 120 can't , but the non-advanced 54 could.

Never saw any DL info without an Awacs in the air in the F16/Hornet/Flaming cliffs modules . Maybe not a DCS issue indeed.

How come only the F14 has this bug if it's on ED's end ? I really do hope Heatblur will take an extra look because this is quite a major problem. (for all the other planes that is lol) p.s: Could you also test if there is a significant delay between phoenix go active and the other plane getting an RWR warning ? Also i understood that phoenix doesn't go active without a signal from plane, but it seems this is not the case ? @Coxy_99 @Naquaii

I have two questions : - There's quite some time between the missile appears to go active, and getting an RWR warning. What could cause the delay ? - Are we sure the 54 doesn't go active without a signal from aircraft radar at the moment ? I see F14's go cold , and then 5 seconds later the phoenix gives an RWR warning. (goes active) Has this been changed ? Missile goes active on it's own now ?

How does this only now come to daylight ??? I'm so confused It does explain a whole lot of tacviews where i actually thought the enemy had real time tacview on another screen or something >_<

So just to make it clear so i get it. The F14 RWR tells you exactly when a missile is launched even when the missile is not active yet ? And if so, how's this ED's fault if the F14 is the only aircraft that has this uhm ... bug. ?

sigh ...

No i think it's track width. Wheelbase is the distance between the front and rear axle.

Judging from the changelogs it seems multiplayer isn't of great concern to anyone at ED and third party devs.

bish please ... (edit* ok i quoted the wrong person)

You can do pretty cool drifting with an empty plane. With a full plane , you can do some pretty cool falling over. The back wheels are quite close together , not sure what the english word is but we call it 'spuhrweite' (track-width ?) is small so yeah it flips over very quicly when it's heavy with weights that hang besides the wheels. I do wish they would make the anti-skid function though. I don't mind the wobbly-ness, it seems accurate.

Not a heli guy but ... the ah64 ... I might actually get it. Slightly excited.

Has this always been the case ?

Well, this ECM blinking apparently has always been a problem. It is even why the FC3 aircraft have this 'warmup' thing. But only very recently this problem has resurfaced (Original thread spoke about F14 only, with AIM54 only misisle not affected) so it makes sense that this blinking ECM of F14 was only recently added/changed in the F14 ? Yes, the mirage has this also but you don't see it online a lot so it could have had blinking ECM since forever without really getting noticed . So i was just wondering, was this blinking ECM recently added in the F14 ? And if so, (also when it was added not recently) why not disable blinking for the time being just like the FC3 aircraft have been for years ? It would be a temporary solution but it's needed right now.

Did Heatblur not make the F14's ECM blink only very recently in an update ?