Makerwys 82 and Threshold offsets

[Galager]

Hi,

When I read files generated by MakeRwys for P3D V4, the runway threshold offset value is always 0, even on runways with actual displaced threshold.

Do you have same results?

Jean

[Pete Dowson]

Comparing P3Dv4 results to what? Default airports or add-ons?

MakeRunways hasn't changed at all, except to enable it to determine where the SCENERY.CFG file is, or using the Lorby add-on manager to generate the version placed into the P3D folder which then includes scenery layers added by the new XML files.

Also, most if not all of the default airport BGLs are unchanged in P3Dv4, so it should surely give the same results -- same data, same program reading it.

Can you find an example which was correct in P3Dv1-3 or FSX but which, for the same BGL files, is not?

Pete

 

 

[Galager]

Hi Pete, 

Thanks for your reply.

Example Airport ICAO code PARD, both runways have displaced thresholds.

Makerwys version  < 82, see runways.txt below for PARD

Airport PARD :N68:01:53.3874  W162:54:08.9516  974ft
          Country Name="United States"
          State Name="Alaska"
          City Name="Red Dog"
          Airport Name="Red Dog"
          in file: Scenery\0000\scenery\APX04070.bgl

          Runway 2 /20  centre: N68:01:53.3874  W162:54:08.9516  974ft
              Start 2 : N68:01:32.0395  W162:54:55.0844  974ft Hdg: 39.0T, Length 5753ft
              Computed start 2 : Lat 68.025360 Long -162.915754
              Offset Threshold primary: 300 feet
              Start 20 : N68:02:14.7352  W162:53:22.8185  974ft Hdg: 219.0T, Length 5753ft
              Computed start 20 : Lat 68.037628 Long -162.889208
              Offset Threshold secondary: 300 feet
              Hdg: 39.000 true (MagVar 19.000), Gravel, 5753 x 120 ft
              *** Runway *** PARD0020 Lat 68.025360 Long -162.915756 Alt 974 Hdg 20 Len 5753 Wid 120
              *** Runway *** PARD0200 Lat 68.037628 Long -162.889206 Alt 974 Hdg 200 Len 5753 Wid 120
          COM: Type=3 (UNICOM), Freq=122.80, Name=""
          FSM A/P PARD, lat=68.031502, long=-162.902481, alt=974

Now same file but produced with MakeRwys 82

Airport PARD :N68:01:53.3874  W162:54:08.9516  974ft
          Country Name="United States"
          State Name="Alaska"
          City Name="Red Dog"
          Airport Name="Red Dog"
          in file: Scenery\0000\scenery\APX04070.bgl

          Runway 2 /20  centre: N68:01:53.3874  W162:54:08.9516  974ft
              Start 2 : N68:01:32.0395  W162:54:55.0844  974ft Hdg: 39.0T, Length 5753ft
              Computed start 2 : Lat 68.025360 Long -162.915754
              Start 20 : N68:02:14.7352  W162:53:22.8185  974ft Hdg: 219.0T, Length 5753ft
              Computed start 20 : Lat 68.037628 Long -162.889208
              Hdg: 39.000 true (MagVar 19.000), Gravel, 5753 x 120 ft
              *** Runway *** PARD0020 Lat 68.025360 Long -162.915756 Alt 974 Hdg 20 Len 5753 Wid 120
              *** Runway *** PARD0200 Lat 68.037628 Long -162.889206 Alt 974 Hdg 200 Len 5753 Wid 120
          COM: Type=3 (UNICOM), Freq=122.80, Name=""
          FSM A/P PARD, lat=68.031502, long=-162.902481, alt=974

 

Offset Threshold information is missing as you can see.

If I check on the r5.bin, this offset information is also never set, always showing 0 feet.

 

Jean

[Pete Dowson]

4 hours ago, Galager said:

Example Airport ICAO code PARD, both runways have displaced thresholds.

Hmm. and the same file read by different MakeRunways versions, produceds those differences, both with the same Sim?

That is indeed strange, as nothing has been changed in its actual BGL processing, only in the file identification.

I'll make time to check this out later today, or maybe tomorrow. Thanks for the example.

Pete

 

[Pete Dowson]

I've fixed this for BGLs compiled with the usual tools, but I found that the reason it didn't work in 4.82 was that I was trying to cope with BGLs compiled using the latest P3Dv4 SDK tools, and made an error.

For now, it won't find threshhold offsets, VASI and Approach Light information for such newer BGLs. Until the new formats can be worked out this is probably one of several areas which will not work.

Luckily, 99% of all scenery currently in use, including the default P3D4 sceneries, still use the older tools.

Pete

 

[Galager]

Great thanks Pete!