Frostie

Negative, R-60M is. You only need 6 to kill F-15. @OP There are a million and one threads in these forums explaining how to use Flanker or R27ER or how useless they can be etc. So much great info has been written about it, to not search for it is doing yourself an injustice.

Balaced missions are made to create balanced servers otherwise all the hardwork in mission creation does nothing but create an empty server. The best way to enjoy unbalanced, DACT or specialised missions are either through hosted events or internal squad meets.

First thing I did when this became an option, no joy back then. This is the reason it was brought up because having clients in a flight was what we hoped would make datalink work in multiplayer. Haven't tried it again in a while though, maybe something could have changed. :joystick:

Yes good match, congrats on the win.

This is awesome news, I find it impossible to see a negative here, pay and enjoy the new systems or don't pay and get much needed free love for Ka50. I'll gladly pay for the effort on a classic module. Thank you ED.

DCS versions, no.

Link to G drive for SATAL 2019 tacviews https://drive.google.com/drive/folders/1FGZKAG2yX4YhB0gk1ocydtegpxUhtCSR ---------------------------------------------------------------------------------------------------

To revert back to stable I recommend using this. https://forums.eagle.ru/showthread.php?t=160053&highlight=updater%2Autility

https://forums.eagle.ru/showpost.php?p=3861576&postcount=8 This was done in sp and all my testing has been done sp. The behaviour below is clearly a bug. As soon as the missile is launched the F-14s radar is switched off. the missile flies out at 358 deg (353 tacview) the target then cranks to the missiles left the missile follows to 356 deg (351 tacview) the target then starts cranking to the right the missile follows and slowly turns to 002 deg (356 tacview) just before the missile goes active the target starts cranking to the left the missile starts following again just before going active and violently nosing down. The tacview is included here, the track is in the above thread. This bug is happening to all missiles in DCS, it is an ED problem. Tacview-20190328-DCS.zip.rar

SATAL 2019 6th April 2019 104th Phoenix vs Reservoirs Elite -- 14:00z 59th Ravens vs UVAF -- 17:00z Stream live zulutime http://zulutime.net/ --------------------------------------------------------------

<51>Frostie Kamov

Just to be clear here, target range has no effect on radar range at all. The only effect is to change the angle of the elevation increments. eg. Target range of 80km moves the radar up 0.7 degrees for every +1 of elevation. Target range of 10km moves the radar up over 10 degrees for every +1 of elevation. The only time you'd need to put the target range at 80km is if you knew the bandit was 80km away and you also knew his altitude was for example 5000m above you, so as you could focus target range at 80km and +5 elevation for 5000m above you, then the radar would be focused on that targets angle to you. While 10 is not optimal it is a good enough default for large area scanning coverage. A more optimal range set is 20 though this gives 7.5 deg per elevation so with the radars +-5 deg area you cover a large area quickly with decent overlaps to account for targets moving fast towards you. Granted there is no issue being caused by that here, after looking at the tacview screens it becomes clear that the MiG and bandits are all really low 100m to 500m. Some things to highlight, MiG radars as are all radars, are very poor in the weeds, about 40% inferior performance than at medium altitude. In Interleave you won't see a cold bandit at that altitude until 12km, Medium PRF 15+km. Vertical scan with radar on won't lock until 10km regardless of altitude. Vertical scan with radar on will always ignore EOS locks, even if an EOS lock is possible. You need to turn radar off to get EOS to lock in this situation. 4 bar scan is very slow to relay info. And also like I said earlier F/A-18 is very cold signature in DCS, even prop planes give off more heat. :lol: I'm not discounting a bug here I am just pointing out that there are a bus load of variables in this sim that many don't consider or believe are actually there.

When exactly that is happening here. https://forums.eagle.ru/showpost.php?p=3861576&postcount=8

F/A-18 Hornet, Mirage and F-14 have a very low heat signature in DCS, much, much lower than any FC fighter,EOS is really poor at picking these aircraft up. IFF is performed by an interrogator/transponder. Su27 is missing peer to peer datalink in multiplayer, this is a invaluable tool that it has to do without in DCS mp and pretty crucial for the Flanker. F-15C didn't start wholesale upgrade to datalink until the 21st century, JTIDS developed in the 80s was cancelled. Ka50 doesn't have a radar.

One thing that stands out for me here is why in the hell do you have target range set at 78.9????? This will make any elevation in your radar very small so if a target is higher than you and you elevate the radar you're chances of getting him in the scan zone are extremely low. Just leave it at 10 and don't play with it. One thing you need to remember is that the radar runs a 4 bar scan this can take several seconds to get a picture. Another thing that could be happening here is doppler effect with the cold bandit, if you're chasing a target who is matching your speed your radar will not pick this up. And finally the Hornet heat signature in DCS is about as hot as a wet fart.

So maybe the R27 family in DCS need better kinematics but have a battery life both like the 530D has in DCS.

I've updated the AIM54 track now on the original post since the update. As soon as the missile is launched the F-14s radar is switched off. the missile flies out at 358 deg (353 tacview) the target then cranks to the missiles left the missile follows to 356 deg (351 tacview) the target then starts cranking to the right the missile follows and slowly turns to 002 deg (356 tacview) just before the missile goes active the target starts cranking to the left the missile starts following again just before going active. If you watch the track with out changing views you will see this all happen. The track is on the opening post. I've attached a tacview here Tacview-20190328-113921-DCS.zip.rar

Yes an estimated course from last known is how an ins system would work but in DCS it doesn't stop there, it continues updating the targets aspect changes even though the host radar is switched off. That is the point of this thread. Counter measures still apply and will stop the missile from trackng.

Since the inclusion of the AIM-54 it has become apparent that all missiles track targets without any source of guidance, be it aircraft radar or missile own seeker. Once launched on a target if the shooting aircraft drops lock the missile continues to track as though it would HOJ. I think this is to do with some INS features ED added not so long ago. This has become more apparent with the AIM54 because of its speed and range and this bug greatly exaggerates its capability. This is a major bug and needs to be addressed. I have attached 3 tracks 1. AIM-54 launched at approx. 50nmi, lock is immediately dropped but the missile continues to track targets lateral movements and then goes active at the appropriate range and splashes the target. (updated this track since update 2.5.4.29004) As soon as the missile is launched the F-14s radar is switched off. the missile flies out at 358 deg (353 tacview) the target then cranks to the missiles left the missile follows to 356 deg (351 tacview) the target then starts cranking to the right the missile follows and slowly turns to 002 deg (356 tacview) just before the missile goes active the target starts cranking to the left the missile starts following again just before going active. If you watch the track with out changing views you will see this all happen. 2. AIM-120 does the same as above though launched at 35nmi (older DCS version 2.5.4.28840) 3. R27 is affected by the bug also but having no radar of its own never gets near the target. (older DCS version 2.5.4.28840) AIM-120C tracking.rar R27 tracking.rar AIM-54 tracking 2.trk

You have to have the target crank from left to right, you will then see the seemingly dead missile follow the movements.

From the manual. The AIM-54 has a range of at least 60 NM against a fighter sized target at high altitudes in pulse doppler STT. When using TWS for engagement against multiple targets this drops to about 50 NM. It has a greater range against large targets and vice versa against smaller targets.

As far as I can tell, yes.

I believe this bug is to do with the missile INS logic ED started implementing not too long ago. It affects all missiles and it is simple to test. Just set up a mission against the AI that makes lots of turns, fire a TWS shot on the aircraft from 60nmi then turn cold, radar off etc. and then watch the missile in externals. The missile will follow the heading of the aircraft but this is not tracking pitbull with radar it is pure INS driven. You can test this with any missile any aircraft. When the missile reaches pitbull range around 10nmi you will see it snap its nose on to the target, SARH missiles obviously don't snap on. ED need to fix this asap.

Held back on pre purchase and waited for the release of the F-14 to use some of my large collection of bonus. Considering i've spent full price on so many modules I thought it'd be a good opportunity to use some and save a few dollar. But no bonus is not available on the F14 so i've now been suckered and have got to pay 79.99 instead of the 69.99 I would normally have paid for pre release.

<51>Frostie BMP2