|
Note: You must be registered in order to post a reply.
|
| T O P I C R E V I E W |
| Crowebar |
Posted - 18 Jan 2016 : 07:54:05
Flight leads in this Sunday's official campaign mission, "Korean 4.33 Part 8" 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
|
| 7 L A T E S T R E P L I E S (Newest First) |
| Ironman |
Posted - 20 Jan 2016 : 15:39:43
P2P and CS
For the technical people amongst you this might help explain some of the issues we are having
http://www.bmsforum.org/forum/showthread.php?25542-4-33-not-showing-the-right-connection-type-(P2P-CS)
 |
| Crowebar |
Posted - 20 Jan 2016 : 09:01:21
Ironman - I have converted the IQT TE's and the assessment flight. It was straight forward and they worked fine.
All - JSOW remain a banned weapon and should not be used on 185th official missions.
|
| Sharpe |
Posted - 19 Jan 2016 : 20:01:50
Guys,
In addition it's worth noting that blue flight considered the use if JSOW but we averted from this by the XO on the basis that there was a recent ruling (post 4.33) that says they are still not to be used.
Given that black flight opted to use JSOW (or at least that's what they said in the brief) can we have a common consensus on the use of JSOW in 4.33 as it is clear the message has not got round the whole VFS.
-Sharpe
 |
| Ironman |
Posted - 19 Jan 2016 : 17:42:22
has anyone converted any TE's from 4.32 to 4.33 ?
re:- Zips post above, we tried 1. above but it was pretty much FUBAR from take off we delayed switching to U6 until I saw everyone was airborne then tried again ... when we did get intermittent connection it was unusable as a means of package communications.
glad I did not pull PC duty this night :0)
|
| Zipgun |
Posted - 18 Jan 2016 : 23:23:42
Flight Role: (CAS/Strike)
Avenger11: "Zipgun" AA=1 AG=8 RTB
Avenger12: "Sharpe" AA=1 AG=8 RTB
Avenger13: "Crowbar" AA=0 AG=0 RTB
Avenger14: "Scruffy" AA=0 AG=8 RTB
INGRESS was good, we burned our way to the release point as briefed. As mentioned above, COMMS left a lot to be improved upon, so I don't think I need to rehash it here. Suffice to say, we need an understanding of what went wrong, but more importantly, we need SOP improvement here!! Some points come to mind:
1) All flight leads should come up on tactical, check in with the package lead, and do a comm-check round to ensure all can be heard by each -- before switching to tower. ALL flight members should monitor the comms check and report their success to flt lead on Victor.
2) If #1 suffers radio damage or cannot communicate with the package, they should pass the lead to #3 (#2 if a 2 ship) immediately, and then try to sort the issue. It is a responsibility of #3 to assist #1 by pointing out radio calls that have gone unanswered and offer to step-in, if necessary.
I’m sure there other suggestions/procedures, but I offer these as seed for discussion.
Back to the debrief, it looks as though units were “missing” during the mission. I’m not sure why, but I bet the Devs. would speculate/blame connection issues (given the amount of warping visible in the ACMI). It could be the combination of bandwidth issues + comms issues + the fact we were exceeding the recommendation for long-range weapons (4 per ship) might have resulted in a confused server and FUBAR results. I recommend the 185th not carry more than 16 SBDs (2 ships) in any given mission. We had no issues with that number last week, 32 may be over-the-limit Also, staggering SDB deployment to have no more than 8 in flight at a time should be considered.
This situation may need to be checked against some unknown quadratic equation of:
[# ships in the package * (A-G stores carried / bubble factor {range greater that say 20nm} / number of low bandwidth pilots] / the square root of Avogadro’s number
-- you get the idea … there is a limit to the server tolerance for 12-16 pilots on Sunday night – compared to Mo-Sa or TEs with fewer variables. As much as I love flying campaigns, maybe we should convert some of our old TEs and see if there is better performance with those. Then we can decide the way forward.
|
| Ironman |
Posted - 18 Jan 2016 : 19:03:00
Flight Role (CAP)
Gipsy 21: Ironman AA2/AG0 RTB
Gipsy 22: Mango AA0/AG0 RTB see below
Gipsy 23: Sabre AA0/AG0 RTB see below
Gipsy 24: Fisty AA1/AG0 Ejct
Mission Outcome (according to BMS ): MS
Mission Outcome (according to flight standard): not MS
The Take off was good - ingress was good - first encountered group of bandits on the nose lead popped 2 of those chaps. second group called at 11 o'clock second element got one of those but lost fisty.
Comms were shocking for everyone - I even reverted to texting at one point to try and communicate. HSD was only way to kind of guess what the strike flight was up to.
We never acquired Gipsy 2:3 in IDM which added to 2:4's work load trying to keep some kind of formation and mutual support suffered when they attacked the migs.
Eventually RTB making sure we covered the other flights 6 on the way home.
The landing was not our finest hour - sabre came in too hot (190knts at touch down) and slammed into the back of Mango who was at the time doing 45 knts as I would expect 3/4 of the way down the runway - GREEN will debrief this privately.
KIA or RTB - BMS will not depict you as KIA if you land back on the runway - so the debrief said Mango and Sabre RTB - am sure zipgun can testify this is correct.
don't know what the solution is to the comms situation - perhaps each flight lead should be given broadcast rights on T/S as a back up plan ????
Ironman
|
| Veiland |
Posted - 18 Jan 2016 : 12:43:16
Flight Role: (CAS/Strike)
Lobo21: "Veiland" AA=0 AG=7 RTB
Lobo22: "Flyingstone" AA=1 AG=13 RTB
Lobo23: "Floyd" AA=0 AG=0 RTB
Lobo24: "Griffin" AA=0 AG=0 RTB
Mission Outcome: MS
Internal briefing was rushed due to lengthy initial discussion about which targets to attack (We need to have this sorted out beforehand on the forum instead)
I ended up attacking Floyds target as I had misundestood the target assignments. I was 100% sure which target I should attack and confirmed I would be attacking the westernmost target, but afterwards both Floyd and FlyingStone was 100% that I instead should have attacked the target at wp 3.
This lead me to killing everything at Floyd target seconds before his bombs hit.
A classic case of not paying enough attention to what is being said.
I should have repeated individual target assignment.
Once in the pit we all experienced texture clipping and other weird graphical glitches. I think its related to the specific airbase. I couldn't see my own taxi light and couldn't determine the extents of the taxiway.
Once Airborne I was suffering from severe bird twitter noise on the radio, making it hard to hear any communications (Try imagine a telephone conversation with someone at a concert)
At time of weapon release we were being engaged by SU-27, which we then proceeded to engage, downing one of them.
When Zipgun called RTB we disengaged and headed home.
Safely on the ground #1 and #4 exploded on the taxiway at the same time. Apparently I ran into Flyingstone, though my visuals and the ACMI showed him 100+ meter ahead of me. Not sure what got Griffin.
On debrief I was court martialed but the whole 4-ship showed as OK.
Flyingstone and Floyd were switched around on the debrief.
Griffin was listed with a 0/0 RTB in the debriefing, despite good releases. We were unable to find anything in the Acmi as it looks like his targets deaggregate before the bombs hit. The bombs are flying as they should, the targets just disappear well before bombs hitting.
Not very enjoyable flight from my point of view.
I think we should disable the radio range option and the option that makes radio sound more realistic.
I never had any problems of any kind in 4.32 (Besides forgetting to turn on trackir and the like) but 4.33 is almost unplayable on sundays. |
|
|
| 185th VFS |
© 2000-2018 185th VFS |
 |
|
|
