![]() |
|
IL-2 Sturmovik The famous combat flight simulator. |
![]() |
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]() Quote:
Quote:
Quote:
Otherwise its up to you as the mission builder to put them where you want to depending on the missions objectives. I suggest testing the Lorenz placement for the outer marker and inner marker indicators as suits the type used. Last edited by KG26_Alpha; 01-26-2012 at 07:31 PM. |
#2
|
|||
|
|||
![]()
To partially answer my own question(Are there only short and long runways of fixed lengths), I did the following on the New Guinea map:
Fully zoomed in on each runway, place a waypoint at the beginning and end. Right on the edge, using the lines between the tiles or mats to align them. A pair of independent waypoints per runway that are only connected to eachother, not the other waypoints/runways. Set the speed for each waypoint to 6kph using a text editor. Looking at the second waypoint in each set, noted the time. At 6kph, 1km takes 10 minutes, so an arrival time of 12:17(mission starts at 12:00) makes for a distance of 1700 meters. Using this method, I determined the runway length for all airfields(Note that there is a margin of error for the few grass runways, as the beginning, end and centerline are hard to determine): Vivigani: 1700m x2 (IRL 2000m) Garuahi LG: 1200m Turnbull LG: 1600m Gurney Airfield: 1600m No. 2 Strip: 1600m Sagari LG: 1200m DOB 1: 1600m DOB 3: 1600m New Strip: 1200m Old Strip: 1600m Soputa: 1600m DOB 2: 1200m Unknown(Between Fighter Strip and DOB 2): 1200m Fighter Strip: 1600m DOB 4: 1200m POP3: 1600m Kila Airdrome: 2200m Jackson Airdrome: 1700m Wards Airdrome: 1700m x2 Durand Airdrome: 1600m Schwimmer Airdrome: 1600m Berry Airdrome: 1600m Boera Field: 1600m This gives us the following lengths: 1200m, 1600m, 1700m and 2200m. I've checked Vivigani and Garuahi LG, and neither have historically accurate runways. Even then, using historical data for beacon placement is only possible for a small number of airfields. Measuring this is relatively simple, though time consuming. This method could be used to determine the beacon location. However, as there are so many variables involved, I believe this would be inaccurate at best. I just need the hard data, as already supplied in the manual for the regular lorenz beacon, of the two other landing beacons. |
#3
|
|||
|
|||
![]()
I didn't find any data except for Lorenz blind landing system.
|
#4
|
|||
|
|||
![]() Quote:
At this point, I believe only someone with access to the sourcecode could find the proper values. Unless they're in a design document somewhere. Either way, if someone from Daidalos Team has the time to look into this, it would be most appreciated. Though I do realize other issues have priority. |
#5
|
|||
|
|||
![]()
Maybe I'm missing the point. It might be easier to place if the center of the icon represented the inner marker, which I think is touchdown. Then, placing the object in FMB might require nothing more than making sure that, in 3D mode, the building is off the runway when the inner marker is aligned with touchdown point. If it can't be done, that particular Lorenze can't service that runway.
|
#6
|
|||
|
|||
![]()
I will check with the coder of Lorenz and ILS.
|
#7
|
|||
|
|||
![]() Quote:
I would instead suggest a line at the expected runway start. This would also be useful for aligning the Lorenz with the angle of the runway. Having icons where the outer and inner markers are could also be useful. If these are combined with objects to represent the markers, they could be placed manually. This prevents problems with terrain elevation that would occur if the marker objects were part of the beacon model(I.E. floating or underground marker placement). Thank you IvanK. I'm looking forward to finding out. |
![]() |
|
|