al531246

Please disregard Bignewy's comment, he's talking nonsense. The issue is caused by the F-16C's damage model. The pilot's hitbox is defined by the entire canopy. It is the same in the F/A-18C too. Any hits to the glass cause the death of the pilot.

It's in my post with the graph image, it's an attached file. Whether the ECM came on 1 second or 15 secs after launch is inconsequential; the missile was not launched in HOJ nor was it flying a HOJ pursuit course. It's performing a guided intercept without guidance. It's that simple.

My buddy in the Su-27 also reverses his crank at the same time. You can see this in the tacview. I think it's more likely the missile is reacting to his defensive maneuvers.

I believe he activated it (as in hitting the E key) immediately post launch.

Because I made the track with my buddy about 8 hours ago.

You've misunderstood. The opponent's ECM was off at the time of launch. Launch + 2 second the ECM was activated. The missile then holds the lock and tracks until ECM is deactivated, regardless of whether the guidance radar is alive or not. A standard STT launch is lead pursuit. A HOJ launch is pure pursuit. The missile is operating in lead pursuit throughout, confirming the presence of a bug. Basically ECM being on turns your FOX-1 into a FOX-3. This is obviously incorrect.

@FlappieTrack acquired. Tacview attached as well. Brief: Me and a buddy flew head on. He would activate his ECM (Su-27) one second after receiving the Missile Alert warning on RWR. Therefore it is not a HOJ launch. It is an STT launch. He then killed me (F/A-18C) leaving the AIM-7 without guidance. The missile still guided to his aircraft and only stopped tracking when ECM was disabled. Timestamps: 08:26:39 - We both launch missile 08:26:41 - Su-27 activates ECM 08:26:58 - F/A-18C explodes, AIM-7 continues tracking 08:27:05 - Su-27 turns ECM off, AIM-7 stops tracking You can see the moment the ECM turns off and missile drops lock in the graph below. Tacview-20230117-230159-DCS-HOT_SHOTS.zip.acmi server-20230117-220517.trk

It is done using Trigger. Trigger Type Once Condition [whatever you want] Activation PICTURE TO ALL

Because the missile must be launched in HOJ mode. HOJ guidance is completely different from normal guidance. Also the AIM-7 doesn't have a logic which would auto-select HOJ if a lock is lost.

Okay. I will attempt to recreate for a track.

Is it absolutely necessary to provide a track..? It's not a bug that needs to be identified. It's an incorrect programming of the missile's logic.

Aye. However I would point out; 1) I didn't launch in HOJ. It was STT guidance. The AIM-7 would not auto revert to HOJ after dumping lock. 2) AIM-7F doesn't have HOJ capability UPDATE: AIM-7F does have HOJ capability per ADA142508 - https://apps.dtic.mil/sti/pdfs/ADA142508.pdf But this doesn't negate the issue. Point 1 still stands.

The AIM-7 has once again acquired the ability to self-guide to aerial targets. I've confirmed this on the AIM-7F, I've not checked other variants of the AIM-7 but I suspect it will be the same. In the following series of event I am the player герой. 1st Event In the Tacview attached below skip to 11:01:20. Observe the AIM-7F launched by player 'Baguette 3-5 - The Skyline' (F-14A) track to player герой in an F-15C. Timestamps: 11:01:24 - F-14A launches AIM-7F 11:01:50 - F-14A destroyed by Frosty in F-15C (note the F-14A's AIM-7F continues tracking) 11:02:15 - AIM-7F impacts герой F-15C despite being unguided 2nd Event In the second instance герой launches an AIM-7F onto an F-14A 'Sapphic 1-1'. The F-14A is destroyed by a friendly F-15C. The lock on the F-14A is dropped by герой. The AIM-7F guides itself onto a new target - a friendly F-15C. Timestamps: 11:44:15 - герой launches AIM-7F 11:44:23 - F-14A destroyed by Frosty in F-15C 11:44:29 - STT lock by герой on F-14A is dropped > Missile then acquires Frosty in F-15C (uncommanded) 11:44:51 - AIM-7F impacts Frosty in F-15C Don't have a track file because I don't record tracks. They're always broken. Tacview-20221230-201455-DCS-80s-production-V42-OVC.zip.acmi

Was about to report this. Quite stunned to find it's been known and untouched for over a year. Sad!

I did not know this was possible, appreciate the correction. Many thanks to you both.

Integrity check was a brilliant idea implemented with utter incompetence. It doesn't prevent actual cheating (you can easily fool IC if you know how) and it classes any modified file as a 'fail'. It's so bad that most servers don't run it, it just causes problems. I feel your pain on this matter. When ED expanded IC to include everything and playerbase responded negatively, ED ignored all of it and preceded to do it anyway. Intelligence and basic awareness is not something commonly found in Russia it seems.

The time displayed on the clock for each clients jet is not synced in online multiplayer. This is a critical issue and prevents any kind of co-ordination on missions. No tracks attached as there's no point. Issue is self evident.

They are installed in the main directory. There are certain aircraft you cannot install liveries into Saved Games for. Mostly AI aircraft and anything added to the game before the F/A-18C. These are failing IC. They shouldn't be. It's a bug.

FOUR YEARS ED, FOUR FREAKIN YEARS!

For some reason liveries on aircraft placed in Bazar > Liveries fail the IC. Certain aircraft require liveries be inserted into this folder because they are not part of the coremods file structure i.e. Mi-8, E-2, MiG-29 etc. Obviously these aren't 'hacks' or cheats. In fact there's nothing you could place in the bazar > liveries folder that would enable cheating. For next update could the liveries folder please be removed from the IC. It serves no purpose.

Feels like that when reporting bugs to ED doesn't it...

Just to add to this topic. I thought the Tin Shield had been removed from the editor because I couldn't find it, only to discover (as a result of this thread) that it's incorrectly associated with the SA-5! It's definitely erroneously named. I have mapped a number of SAM systems all over the world onto my own .kmz file and I have never seen a Tin Shield operating in unison with an SA-5. I've seen Tin Shield's left behind when an S-300 site has moved and the TS is used as an EWR. Northstar98 is quite right to point out call this a bug. It's incorrect.

Yeah, US Flag should always face forward. Stars first. Intended to signify flag being flown into battle.

+1

This issue is still present ED after a YEAR...