HeavyGun1450

Yep this is definitely happening after a bandit gets splashed, really annoying

I have experienced this many times now and know several others on the same server I play on have as well, but it appears (sometimes) that the SA-5 will not always give you a launch warning on the RWR. I have experienced this in the attached trackfile. Initially I thought this was happening to all aircraft, but after extensive testing in the mission editor only the Tomcat is doing this. Basically what generally happens is your cruising along at 30k-35k and enter the edge of the SA-5s engagement range, the SA-5 will soft lock you for a few seconds, drop lock for a few seconds and repeat over and over again until all of a sudden you get killed by a missile from it with absolutely no launch warning what so ever. So it seems something is wrong with launch detection with the F14's RWR and SA-5 system. @IronMike SA-5Bug#2.trk SA-5Bug.trk

I believe you are right. Tried it several times with the hornet and couple of times with the F16, F15C, A-10 and cant reproduce. Nearly everytime I try it with the Tomcat is happens. I will go submit it to Heatblur. Thanks

@BIGNEWY@FlappiePlease review the track files when you get a chance. Thanks

I have been able to reproduce this bug twice, two trackfiles attached. Both of the track files have different SA-5 Site layouts with me flying at the edge of the engagement zone of the SA-5, but both result in the same thing: The SA-5 will constantly soft lock you up, drop the lock and repeat. Then without you knowing (because you dont get a rwr launch warning) the sa-5 fires a missile at you, and a minute later, your dead. Note, I have ran this several times over on both track files, it does not happen every single time for whatever reason. I hope this is fixed and helps the ED team out. SA-5Bug#2.trk SA-5Bug.trk

Trackfile attached showing me in a A-10C Strafing MIG-23s parked on the runway. Hit two MIG-23's with the gun with a good 3 seconds burst each, all it did was destroy part of the wing and made it catch on fire for a few minutes. I then dropped a Mark 84 on one, it instantly destroyed one of the migs, then I dropped a Mark 82 on one and it barely did any damage. Damage model is very werid and incorrect here. AIDamage.trk

Thanks for posting some track files guys, hopefully Big Newy reviews them and finds the issue. @BIGNEWY

I'm not sure ED has ever looked into this, something is defenitely not right with the damage model for jets on the ground.

Anyone else experienced this willing to chip in?

Current work around is to cycle the ap switch on and off when you notice the plane doing something weird due to the current autopilot bugs from the newest patch.

Yep. If you land at another airfield and shutdown/repair Jester inputs the INS coordinates from the place you spawned from. Its been brought up several times now and hasen't been acknowledged.

Not sure if it's been reported before but, any AI aircraft parked on on the ground are nearly Impossible to kill. For example I strafed several migs parked on the runway with the A10s gun and a good 3 second burst on one, at most the mig lost part of its wing or just had a few bullet holes in it.

Does anyone know if this bug known and is there a planned fix for it?

Has anyone else looked into this yet?

Yes the SA-5 is a SARH missile.

Happened to me again last night. Its definitely a bug that needs to be checked out.

Problem I have been seeing with the new phoenix model is that If you launch the phoenix at say 35kft, and your target is at say 10kft, the missile drags and decelerates horribly during it dive down to the target making it lose a ton of energy. None of the other missiles in DCS do this.

Awesome point, yeah flying one sortie then coming back and rearming and flying back out to only realize your INS is off several miles and is practically useless is absolutely infuriating. We absolutely need a option to tell jester to realign on the ground. Amazing that nobody has responded to this so far.

Sometimes water textures will not load at a distance, for example flying over water and the water a couple miles ahead of you is not loading and just shows an empty blank part of the map. Looks horrible

This has been a bug for long as I can remember. Basically if any other aircraft are hooked up to any of the 4 catapults, the catapult crew will not let anyone else hook up or guide them to the catapult until the other person launches off the catapult. Can be a big problem in multiplayer when someone goes afk on the catapult and nobody can launch till they leave or launch.

Not sure if ED or anyone else on the forum has experienced this, but I have experienced this several times now and know several others on the same server I play on have as well, but it appears sometimes that the SA-5 will not always give you a launch warning on the RWR. I have experienced this in both the tomcat and hornet so I'm sure this is happening to all aircraft and it is a bug with the SA-5 only. Basically what generally happens is your cruising along at 30k-35k and enter the edge of the SA-5s engagement range, the SA-5 will soft lock you for a few seconds, drop lock for a few seconds and repeat over and over again until all of a sudden you get killed by a missile from it with absolutely no launch warning what so ever. I suspect that unlike other SAMs, the SA-5's missile doesn't self-destruct when illumination is lost, and that there's a bug where if it drops lock and reacquires it won't trigger the launch warning again.

Is this fix expected to be coming within the next patch or two?

Also, can we get a realignment option in the jester menu while on the ground? Sometimes jester flat out refuses to align the ins after a shutdown or repair.

When will this be fixed? I landed and repaired at a different air base and had to reslot because of this.