speed-of-heat

Yeah , I did that yesterday, but thanks for the tips

There is some inital chat before the start of the jet that shows on screen but doesn't have any voice over for ? Once you get the mission success banner there doesn't seem to be any approach comms when you get back to the airfield, is there anything intended ? Targeting and the waypoints seem "odd" to me , I mean why put the target waypoint at 30k feet rather than say on the center of the runway I get we don't know where the targets are exactly, but we know they are somewhere near the airfield ?

As above , they don’t … @SorelRois working on a fix It was likely the J-11’s who took out your wingmen, the harms almost never get through, they are there as a distraction really for the massed harpoon firing from the buffs

The mission objective is to get the buffs into range to fire, when you are firing your HARMS make sure you PGM2 (at least) on HAD before releasing them . Most likely you are being launched at by J-11 , they will murder everyone unless you take them out

as title. briefing says we have a HTS but none is equipped on the jet at startup

Thanks!

@SorelRoOk after replaying this many ... many times... the issue seems not to be the SAM's but actually the J-11's or the F-15C's take your pick, the F-15's just don't engage the J-11's or not very well and certainly not early enough in one mission i saw them pickle their tanks at WP1, in my last mission they got 1 - 2 of the J-11's for a total of 3 slammers fired... my "fix" was to load up with 4 120C's and fire of my 4 HARMS as soon as I got PGM2 then got my wingmen to engage the SU-27's alongside me (their parents have all been notified) I got 5 kills on the J-11's one with a gun and my 4 slammers all found a home... and we had 5 of the buff's actually make an attack and exfil. The issue seems to be a few things: 1) The SAM's trigger completely defensive behaviour in nearly all the flights regardless of if they are actually threatened or not , which costs them energy and initiative and time 2) meanwhile while they are all diving for the deck the J-11's slaughter the buff's and anyone silly enough to try and climb up to meet them from the deck, meanwhile the Buff's also get slaughtered 3) the Eagles just don't engage (but 3 of them survived, 2 with a full set of Slammers and Sidewinders), and that can be said of Uzi 1-2-4 as well who all died very bravely for their country 2 of Uzi 2 survived and they either fired weapons or jettisoned them dragon 04.trk

make sure you haven't got power saving enabled on the USB device opr hub that supports

did spotting dots get changed in the last update? I don't find then in any way effective now?

yes

This, I don't care if it is technically as accurate as you can make it, if it doesn't provide a realistic outcome in the game...that just means it's broken... Put it another way, *The King Has No Clothes*, can we stop admiring the beauty of it and fix it, and if fixing it means "less realistic code" then I think you will find everyone is OK with that. I honestly don't care the route to the fix... Whichever is simplest and quickest

well at least it's consistent... i mean it's either fixed or not

@SorelRonot sure if this is related

For me it's a consistent veer to the right on takeoff roll, I'll try the 20 curve as above, I have a dampened set of MFG crosswinds

No change in behaviour

dcs.log sorry forgot the log !

the TCS worked in 2D, but did not work in VR, same behaviour on both runs

Ok...

AFAIK it only removed the effect not the processing cost, and it is only really for MSAA

COM1 is UHF ergo U Uniform

i was on the correct frequency and the wing man did call out .. couldn't spot it at all ...

Your definition of fun might need a little work

sorry ! Track file dragon cap 03.trk

when i said "some vram" i might have set a hare running that was not really worth it ... we are taking tiny amounts of vram ... like whatever a screens worth of stuff is ... so if you are really tight on VRAM set the system resolution to as low as it will go , and the mirror to use DCS System resolution... it will make almost no difference ...

the "best" current option is to "restart the mission" with Left SHIFT + R , which is marginally faster... there is no "other" fix at present that i am aware of