Date: 2010-11-27 07:21
Dslyecxi's MH-6 Practice Scenarioby
The intent of this mission is to give MH-6 pilots an opportunity to build their skills via observation of techniques as well as practical application of the same techniques themselves, to include flying as a wingman in any training scenario. The intent is not to give a from-the-ground-up period of instruction in all things helicopter. You should have some basic helo skills to get the most out of this, though that's not to say that a novice pilot won't find something useful in it for them. Finally, note that this is primarily a skill-building mission - every "real" LZ has to be considered with a multitude of things in mind (see TTP2 for more details), while these have been chosen to show various concepts without the overhead of a fully established enemy presence etc. Note too that all LZs show an exfil as well, since landing at an LZ is only the first half of the dangerous task.
Upon launching you will experience a longer-than-usual load time. This is due to processing a lot of scripts (helo paths) at the start.
The interface for this mission is exclusively action-based, aka the mousewheel menu.
The initial options you will have are:
"Show Selections" will display the entire set of training courses. They are labeled either as S, M, or H - translating to simple, medium, and hard courses respectively.
"Display Help Hint" will cause a constant hint to show your speed, the lead helo's speed (if different), and the difference between. This can be used to display the speed when in "Ride-Along" mode, or to compare your speed with the lead helo in "Fly With" mode.
The "Training Mode" option toggles between "Ride-Along" and "Fly With" modes. "Ride-Along" puts you in the copilot seat, allowing you to get a perspective of a given flight path from that point of view. "Fly With" allows you to fly your own helo in wingman (or chase) mode alongside the flight-pathed helo - you will typically start on the right side of the lead helo, offset behind it somewhat and generally above it to permit you to build up some speed at the start.
Once you have selected the training mode and whether you want to use the help hint, show the selections and pick a course. The descriptions of the current ones will follow later in this post.
At this point you will be teleported to the starting area, followed by a quick countdown that ends with the path starting. When the course is complete, the lead helo will freeze in space for three seconds, then teleport safely away. At this point you will be returned to your own helo (if in ride-along mode) and given an opportunity to pick a new course. You can repeat this until a helo blows up, at which point you'll need to restart the mission.
Extract the .pbo file(s) to your ArmA2 Operation Arrowhead\Missions folder.
This is untested on other systems. For me, the given scenes will play reliably for me whether at 1x or 4x replay speed. It is possible to have them glitch out and result in the lead helo exploding due to a collision with 'something'. If that's the case, restarting the mission generally will result in it working. This may happen more often on slower machines, but like I said, I haven't been able to test that.
I intended to do more 'rabbit chase' scenarios, but these tend to explode more often than not, and after awhile I got tired of watching cool paths explode when being replayed.
I have recorded some formation stuff that I'd like to make into a training scenario sometime. If you're interested, let me know and it'll bump higher on my priority list. You can see one example of this in my "Omen" video.
I could have filmed dozens upon dozens of paths for this, but due to various concerns I've limited it to 40 paths for now (with 14 of those being autorotate/tail rotor scenarios). I am more than happy to create additional demonstrations of anything anyone would like to see, so if you have an idea/suggestion, simply post it and I'll work something up sometime... hopefully, schedule permitting.
The current courses are as follows.
Easy: The easy scenarios are intended to show basic skills that all helo pilots should be proficient in. These are the building blocks from which you can execute more complex and demanding maneuvers.
Medium: Medium scenarios turn the difficulty up a bit.
Hard: Hard scenarios take it a step further.
RL scenarios are about rotor loss. There are ten examples, showing recovery at different initial speeds, altitudes, and environments. You can trigger your own rotor loss by 0-0-1 in the radio menu. You will have ~15 seconds of fuel after this, and will have enough damage to cause a heavy spin and require a gentle landing. See "Tips" for more on this.
AUTOROT scenarios deal with autorotation, brought on by total fuel starvation. There are four examples covering the basic possibilities - highspeed at low and high altitudes, and engine failure while going up and down hills. Note that this demonstrates the default vanilla Arrowhead method, and not the how-can-you-possibly-mess-this-up ACE2 hand-holding method. You can induce an engine failure by using the 0-0-2 radio option.
Rotor Loss Tips
Generally speaking, rotor loss that happens at mid to high speed, or high altitude, is very easy to recover from. Low-speed rotor loss that results in an immediate spin at low altitude is very hard to reocover from due to how much can go wrong before you get enough altitude or get the spin under control. This is what I focus on most in the examples, and as you can see, it can get very hairy and require some creative touchdown methods.
This is an inexact science for me presently, but my general actions are as follows. If you find a more reliable method, feel free to post about it.
The basic steps are:
To go into more detail:
Engine Loss/Autorotation Tips
This is dead simple in the vast majority of cases. Immediately bring your forward speed to a minimum (30kph or lower) while holding your thrust down key. When 20-30 meters above the ground, press and hold thrust up. You should touch down lightly, provided you chose a good LZ. See the "Going uphill" example for a good case of where quick-thinking is required to prevent a disastrous outcome.
- BI forums