ROTW_FORMATION_V1.0.8
FOR PC ONLY

ROTW August 2005(c) 	(http://fly.simvol.org/)
author = laurentC		(http://balloon.flightsims.perso.cegetel.net/Fly_FORMATION1.html)
baloon@hotmail.com 


***************************************************************************************************
The plugin allows to save 1 or more user flights, then to play them back again ... 
You can then create some traffic around the airport or prepare a complete formation flight,
saving a new flight while you're having a playback of a former one.
 
Features :
- record a flight and playback it again
- record many flights separately and play the whole pack at once
- record a first flight, then record a second flight while the first is in playback, and so forth ...
- record flights with different timers according the level of precision is needed
- start playback flights immediately or when recorded time has been reached (useful with AI traffic)
- have single playback or looping playback
- use user aircraft or generic AI a/c (planes or helicopters)
- models are enlightened to see them farther, gears can retract and extend
- record dynamic objects such as cars, trucks, ships ...
***************************************************************************************************


***************************************************************************************************
History :
- 1.0.2 = added timers 1 sec, 0.5 sec, 0.25 sec, 0.125 sec
- 1.0.3 = added AI lights, key "V" (cycle throught AI vehicles) now allowed
- 1.0.4 = saving a flight while having a previous playback now allowed ; gear up-down
- 1.0.5 = modified last timer 1/12 instead of 1/8 ; Bell is rendered withour rotor blades
- 1.0.6 = timetable dynamic and repetition allowed
- 1.0.6b= generic TRI aircraft allowed - ROTW_FORMATION_v1.0.pod updated
- 1.0.7 = endless motion allowed at the end of the dat file (useful for constant cheap steady motion)
- 1.0.8 = no more adjustments by hand for NFO files in most of the cases 
***************************************************************************************************
Details :
timetable dynamic = AI moves only if the recorded time is reached (first dat file row)
ex : 55375.986000 => 55375 / 3600 = 15.38 decimal hours that stands for 15h and 38*0.6=22 minutes
     you need to be in the scene before 15h22

repetition = first dat file line has a two important flags
ex : timer 0.083000 sec  // code: R030 
     the first is the record timer (here 1/12 sec) => don't change it or BTD
     the second R030 stands for R = repeat action after being stopped 30" after last step
     default is S000 = steady or don't repeat

If you want a repeat action you need to hand change the code in the dat file. 
(S000=steady Rnnn=repeat each nnn sec : respect white spaces)
If you want an endless motion at the end of the data file use this code instead : N000
 
***************************************************************************************************

Installation :




...\FLY\Modules\PC\ROTW_FORMATION_v1.0.n.dll				= plugin
...\FLY\Aircraft\Stuff\ROTW_FORMATION_v1.0.pod				= UI menu
					


***************************************************************************************************
Simple Usage :
The aircraft of your choice has to be selected in the "quicklaunch" dialog and fire up Fly! again.
(to save it in the fly.ini file) or, you can also write it in the fly.ini file
(ex : startupAircraft=WORLD\FLYHAWK.NFO)
Once the aircraft is selected ...
 
1) In Fly, select the menu bar "plugin" then "formation" :  a new menu bar will show up

_Record_
[Adjust hour of day if you want to use the "timing" feature]
2) Record a flight (select a check box for timer value)
3) "record" again to stop

_PlayBack_ (after a record or for a previous saved flight)
4) "play" then "go" or "timing"
5) "go" again or "timing" to stop

Then all the steps back again in reverse to remove the "planes"
... 
6) "play"
7) "formation"

Save a flight during a playback :
- record a first flight (or use a former one)
- "record and play" menu + select a frame timer (check box)
- "Go !!!" menu
- "Go" again to stop then select a new option in the menu bar (record another flight,
play the ones just recorded etc ...) 


**********************************************************************************************+
Timers :
- 1.0 sec for long flights and low horizontal precision 
- 0.5 sec for medium flight, formation flight but with low precision
- 0.25 sec for medium flight, formation flight but with low precision
- 1/12 sec for precision flight like educational flights (I recommand a sole flight saved)

**********************************************************************************************+
Technical informations :

The program will create a new fly! folder called "FORMATION_DATA"
In this folder you'll find a "ini" file, then a certain number of BOY and DAT files
depending on the number of "recorded" flights

BOY file is the plane script file
DAT file is the plane database filled with :
- day time in seconds
- pitch, heading and roll for APISetObjectOrientation
- pitch, heading and roll for APISetObjectBodyVelocity
- pitch, heading and roll for APISetObjectInertialVelocity

or (in 1/12 sec timer)
- day time in seconds
- speed in ft*s for APISetObjectSpeed
- lat, lon and alt for APISetObjectPosition
- pitch, heading and roll for APISetObjectOrientation

When a serie of flighs has been recorded, you should always remove any file from the
folder "formation" before any new recording flight session.
Mainly because old files flights may not work properly with the current flights,
and incidentally because dat files are made for a specific geographic area (around airports)
and it's not a good idea having a lot of memory loaded with useless data.
I use to zip all the files linked to an airport (zip named with the icao code),
included the ini file, in order to install the files only when they are needed for a
specific intent ... then quickly remove them again.


You can also find some "new" NFO files in your current 'world' folder : these NFO are used
by the dll ...
you can remove them if you want after a Fly! session or keep them in place : they are harmless.



**********************************************************************************************+
About NFO files :
Normal aircraft have this kind of NFO (ex: Malibu). The NFO is automatically produced.
<bgno>
	<sign>
	gvew
	<capa>
	0
	<make>
	AI Model
	<CLAS>
	1
	<USAG>
	1
	<_LOD>
	WORLD\TRI1.lod
	<_SVH>
	WORLD\TRI1.svh
	<_AMP>
	BUDDY_FORMATION.amp
	<_WHL>
	WORLD\TRI1.whl
	<_ELT>
	BUDDY_FORMATION.elt
	<_ENG>
	WORLD\TRI1.eng
	<_PSS>
	WORLD\TRI1.pss
<endo>

Instead, for TRI generic aircraft you should CHANGE the produced NFO
like this (ex: FLY2W737)
<bgno>
	<sign>
	gvew
	<capa>
	0
	<make>
	AI Model
	<CLAS>
	1
	<USAG>
	1
	<_LOD> -
	FLY2W737.lod
	<_SVH>
	FLY2W737.svh
	<_AMP>
	BUDDY_FORMATION.amp
	<_WHL>
	BUDDY_FORMATION_TRI_GENERIC.whl
	<_ELT>
	BUDDY_FORMATION.elt
	<_ENG>
	BUDDY_FORMATION_TRI_GENERIC_JET.eng
	<_PSS>
	BUDDY_FORMATION_TRI_GENERIC_JET.pss
<endo>


The TRI generic F16 is quite special. CHANGE the NFO like this
<bgno>
	<sign>
	gvew
	<capa>
	0
	<make>
	AI Model
	<CLAS>
	1
	<USAG>
	1
	<_LOD> - -
	FLY2F16.lod
	<_SVH>
	BUDDY_FORMATION_TRI_GENERIC_JET.svh
	<_AMP>
	BUDDY_FORMATION.amp
	<_WHL>
	BUDDY_FORMATION_TRI_GENERIC_F16.WHL
	<_ELT>
	BUDDY_FORMATION.elt
	<_ENG>
	BUDDY_FORMATION_TRI_GENERIC_JET.eng
	<_PSS>
	BUDDY_FORMATION_TRI_GENERIC_JET.pss
<endo>

