SATAC 2017

[*Rage*]

I dont want to put anyone off. By all means if you want to put a team together, please do, and register. I just want to stress the importance of reliability. This is an issue for everyone involved including the big squads.

[ITGCVerticle Charlie]

hey Rage !! We were having issues with the AWACS in the mission yesterday. The blue AWACS are flying only for 13 minutes in the start and goes for landing after that in both the missions. Can you please have a look ?

[Slutcher]

hey Rage !! We were having issues with the AWACS in the mission yesterday. The blue AWACS are flying only for 13 minutes in the start and goes for landing after that in both the missions. Can you please have a look ?

 

I didnt experience that when i test the mission. Will check it. Thanks for the feedback.

EDIT: It is true. I've fixed it and update the original post.

Edited September 10, 2017 by Slutcher

[ITGCVerticle Charlie]

I didnt experience that when i test the mission. Will check it. Thanks for the feedback.

EDIT: It is true. I've fixed it and update the original post.

 

No problem buddy !!

[Alpenwolf]

I dont want to put anyone off. By all means if you want to put a team together, please do, and register. I just want to stress the importance of reliability. This is an issue for everyone involved including the big squads.

Don't bother, mate. All good. I'll watch with joy!

[Aries]

Squadron Name: *NOB*Mrcine

Aircraft Selection: 4*F-15C / 2*Su-27

Time zone for every pilot is: +2 Zulu

 

Pilot Roster:

*NOB* Aries

*NOB* Wepar

*NOB* Shark

*NOB* SexyRexy

*NOB* Bobby

*NOB* Cove

*NOB* Adi

[MasterYoda1]

Squad Name: VF-6666 =NP=

Time Zone for all pilots: Zulu+8

Aircraft Selection for 1st match: F15*2, M2K*2,Su-33*2

 

Pilot Rooster:

=NP=Master Yoda

=NP=Niaotou

=NP=Driver

=NP=Newbie

=NP=Skywalker

=NP=518

=NP=Yellow Crane

=NP=Saobao

=NP=165

=NP=Killer

(this list is subject to change as I am trying to add in as many backup fliers as possible in case of no shows)

 

and a request

 

October 1-7 every year is a major national holiday in mainland China. Because of this, a lot of squadrons based in China cannot send enough people for SATAC, my team is also struggling to come up with six people. Therefore my request is that from next year, if possible, let's push SATAC's start date to mid-October. I guarantee you will see many more Chinese players participating.

Edited September 12, 2017 by MasterYoda1
rooster change

[JunMcKill]

I didnt experience that when i test the mission. Will check it. Thanks for the feedback.

EDIT: It is true. I've fixed it and update the original post.

 

The other problem I found with AWACS: is giving the BRA to russian aircrafts is miles and feet. I tested the mission in the RED side using SU-27 and SU-33. The AWACS callsign was Magic

[M0ltar]

Right now we only have NATO awacs as Russian awacs, to my knowledge, will not work with NATO units. It's something that both sides will have to deal with if they choose to fly Russian aircraft.

[Slutcher]

The other problem I found with AWACS: is giving the BRA to russian aircrafts is miles and feet. I tested the mission in the RED side using SU-27 and SU-33. The AWACS callsign was Magic

 

This is the best compromise we can do. Because within DCS whether the call is metric or imperial is determined by the AWACS type and coalition not the receiving aircraft, only A-50 in red give metric calls and either red E-3/Blue A-50/Blue E-3 give imperial calls. As the flanker already have datalink we decided to use E-3 for both teams otherwise it is unfair for the F-15/Mirages.

[Aries]

Our squadron developed a realistic warning sound for pilots leaving the engagement bubble...

 

Mission maker, please consider adding this to the final SATAC 2017 mission...

 

Thanks!

 

:thumbup:

LEAVING_BUBBLE.zip

[Slutcher]

Our squadron developed a realistic warning sound for pilots leaving the engagement bubble...

 

Mission maker, please consider adding this to the final SATAC 2017 mission...

 

Thanks!

 

:thumbup:

Fantastic! Tho it is not April fool yet:megalol:

Edited September 12, 2017 by Slutcher

[Aries]

Fantastic! Tho it is not April fool yet:megalol:

 

:D

[IronMike]

104th Phoenix VFBS

 

104th_Maverick

104th_IronMike

104th_Stuge

104th_Knight

104th_Spade

104th_MoGas

104th_Blaze

104th_Blackbird

104th_Crow

104th_Money

104cdt_Tiger

104cdt_Dozer

104th_reserve

104th_reserve

 

(list might change and significantly shorten before oct 1st)

 

 

S!

[Teknetinium]

51st are honored to welcome back the current SATAC Champions!!!

Welcome 104th to SATAC 2017 /0.

[Slutcher]

Mission updated in post 17!

[Gaanalma]

Squadron Name: 36° Stormo Virtuale

 

Aircraft Selection. 10*Su-27 3*F-15

 

Pilot Roster:

 

=36=Viking (+2 Zulu) Su-27

=36=Falcon (+2 Zulu) Su-27

=36=Lornix (+2 Zulu) Su-27

=36=Merlin (+2 Zulu) F-15

=36=Drigo (+2 Zulu) Su-27

=36=Barbarossa (+2 Zulu) Su-27

=36=Eircog (+2 Zulu) Su-27

=36=Scorpion (+2 Zulu) Su-27

=36=Gaanalma (+2 Zulu) Su-27

=36=Rabo (+2 Zulu) Su-27

=36=Lowlee (+2 Zulu) Su-27

=36=Truthkeeper (+2 Zulu) F-15

=36=Daniel (+2 Zulu) F-15

Edited September 17, 2017 by Gaanalma

[red_coreSix]

Just a heads up, there is a bug at the moment where SARH launches sometimes don't trigger RWR warning. We had this for a while and just today we had a training match against ITGC and it was especially noticeable. Happens with AIM-7 as well as R-27R. Sometimes it doesn't even give a nail.

[Kapsu]

Just a heads up, there is a bug at the moment where SARH launches sometimes don't trigger RWR warning. We had this for a while and just today we had a training match against ITGC and it was especially noticeable. Happens with AIM-7 as well as R-27R. Sometimes it doesn't even give a nail.

We have noticed this too. I think restarting the server usually fixes it, but reloading the mission doesn't work.

[Slutcher]

This bug has always been there...and that's why it is essential to restart the server between rounds. Reloading the mission does not always work and might cause some strange issues.

[Gaanalma]

Edited post 42

[red_coreSix]

This bug has always been there...and that's why it is essential to restart the server between rounds. Reloading the mission does not always work and might cause some strange issues.

 

This definitely hasn't always been there, and it happened in the first round on several servers.

 

Bug report here: https://forums.eagle.ru/showthread.php?p=3246673

[Slutcher]

This definitely hasn't always been there, and it happened in the first round on several servers.

 

Bug report here: https://forums.eagle.ru/showthread.php?p=3246673

 

Ive got this before several times as well. But i have noticed that it happens way more frequently in current version. Hope they fix this with the 'late September' Su-33 update before SATAC.

[*Rage*]

10 teams signed up so far!

 

1st post updated with latest mission files. 2nd post updated with latest rosters. Registration closes in less that 2 weeks.

[IronMike]

51st are honored to welcome back the current SATAC Champions!!!

Welcome 104th to SATAC 2017 /0.

 

Thank you so much, old friend! <3

 

We are delighted to be part again and to support the 51st with anything you guys need!

 

Big time S! and thank you so much for organizing!