Quote:
Originally Posted by FG28_Kodiak
A great help would be looking what oggs (and sequence) are usefull for communication. So i can 'translate' it direct in code.
|
I can give you a solution to a minor problem, in one of your scripts you said in comments that there was no "to.ogg" - just use the "2.ogg" instead since it is phonetically the same.
Really sorry I did nothing yesterday. I am changing ISP and since I told them I have been getting cut off every night
I have been looking at these and have some ideas on what needs to be said by the radio operator. For instance, I'm interested in the Point3D position of both aircraft, therefore for example
if(pilot.height < aiairgroup.height)
{
//use "climb.ogg" & "2.ogg" angels i;
}
else
{
//use "descend.ogg & "2.ogg" angels i;
}
There are also direction oggs such as "turn right.ogg" but I don't know how sophisticated this can be. Unless it is easy to work out interception vectors then that is probably too much work or a longer term project. It is not needed for now
I would like to know more about the sectors and how you intend to have this working. I have some input for this. There are a few important behaviour requirements for this if possible, briefly:
1. No aircraft reported under 600m (Chain Home Low min operating height)
2. RDF range as far as the French coast (and into France some 50 miles in the Pas De Calais area) A range map is available on Wikipedia
I have an idea for a 4 minute delay but it's probably complicated and not the first thing to implement. It would involve the radar constantly working behind in the script and storing 4 minute old data in variables, then releasing that to the user on request instead of current data. Perhaps if the RDF event fired every minute transparently and the resulting information string stored and passed on every minute into a new variable until the 4th minute, then this was accessed and played to the player. (hope that makes sense)
Speak later ~S~