More than 2 runways airbase in Nevada
Posted: 2008-03-12 16:21:57
I discussed this idea of mine in the airbase for Nevada thread. Now that the alpha station.dat file is done and support ILS & radio frequencies, it's time to try and see if the idea is workable
As a reminder, the idea is to place two F4 airbase close another to have quite larger airbases. Lots of airbases in real Nevada are multiple runways and we know we will never reach the same level as the real ones in F4 due to the minimal number of generic we have. Still we can try to make compromises that are closer to the reality...
Granted the airbases we place close another will not be connected, each will have it's own IDs, runways, building, freqs for communication, ILS...
- ILS is not a problem since it's RWY dependent in OF. Not a concern with AF & RV since it's not implemented realisticaly
- Radio coms is plausible since often large airports have multiple tower freqs depending on the quadrant, so we are good with that aspect too
- Two names , not a problem. We can make LAX north and LAX south
Let's start by something simple
KLAX (Los Angeles) is normaly a 4 (almost parralel) runways airport.
IRL it's something like a double 06/24 and a double 07/25.
In F4 for the moment it's assigned as a double 05/23
None of those are availaible in F4 but we do have two double 05_23 airbase model
So let's say we stick those two models together close by and see what happens
By using two different models (ID 978 and ID 1779) we can arrange the layout so we get minimal obstruction with Objects... Of course we will probably have tiles problem and some specific tiles might be required in the long run
Here's what it could give:
Other combinations are possible, like 2x ID978 or 2x ID 1779
Next step is to actually try that with the current Nevada version
Comments welcome
As a reminder, the idea is to place two F4 airbase close another to have quite larger airbases. Lots of airbases in real Nevada are multiple runways and we know we will never reach the same level as the real ones in F4 due to the minimal number of generic we have. Still we can try to make compromises that are closer to the reality...
Granted the airbases we place close another will not be connected, each will have it's own IDs, runways, building, freqs for communication, ILS...
- ILS is not a problem since it's RWY dependent in OF. Not a concern with AF & RV since it's not implemented realisticaly
- Radio coms is plausible since often large airports have multiple tower freqs depending on the quadrant, so we are good with that aspect too
- Two names , not a problem. We can make LAX north and LAX south
Let's start by something simple
KLAX (Los Angeles) is normaly a 4 (almost parralel) runways airport.
IRL it's something like a double 06/24 and a double 07/25.
In F4 for the moment it's assigned as a double 05/23
None of those are availaible in F4 but we do have two double 05_23 airbase model
So let's say we stick those two models together close by and see what happens
By using two different models (ID 978 and ID 1779) we can arrange the layout so we get minimal obstruction with Objects... Of course we will probably have tiles problem and some specific tiles might be required in the long run
Here's what it could give:
Other combinations are possible, like 2x ID978 or 2x ID 1779
Next step is to actually try that with the current Nevada version
Comments welcome