Kula66

The SPQR guys put together a great composite video of this: NOTE: I did not change the target size switch from default.

Thanks IM. Is this something you were aware of previously? I ask because its been mentioned for quite a while; should we bring things like this to this forum for your attention? I was very surprised that all these 'major' issue being banded about, have little or no posts either here or in the ED/Missile bug forums. I guess most of them aren't issues at all, but lack of understanding.

The examples I was shown, after being told it happened 'all the time', were: * a perceived 54 reacquiring issue after being spoofed off target by chaff. The 54 appearing to weave towards the target ... but to me this again seems 'reasonable' in a tacview that was shown to me as a good example of an issue. * a 54 suddenly 'reacquiring' after going stupid at launch; but this seems to me to be the 54 flying straight after launch and then starting to track the target after a few seconds ... its easy to see because of the massive bent smoke trail, but some people claimed this was an issue. Is this expected behaviour? Nobody could show me an example from the current TACT comp ... examples using recent DCS builds in a stable environment. I know you have an established trusted testing team, but I'm also happy to assist in any testing if you need numbers.

Not something I've ever used (I only ever fly with Jester) ... is that a new 'feature'? I think it unlikely ... I've not had the issue before, and we were both at M1.0ish, all very standard stuff. I then jumped onto GS and couldn't reproduce it. I know this 'report' is not enough to go on, so I guess it was just one of those things.

Many thanks Cobra, I appreciate your comment and the position you're in. There seem to be so many people claiming its broken, but having asked for examples and reviewed a couple of them with even some simple analysis, shows 14/54 are acting in 'reasonable' way. (I'm obviously not a pilot, so I appreciate that my view of reasonable may be off). Having what I am sure are very frustrating issues on a busy PvP server, with dozens of players, some with very high ping is very different from a controlled PvP comp environment; but that's the way it is. I appreciate your efforts.

Nope, we were flying head on at each other (testing) ... and again, no, I never play with the radar elevation.

Just doing some testing in MP to confirm what bandits can see 54 launches, and something else cropped up: I was in a 14, with Jester at 40k' and I had a 16 on my nose, co-alt. I could see it using D/L, but not on RWS or TWS ... not at all, even when I could see it visually. I could see my 54s on radar as they launched and climbed away, sometimes as high as 70k'. I didn't alter the radar elevation, or anything else. I was flying a TACT mission; the only change was to allow external views and F10. Anyone else seeing this?

Yes, the careful wording was of note

Regarding 54s appearing on radar; is this as in RL or considered a bug?

I was thinking the same! Hats off to you gents.

14 has just been banned completely in the next big BVR tournament ... lots of Tomaters out there

For me, its not really a crash, more a freeze of the interface. I was hosting an MP mission and it 'froze' ... the other pilots could join ok and apparently, my aircraft was visible!

Just had Jester call out a missile that I'd just fired ... no other missiles in the air I've not noticed any performance hit flying over Cyprus compared to previous over other parts of Syria. I've certainly noticed the additional shaking behind the boat

Just wanted to add: this map is excellent, a really great effort, thanks!

I get systems failing or going out of alignment when I over-g, but your g meter doesn’t seem to show anything excessive. I lost my radar at the weekend, but that may have been 10+G ps1: not being a real pilot, I use FPM a lot more than I probably should

There was a post about it previously ... I still hear it in the front seat, still irritating.

Yes, mine froze again last night UPDATE: Just so it may help anyone, in MP, selected the 14, clicked FLY and it said WAITING ... although apparently, I was spawned on the pad!

Well, I appreciate your comment, and can understand your position.

If it is of any help, this (freezing on second mission load) was happening to me fairly frequently, and at BIGNEWY's suggestion, I renamed my 'Saved Game' DCs folder, allowed it to create a new one and copied in my missions and scripts directories and the problem hasn't reoccurred - not saying its fixed, but in a few days, it hasn't happened again.

This is extremely frustrating … 14 nerfed again in competitive play. Is this something HB recognise as an issue?

Fingers crossed ... thanks for your assistance Gents

I renamed the folder and just copied CONFIG across, ie. not scripts (I have Tacview, Viacom and a chair addin), etc and ran the same mission what felt like 10 times with no crashes ... not conclusive, and I'll keep trying.

Yes, this is loading a mission from the mission editor I think it was this mission ... I've had this issue since 2.7 release, otherwise very stable. jF-14B Missile defense.miz

Still an issue on my system (Win10, HP G1 VR, 32GB, M2, 3090) - load a mission, fly it, go to mission editor, fly again and 'WAITNG ...' dcs.log

TWS is very effective in the 14 ... just switch to TWS and position the target in the scan cone; let the WCS assign it a priority number and fire - works just fine. When cranking, just keep the target in the scan cone (TWS-A will automatically keep the target centred) until the countdown starts flashing - I regularly get hits out to 75 miles in competitive games. The only thing that I can't do is launch a second missiles at the same target ... not sure this is as its supposed to work.