The Bad: I could not get the PRC117F long range radio to play nice. I totally forgot the relatively easy step of hitting Pre +/- to change channels, and spent way too long trying to figure it out before giving in and asking on Side channel. This was a mission critical issue, which was not received well by command. I had already asked my aircrew and anyone available on how to fix it. I asked on Side channel as a last resort was told to...figure it out. Failure is on me for not knowing how to set it, but I think there needs to be a contingency for this. We didn't know if it was a range/power issue initially, and spent a long time troubleshooting it. Part of this is possibly due to the server crash after the initial mission start. We had been doing comms checks when the server crashed, and I did not check them when we started again the second time.
You're not the only one who had radio issues for the first thirty minutes. It may have been server related.
When I saw there was no pilot, I became worried the aircraft was damaged or Dimitrius had been killed. I was very happy to see him alive and well, helping carry the remaining wounded out to the helo after stopping to do CPR. The helo spooled up and Dimitrius raced us back to base. Unfortunately en route our patients expired.
So this is to woof or anyone who wants to answer.
What is the proper procedure for calling out "We're all in the chopper, take off!"
There were to times where I almost took off because of conflicting responses to my "Are we all in?"
Pilots can't look backwards very well, especially in the KnightHawks.
I realize "We're all in the chopper take off" is a good enough answer, but I wondered if there was a "Squad" level mindset/quick-check for "We're all in, take off, already!"
Simplest method is for the team/squad leader to use his shacktac HUD and call for example "Apache 1'2, all in". If there is more than one unit wait for both leaders to call all in and then either of them should tell the pilot to take off. I myself like to be the last one to board of either my team or squad as to safeguard against Stonethrower M/54 still sitting a bush and cooking in his safety direction and because it is highly unlikely for the unit to call all in if their leader isn't in.
We had the same problem at the first CASEVAC call. The nine-line stated 4+1 (WIA, KIA), but we had no confirmation on how many were on board, and as pilot I ended up sitting too long on the ground trying to find out if all the patients were on board and we were good to go. Having a soldier do hand signals would be a good fall back, with them positioned in front to the right of the aircraft. As pilot, I wasn't comfortable switching to the ground frequency comms because then I wouldn't be in touch with my aircrew or the other helo in the air that was orbiting in case we went down or had a malfunction.
When hauling troops, I just ask to be notified when last man is on board and we're clear. When I get a confirmation, we're off. When dealing with patients who can't speak, it gets a lot more complicated. On that first call I had Pepper contact the ground team to confirm the number of patients, and you can see in one of the videos posted above there was some confusion, with the helo just sitting there.
Some practice/training for CASEVAC runs would definitely be a good. Including a rotary ops evacuation (with 9-lines) into an advanced medic class would be ideal. I've requested a basic and advanced medic class for ArmA in the TGU forums because I suck as a medic and would like to get better.