Author |
Topic  |
|
Zipgun
USA
521 Posts
Status: offline |
Posted - 08 Jun 2016 : 20:14:15
|
Missions using the new theater: The one-time overview of the OPFOR strength

There are SA-11 and AAA battalions near the FLOT, and they can be mobile. Supporting these are SA-10s deeper in the north that may overlay the FLOT. Expect BARCAPs to be on the FLOT in varying numbers (F-18, Mig-29S, Su-27, Su-30)

Our misssion is to begin reducing long range SAM threats to protect our CAS missions on the FLOT.
Python 1 - 4 ship AI out of Chongju with the objective to kill at least 2 SA-10s. Results of 1 SA-10 and 5 SA-11s will also be viewed as a MS. 1 SA-10 and 2-4 SA-11 will be partial success
Shark1 - 4 ship Sweep out of Yecheon is escort for Python1. Mission success is no losses to the package. PS is no losses to the DEAD flight. A-A loaded F-16s in this theater carry only 4 120s, so careful sorting and good shots are required. Shark lead is package commander and may change the steerpoints as required.
Other flights will be added to the package if more than 8 pilots show up.
The Save files are here: https://www.dropbox.com/s/2ok3gc01dklqzp4/12Jun16%20Mission.zip?dl=0
|
|
Griffin

UNITED KINGDOM
4979 Posts
Status: offline |
Posted - 08 Jun 2016 : 20:40:26
|
Apologies for not keeping up, but where is the new theatre? Is it part of 4.33.1 or is a separate download?
Nice briefing Zed.
|
 |
|
Vosene

United Kingdom
4594 Posts
Status: offline |
Posted - 08 Jun 2016 : 21:07:44
|
quote: Originally posted by Griffin
Apologies for not keeping up, but where is the new theatre? Is it part of 4.33.1 or is a separate download?
Nice briefing Zed.
Seperate download.
http://www.185th.co.uk/forum/topic.asp?TOPIC_ID=7744
 |
 |
|
Zipgun
USA
521 Posts
Status: offline |
Posted - 09 Jun 2016 : 19:17:41
|
We should all add this line to your BMS config --
set g_nClientPort 2935
this forces you to use that port and should become a squadron standard. If your router is misbehaving and 2935 is not forwarded, you will not be able to connect.
Several config values should be checked by prospective hosts:
set g_nForceMinClientBwSetting 1024 // Allows the MP host to specify a minimum client bandwith setting (default 0=no value forced)
set g_bNoAiForHumanControlledSqd 0 // Allows the MP host to specify whether AI pilots can be assigned for Player Controlled Squadrons (default 0/false)
set g_bRequireSameAcdataMP 0 // Allows the MP host to specify whether ACDATA files need to be the same in MP (default 1/true)
set g_nRemoteControlSurfacesInterval 0 // Time in ms between control surface updates, valid range 20-1000 (default 200), 0 = disabled
set g_bSkipAggregationBWCheck 1 // Allows skipping the (bogus) check_bandwidth calls during MP reagg/deagg (default 1/true)
set g_bHostAllowsDubiousConnections 0
|
 |
|
Vosene

United Kingdom
4594 Posts
Status: offline |
Posted - 12 Jun 2016 : 19:05:52
|
Flight Leads in this Sunday's official campaign mission, "TvT Mission 1" are requested to post a debrief of their flights actions, including any lessons learned or that should be learned by others.
Please put the following information at the top of your post:
Flight Role: (SEAD, ESCORT, STRIKE, Etc..) Callsign11: "Pilot's name" AA=X AG=X RTB,MIA/KIA,EJT Callsign12: "Pilot's name" AA=X AG=X RTB,MIA/KIA,EJT Callsign13: "Pilot's name" AA=X AG=X RTB,MIA/KIA,EJT Callsign14: "Pilot's name" AA=X AG=X RTB,MIA/KIA,EJT
Mission Outcome: MS/PS/MF
 |
 |
|
Scruffy
UNITED KINGDOM
146 Posts
Status: offline |
Posted - 12 Jun 2016 : 21:25:17
|
Flight Role: AI Callsign11: "Scruffy" AA=0 AG=2 RTB Callsign12: "Sabre" AA=0 AG=0 RTB Callsign13: "Fisty" AA=0 AG=1 RTB Callsign14: "Mango" AA=0 AG=0 TECH
Mission Outcome: MS After a reevaluation from the original brief.
Ingress uneventful until close to FLOT, held at steer 3 until cleared hot briefly, got one off at an SA-10 60 miles north of FLOT, before holding back at 3 again as there was a lot of air targets. Cleared in again and decided to go for the 11's along the FLOT. During this engagement Shark called RTB and on our egress 3 had a eurofighter sneak in close on him. 3 turned hot and got a slammer away on him before burning south. 3 reported 29 spike on the RWR on his tail. 1 and 2 supported for a delouse on 3 before turning south as well.
Egress uneventful, rejoined and overhead break for recovery. |
 |
|
Zipgun
USA
521 Posts
Status: offline |
Posted - 13 Jun 2016 : 15:50:09
|
Shark1 Escort Shark11 Zipgun 2 0 RTB Shark12 Utopic 0 0 RTB Shark13 Poppy 3 0 RTB Shark14 Vosene TECH - AWACS
MS
Ingress was uneventful, we had several targets appear on radar that could not be seen by Vosene -- guessing that the AWACS may not have been on station by then.
We managed to punch a hole in the BARCAPs long enough for Python to engage the SA-10 ... after that we were in a continual grinder until low on fuel and weapons. Called RTB and everybody made it home alive.
The DPRK EF-2K actually show as E on RWR, not 22. If our numbers stay low, I may have to dial-down the red air a bit ... |
 |
|
|
Topic  |
|
|
|
185th VFS |
© 2000-2018 185th VFS |
 |
|
|