It is heartening to see so many people feeling the same way about this. I just hope that Oleg and the team do too.
Taking the SOE Lysander mission type as an example, certain parameters would need to be coded in to make it work convincingly. Most particularly target waypointing and ground unit AI behaviour.
Imagine this:
Having crossed the Channel in the dead of night, you bank and circle "that little field" that you were directed to in the briefing. The target has a rendezvous time (get there too early and the enemy ground units will arrive before your friends do). At the appointed time you get a flashlight signal from the from the ground. (Hidden Target Complete). You cut the motor and sideslip in. The game engine is designed in such a way that it can recognise just how close the player is to the rendezvous point when their aircraft rolls to a stop. When you are on the ground, the clock is ticking. Land close to the friendlies and there is not long to wait. The further you are from the landing point the longer you have to sweat it out. If the friendly units make it to your aircraft, you get the Mission Complete and you can get the hell out of there.
While this is going on, you have AI enemy ground units that are smart enough to detect your presence and converge on your location. Maybe they will get there first....
Similar mission building parameters can be used for air-ambulance missions or supply drops, providing the builder can vary the duration of the stay on the ground. It is a simple enough idea, but versatile and effective. It just needs devs who care enough about it to put it into practice.
|