DoorMouse

https://www.twitch.tv/videos/1097188312 First the Rio crashed and had to restart - Meaning Jester didnt come back and all the aircraft systems were non-functional (which would be a super cool thing to solve) and then when she DID come back, the wing popped off (No we checked the tac view, nothing hit us). It happened the moment she fully loaded in - I presume some de-sync issue made the client think I just went a million miles an hour suddenly.

Yeah, I think that's the point. Most players play single player or no pvp and do not find these issues- But crucially, pvp is part of the game. If that community of players finds issues where the game or its modules aren't working properly then its reasonable for them to report it, and no less valid for them to do so. I dunno what your driving at. I'd say that the online multiplayer community probably finds and is the most vocal about bugs in the Open Beta track, which is working as intended - I'd not suggest discouraging people from reporting issues. The issue being: The Aim54 has a reproducible exploit in PVP and is the only missile capable of it, and the tomcat is the only aircraft with that missile -IE Reporting it on the Tomcat bugs forum. Iron mike already acknowledged the issue, and said it was unknown to them - So problem solved? Is that okay with you? The reality is that the Aim54 AWG-9 behavior exceeds the capabilities of the current API. They cant model it correctly, and clearly something between the Tomcat/ED missile handoff as it is implemented is giving the client and observers wildly different information- again, it is the only missile doing that.

This thread has lost the plot a bit. They acknowledged (in this thread) they had not seen/tested the High AOA PH Active issues, so that now is in their pipeline to investigate. Thats great, and this is the right place to bring that up. Its their module and you'd think they would have some interest in seeing it in DCS World Events, streams, etc... that does drive some sales- And a point of pride that its not considered by the larger community to be "Broken". So this is the right place to ask them to comment on that, IMO. As someone else pointed out - Asking for the RWR, Missile performance, or other things is not asking them to 'adapt to the competitive scene'. Its asking to have basic functionality be realistic and modeled correctly. Really missing the forest for the trees here And finally - In anything people put time into or are passionate about there will be a drive to be competitive. Is this ultra balanced e-sports like Overwatch or Rocket League? no... decidedly not. But PVP is more challenging than PVE, and then flying against random people in pubs who just got DCS today and barely know how to fly gets boring. Why cast shade on people who mutually want to play at a high level against each other? I think Iron Mike addressed the questions and acknowledged the issue being recognized. We've reached the point of diminishing returns on this thread- But the attitude of people saying "why are people trying to play an online game with each-other?" is pretty strange and surprising.

I mentioned it to Nineline and they asked if Heatblur was aware. You guys might want to coordinate.

Ive also noticed a LOT of phoenixes not ever going pitbull on a hold track, even if they should. Only since maybe the last patch or two.

This only effects the thrust as you retreat the throttle? But resets once you hit mil? Or does this also effect your AB thrust capabilities?

I have definitely noticed the copilots threshold for deciding to shoot at a target has been reduced. I was hovering a few feet from an enemy Sam site a couple days ago, and he wouldn't fire, but the door gunners would. It was very strange. He did however decide a bit later to try and hit something 1+ miles away in a treeline I couldn't even see.

Had it happen in my FIRST attempt to play today. Fresh DCS load and when I slotted in a Tomcat (A this time) it froze and hard crashed - no crash log was created. Happened again about 30 minutes later.

@IronMike I really appreciate you taking a look at this and your thoughtful responses. I'm surprised to hear this stuff wasn't 'on your radar' (sorry) but it is a huge relief to hear it has been acknowledged and is a high priority for the team. Its such a great module and an incredible effort to make the Tomcat what it is- It is frustrating for all parties. Really looking forward to seeing the new missile API implemented, and the next few patches. If you need testers, feedback, tracks, videos, or instructions on how to reproduce issues- Please reach out, there are a several dedicated tomcat players on our team who would love nothing more than to help.

Blue F14A E-TF[113]Doormouse/E-TF[109]Whiterabbit Supercarrier

So I am unconvinced it is an "exploit" But basically Target Size Small will often give you very little, or sometimes no RWR. I think if you fly hot into a TGT SMALL phoenix, it hits you before your client can be told it has pitbulled sometimes. You should always get some warning, but I also think a lot of people dont understand that they are flying into a mach 3 missile at 700 knots, so you only get 1-2 seconds before it hits you. The high AOA ACTIVE phoenix thing is real however. Essentially, if you fire a phoenix while pulling VERY HIGH (20+aoa) violently. The missile will on the CLIENT SHOOTER computer, correct and go to target. However on the CLIENT TARGET the missile looks like it is going off into space, crashing into the ground, etc.... And then you suddenly die. This is reliably reproducible. I have also seen this reacquiring/weaving behavior where the missile in TWS AND/OR PSTT will pourpose up and down and weave toward the target

had it three times tonight, every other time I tried to slot into a new tomcat it froze up in vr and windows had to kill the process

I happened to mention this to BigNewy when they were talking about the stable release, and that they had been focusing on crashes. He seemed unaware of it, and asked if HB had been made aware. The problem is it crashes un-gracefully so it doesnt kick a log/crash file out. But literally everyone with the tomcat (that I know) gets this multiple times a night, as of ~2 patches ago they introduced it.

I and all the tomcat players I know, have the same thing. It is very reproducible. Its so well known and an obvious crash I think most people just assumed it would be fixed - Sounds like its not even really widely reported. So I'll add my Go to multiplayer server Fly, get shot down, eject, land or otherwise end your flight re-slot into a tomcat and press "fly" Repeat this and eventually you will get it to completely lock up. It is only an issue in the tomcat.

Hey guys. Ive had a couple passing conversations with HB folks on here or Reddit and I know they are "aware" of the situation but normally I am told that its either A) the missile api or B) the folks at SATAL/TACT being crazy and that "All missiles suffer from the same problems" Ive also seen multiple people be able to 100% reproduce the missile desyncs by flying high AOA while PH active, but no one seems to acknowledge it or have responded that its actively being worked on. I'd love for a proper response to what is basically the entire module being banned from competitive play, which is incredibly disappointing. It would also be awesome for someone from Heatblur to be a liaison to the competitive scene Appreciate it- and thanks in advance

Doormouse F14 Thank you guys for putting on these events!

Was this included in the latest patch?

It actually should take a turn, in the sparrow it's called missile English bias and it kicks out with "English" off the wing because of some limitations turning on the seeker before it is clear of the aircraft. In the Phoenix, according to Naquail, it should slew the head towards the target and then upon launching try to zero out the seeker directly on that course, causing an immediate maneuver to target. So- it should do exactly that. Make a turn right off the aircraft up to the maximal gimbal limit of the missile seeker I'd suppose.

To be clear, what I'm saying and what the OP posted with a track is: 1) PSTT lock 2) ACM Cover DOWN/Unengaged 3) Phoenix fires down ADL with no English bias or course instructions 4) after some indeterminate but short distance/time the missile makes a high G maneuver towards the target 5)PSTT is maintained throughout the encounter (not that this matters other than proving there was a positive lock at launch that didn't drop just as the missile was fired) This happens frequently and is reproducible.

The issue the OP reported is that the missile often does not see the locked target when you fire, which would probably happen irl too... However in DCS there is a 10 mile hard coded limit to missile tracking according to Naquail... Which is probably responsible for the strange behavior Ok, now we are getting somewhere. So you are saying the missile SHOULD maneuver towards the PSTT track immediately and IS getting instructions on where to MANEUVER to... Not just slew the seeker head. Because what I am reporting and the OP is describing is that with an PSTT lock on a target the missile flies ADL... Does not maneuver, and then some time later (2-3miles) appears to make a hard turn to the target. It is not getting any instructions on "What direction to head out at"

The nuances of what I'm asking are being lost in text. This would be clear with a whiteboard and verbal communication, but I'll make a go at it. Boresight no track is clear, I was never unclear on that behavior. The sentence structure in the manual is not proper, and meshes what should be two independent sentences into a single confusing one. PSTT not providing any guidance, and only prepositioning the seeker is new to me. If that's the correct behavior then fair enough. And finally the SAHR description you gave is incorrect or you misunderstood the question- but Naquail clarified. The INTENDED behavior is that if THE MISSILE (not the awg9) loses lock it reverts to PDSTT/TWS SAHR mode. I was not describing the TWS Active handoff. According to Naquail, that behavior is too complex for the current missile API so it does not work.

Appreciate your responses, thank you. So if I'm understanding this. In PSTT it will never get course guidance, english bias, or any course instructions prior to launch.... and will fly ballistic with the seeker head pointed at the STT locked target area, hoping to see it and go active. Basically you need to lead your target and hope it sees it? The SAHR stuff is clear- the game can't handle the complexity of the missile... Yet! And regarding the competitive stuff- I suspected this is people just being sticks in the mud and apprehensive about the Phoenix and tomcat. God forbid the hornet and amram aren't the best, or the hornet pilots reality shatters

Appreciate the reply! Ah so, I think that queueing/english bias is not working properly, often the missile just flies down the ADL even with a lock. It should at least be going to the target area? By the way- The manuals last sentence is confusing, how can it preposition, without a track? Additionally: My understanding from the manual is that if you are ACM Active+BRST then it should SAHR until it gets a lock. This also does not work consistently and you have the same ballistic ADL launch even when you have a lock Finally, the tomcat is currently banned In much competitive play (SATAL) due to either real or perceived issues with the Aim54/AWG9, specifically PH Active and ACM modes causing Desync in multiplayer (banned in TACT). I would love If you had something to say about that either being a known issue and being fixed, or dispelling that notion. Thank you!

PSTT is always active off the rails and gets no post launch guidance? Even at 30 miles? Does it at least get English bias so it goes towards the lock? This is new to me... I was under the impression you could PSTT lock and engage targets at significant ranges. I certainly have in the past and seen the missile guidance work... I thought And just to.be clear about what the behavioral OP is describing, the Phoenix comes off the rails ballistic like a Zuni rocket and does not track anything till it gets to what I suppose is that 10 mile limit.

Regardless of the OP's description... The aim54 does have this strange behavior where it appears to fly straight for a couple miles and then make a hard turn to track the target when in STT. I cannot imagine that being correct behavior while there is an active lock. It's like it doesn't get guidance instructions.