Slutcher

The only thing jammers do in DCS is hiding range info. Normally when you are within 25nm your radar will get a burn-through to the jammer and will be able to tell the range since then. Also if you fire a missile before burn-through, the missile will fly in Home-On-Jam mode and will track the target autonomously with rather poor accuracy.

Congratulations to CNF for the win. Well deserved and good luck in future matches. See you in the finals! S!

<51>Slutcher Su33

Congratz to inSky for a well deserved win. Many thanks to the RAVENS for putting up a nice fight, especially the second round which was close. Hope everyone enjoyed and see you next time! S!

So far I found It can be done via CTLD. Note you must have MIST and CTLD loaded first in the mission. ctld.deactivatePickupZone('name') Not sure if the zone have to be a pickup zone though, gotta test that.

do if Group.getByName('F-86F CAP'):getSize() < 1 then mist.respawnGroup('F-86F CAP', true) end end Hope that helps.

Sorry we brought it down yesterday for some testing. It's now up and running!

Fixed some issue in mission 2

True 'BVR kills' are rare seen in DCS due to poor missile performance, especially against skilled human opponent. Against AI opponents it is easier. Here are some tips: 1. Always go for medium range ET shots. Launch them between Rmax and Rtr, if no LA then override. The AIs almost never notice it coming. 2. Besides silent kills, the best way to increase your missile's lethal range is indeed launching them from high altitude and speed. For example an R-77 launching from 25km has a good pK at 10000m but is nearly useless at sea level. Generally speaking altitude of the launcher gives a more significant boost on missile performance than speed. However there are some other concerns if you shot at a very low bandit from very high up, the missiles may not track well due to ground clutters, so better convert your altitude into speed in such scenarios. Basically you need to get a good 'feeling' of missile performance(both kinetic and tracking) to use them effectively, and that comes from hours of practice.

I suppose this is not a bug. It is a logic law of the FBW system in order to simulate an airspeed-stable handling for the pilot. As the speed increases, the FBW automatically add a small amount of pitch-up input, and vice versa. Refer to page 112 of the DCS Su-27 Flight Manual for details.

Why it misses: IR missiles typically has a low resistence to flares. It also depends on the IR signature of the target. Since most helicopters have a very low IR signature, the missiles are even more likely to get spoofed, when attacking such targets. Attacking from rear aspect will make the missile harder to be spoofed, in most cases. Why it hits, but doesnt cause much damage: The R-60M was designed to be a 'tiny' A2A missile which even the lightest airframe can carry it. As such, it has a relatively weak warhead, compared to other AAMs. And the Mi-24 is an attack helicopter designed to withstand a lot of fire and still stay in one piece, that's why the R-60M, or even other larger AAMs, are unable to take it down with a single hit. Better use guns then...pew pew pew!:D

Any chance of getting some JTACs lasing 1113 code for the Su-25T?

Heads up gents, here's the letter from the Northern Caucasus PVO Command: SATAL Missions & Briefings For this year's SATAL we will be using 5 different missions. Prior to each match, the mission will be chosen by rolling a dice. See below for detailed briefing: Mission 1 - Anapa vs Sochi Distance: 270km/140nmi Bubble radius: 90km/50nmi Mission 2 - Senaki vs Tbilisi Distance: 250km/140nmi Bubble radius: 90km/50nmi Mission 3 - Maykop vs Senaki Distance: 320km/180nmi Bubble radius: 110km/60nmi Mission 4 - Sochi vs Kutaisi Distance: 250km/140nmi Bubble radius: 90km/50nmi Mission 5 - Maykop vs Vody Distance: 250km/140nmi Bubble radius: 90km/50nmi Mission 1, 2, 4 are mixed terrain, while 3 is mainly mountainous and 5 is flatten terrain. SATAL Weathers & Seasons We have 5 presets for weather. Similarly, they will be chosen by the dice: - Calm, CAVOK - Windy, 10 m/s, scattered clouds at 300 m - Stormy, 20 m/s, overcast - Calm, fog, overcast - Stratus overcast, 1800m ceiling, light wind - Broken clouds 500-2500 m, wind 5-15 m/s Real-world season(northern hemisphere) of the match date will be applied. Temperature will be set based on seasons, with an idea of simulating the climate of caucasus region: Winter: 5°C Spring/Autumn: 15°C Summer: 25°C Missions and weather presets are in attachments. To use the weather presets, put them under Saved Games/DCS/MissionEditor/weather/. When you run DCS, go to mission editor and you should have them at the bottom of the 'Weather' Panel. Also, we'd like to inform you that 51st have got new Teamspeak address and Website/forums. Get yourself updated on these infos so you can find us easily! Teamspeak: 96.43.128.170 Website: http://www.51bisons.com (under construction) Forums: http://www.51bisons.com/forums/ Good luck to all squadrons. See you in the sky. S! Weather_Presets.zip SATAL Missions V1.1.zip

My first flight ended up suddenly getting jumped by Micro who was last seen 60km away but Mach 2:doh: GK! Second flight I blown my tires after ferrying to Tonapah Test Range landing with 6 tons of fuel:lol: At last we landed at Groom Lake and look for those UFOs:D The event was a blast! Really enjoyed it. Thanks IronMike and 104th for organizing and everyone who participated.:thumbup:

The FARP Briefing images seems outdated as some names are different in the actual mission and some simply does not exist?

The 51st Bisons PVO Dedicated Server is now running SATAL missions! Everyone is welcomed to get in for some combat practice and familization of the terrain. Final version of the missions will be available for download soon after 2.5 release. For more information: https://forums.eagle.ru/showthread.php?t=200505 S!

Lovely!:thumbup:

Sukumi has R-77 available. Didn't have the time to check other airfields though.

The Viggen does not have an independent A2A radar. However, you can use its A2G radar for basic A2A purpose by turning the antenna elevation upwards. And there is no such thing of "locking" the target, it just provides you with the bearing and range info.

So logistics are only available at the default, non-capturable FARPs, and to be forwarded to frontal FARPs only by players with the FOBs, is that how it supposes to be?

Awesome mission! Taking couple flights in the server today and it certainly brought me some long-missed immersion in DCS MP. And many thanks for the dedicated slots for us at Krymsk, such warm things will always be noted & appreciated;) One side note, when I was flying the Huey spawned from FARP Gali, I was unable to load crates and it says 'not close enough to logistic' even when I moved from the spawn point to the FARP. The troops are working fine. Possibly a bug? Please look into it when you have time!:)

That sounds awesome! Can't wait to try it

Launch the missile at high altitude and with as much speed as possible to increase the kinematical range. Prior to launching, aim the target with a lead angle. This will allow for the missile to fly a relatively straight path and conserve energy. The R-77 is an active missile but it still need to be supported till pitbull range. As the Migs dont have a countdown timer you will have to estimate it yourself. Besides, it is advised to use the R-77 within 20km as otherwise the missile is unlikely to have sufficent energy if the target is maneuvering.

The in-game fog of war have some critical issues at the moment, like missile launches being visible, and is quite unstable at showing contacts. Therefore it would not be used in SATAL, unless ED will make changes of it. The LotATC however, as far as i remembered, has its own built-in 'fog of war' system and is much better than the in-game one. Currently we are still in the process of testing it but I'm pretty sure it is the best option. In conclusion, there will be no god mode or in-game fog of war. Teams either go with LotATC, or there will be no human controller.

RCtrl+Home is left engine start. If you want to start both you should then press RAlt+Home for right engine, or simply RShift+Home for both engines.