Issue makerwy ENHF

[bradimarte]

Hi,

I've used last version makerwy 4.8.4 for P3Dv4.2 but I've found that the utility not see the ENHF airport of ORBx.

bye

Rudy

[Thomas Richter]

Hi,

did you check the manual and installed the Addon Organizer from http://www.lorby-si.com ?

Thomas

[bradimarte]

Hi,

sure, I have used Addon Manager before  makerwy, and I have more or less 2000 scenery included many add-ons but I seems that only ENHF is not recognized from makerwy.

bye

Rudy

 

[Thomas Richter]

Hi,

you will need to send then the Runways.txt (MakeRwys log) file and the MakeRwys_Scenery.cfg file for more information. Pleas zip and attach them.

Thomas

[bradimarte]

Hi,

I have seen that in the log file there is ENHF but in the r4.csv or r5.csv (that I use for internal addon) ENHF is missing, so in any case I can only attached  MakeRwys_Scenery and r5.csv because the other is over 220 Mbyte.

bye

Rudy

 

Desktop.rar

[Pete Dowson]

29 minutes ago, bradimarte said:

I have seen that in the log file there is ENHF but in the r4.csv or r5.csv (that I use for internal addon) ENHF is missing

It sounds like there is something wrong with the AFD (airport facility details) BGL file. We don't need to whole log (Runways.txt). Just find all the sections for ENHF, by searching, and select and copy those into another text file. There will be the default one AND, hopefully, the add-on one. That selection should be short enough to show in a message here. (Use the <> button above the edit area to paste it in, so it looks boxed as I have done below).

The ENHF from the default scrnery shows up (I don't have an add-on for that airport0. here's the runways.xml entry for it:

<ICAO id="ENHF">
<ICAOName>Hammerfest</ICAOName>
<Country>Norway</Country>
<City>Hammerfest</City>
<File>Scenery\0600\scenery\APX54060.bgl</File>
<SceneryName>0600 Base</SceneryName>
<Longitude>23.668612</Longitude>
<Latitude>70.679726</Latitude>
<Altitude>260</Altitude>
<MagVar>8.000</MagVar>
<Runway id="05">
<Len>2887</Len>
<Hdg>47.980</Hdg>
<Def>Asphalt</Def>
<ILSFreq>111.35</ILSFreq>
<ILSHdg>47.98</ILSHdg>
<ILSid>HA</ILSid>
<ILSslope>0.00</ILSslope>
<ILSname>LOC/DME 05</ILSname>
<Lat>70.677422</Lat>
<Lon>23.658688</Lon>
<FSStartLat>70.677498</FSStartLat>
<FSStartLon>23.659031</FSStartLon>
<ClosedLanding>FALSE</ClosedLanding>
<ClosedTakeoff>FALSE</ClosedTakeoff>
<ApproachLights>ALSF1</ApproachLights>
<EdgeLights>HIGH</EdgeLights>
<CenterLights>NONE</CenterLights>
<CenterRed>FALSE</CenterRed>
<EndLights>TRUE</EndLights>
<REIL>FALSE</REIL>
<Touchdown>TRUE</Touchdown>
<Strobes>15</Strobes>
<LeftVASI>PVASI</LeftVASI>
<LeftVASIbiasX>21.04</LeftVASIbiasX>
<LeftVASIbiasZ>170.08</LeftVASIbiasZ>
<LeftVASIspacing>91.45</LeftVASIspacing>
<LeftVASIpitch>4.70</LeftVASIpitch>
<RightVASI>NONE</RightVASI>
<ThresholdOffset>135</ThresholdOffset>
<PatternTakeOff>Left</PatternTakeOff>
<PatternLanding>Left</PatternLanding>
<PatternAltitude>305</PatternAltitude>
</Runway>
<Runway id="23">
<Len>2887</Len>
<Hdg>227.980</Hdg>
<Def>Asphalt</Def>
<ILSFreq>110.70</ILSFreq>
<ILSHdg>227.9</ILSHdg>
<ILSid>HF</ILSid>
<ILSslope>0.00</ILSslope>
<ILSname>LOC/DME 23</ILSname>
<Lat>70.681847</Lat>
<Lon>23.678528</Lon>
<FSStartLat>70.681786</FSStartLat>
<FSStartLon>23.678185</FSStartLon>
<ClosedLanding>FALSE</ClosedLanding>
<ClosedTakeoff>FALSE</ClosedTakeoff>
<ApproachLights>RAIL</ApproachLights>
<EdgeLights>HIGH</EdgeLights>
<CenterLights>NONE</CenterLights>
<CenterRed>FALSE</CenterRed>
<EndLights>FALSE</EndLights>
<REIL>FALSE</REIL>
<Touchdown>FALSE</Touchdown>
<Strobes>5</Strobes>
<LeftVASI>PVASI</LeftVASI>
<LeftVASIbiasX>21.04</LeftVASIbiasX>
<LeftVASIbiasZ>169.17</LeftVASIbiasZ>
<LeftVASIspacing>91.45</LeftVASIspacing>
<LeftVASIpitch>5.50</LeftVASIpitch>
<RightVASI>NONE</RightVASI>
<ThresholdOffset>138</ThresholdOffset>
<PatternTakeOff>Left</PatternTakeOff>
<PatternLanding>Left</PatternLanding>
<PatternAltitude>305</PatternAltitude>
</Runway>
</ICAO>

Similarly the data is all in the Log and in the R4 and R5 CSV files, for example (R5):

ENHF,0050,70.677422,23.658688,260,47.980,2887,111.35BD,98,8.000,70.679634,23.668608,135,,
ENHF,0230,70.681847,23.678528,260,227.980,2887,110.70BD,98,8.000,70.679634,23.668608,138,,

So, it seems you addon ENHF not only deletes the default details, but for some reason fails to add its own in a normally recognisable way.

Maybe they are exploiting something in the BGL system which allows them to do unusaul things -- eg are the runways sloped? If they've made them sloped they may not be using actual runway definitions. See if the runways are properly listed and selectable in the World-Go To Airport menu in P3D.

When you have the log data, we can see what is going on. Maybe I could examine the AFD file to see what is wrong.

Pete

 

[bradimarte]

I have chose to insert all the details of ENHF from log file into a new file .txt attached here (because are too much), and yes the runway is slopped. It's is the last version of ORBX product.

bye

Rudy

Nuovo documento di testo.txt

[bradimarte]

I have forgot to answer that yes, P3D see the airport in World-Go to Airport

[Pete Dowson]

13 minutes ago, bradimarte said:

I have forgot to answer that yes, P3D see the airport in World-Go to Airport

Not the airport, the runways at the airport. Can you use Go To Airport to place your aircraft on the runway ready for takeoff?

Pete

 

[Pete Dowson]

The runways are seen:

         Runway 23 /5  centre: N70:40:53.6798  E023:40:38.0603  263ft
              Runway 23  closed for landing and take-off
              Runway 5  closed for landing and take-off
              Hdg: 55.980 true (MagVar 8.000), Asphalt, 16 x 0 ft
              Primary ILS ID = HA
              Primary ILS: HA  111.35 Hdg: 56.0 , Flags: DME BC "LOC/DME 23"
              Secondary ILS ID = HF
              Secondary ILS: HF  110.70 Hdg: 236.0 , Flags: DME BC "LOC/DME 05"
 
but (a) they are both closed for takeoff and landing, and
(b) there are no "start" positions defined -- i.e. places to put the aircraft for takeoff.

The defaults (which have been deleted by the addon) has:

         Runway 5 /23  centre: N70:40:46.6826  E023:40:06.9889  260ft
              Start 5 : N70:40:38.9728  E023:39:32.5123  260ft Hdg: 56.0T, Length 2887ft 
              Computed start 5 : Lat 70.677422 Long 23.658688
              Offset Threshold primary: 135 feet
              Start 23 : N70:40:54.3925  E023:40:41.4640  260ft Hdg: 236.0T, Length 2887ft 
              Computed start 23 : Lat 70.681847 Long 23.678527
              Offset Threshold secondary: 138 feet
              Hdg: 55.980 true (MagVar 8.000), Asphalt, 2887 x 98 ft
              Primary ILS ID = HA
              Primary ILS: HA  111.35 Hdg: 56.0 , Flags: DME BC "LOC/DME 05"
              Secondary ILS ID = HF
              Secondary ILS: HF  110.70 Hdg: 236.0 , Flags: DME BC "LOC/DME 23"
              *** Runway *** ENHF0050 Lat 70.677422 Long 23.658688 Alt 260 Hdg 48 Len 2887 Wid 98 ILS 111.35, Flags: DME BC
              *** Runway *** ENHF0230 Lat 70.681847 Long 23.678528 Alt 260 Hdg 228 Len 2887 Wid 98 ILS 110.70, Flags: DME BC

You see that there are Start points for both runways. Without those MakeRunways cannot compute all the data needed.

Pete

 

[bradimarte]

I seen, at this point I understood that the issue is of ORBX. I will advice them for this airport.

Thank's for all

bye

Rudy

 

[GHD]

10 hours ago, bradimarte said:

Quote

I seen, at this point I understood that the issue is of ORBX. I will advice them for this airport.

One cannot have sloping runways.