P3D v2 Compiler - not doing all AD4 files

[jvile]

It makes sense to lead the ai aircraft all the way down the runway. But if the approach is not in line with the runway AI aircraft will approach left of the runway and never land I fear.

The placement of the Localizer transmitter (large green triangle) in FS has nothing to do with how the AI Planes align with a runway and where it touches down on the runway when landing.

The FS2004/FSX Localizer Transmitter is for the User Plane gauges

As per my CYKA the user plane flying the offset Localizer will intercept the center line of the runway about 1400 ft. from the threshold of runway 26.

 

[gadgets]

Thanks for the interest Don ... can I send you some water ??? 38c at YKA tomorrow !

No need. I expect to still have a cool breeze off Juan de Fuca Straits.

EDIT: Sorry Jim, I didn't notice your post. (At least we're telling the similar stories.)

Getting back to the localizer location issue, one would normally place the pointy end of the localizer feather at the location of the real-world localizer with the feather pointing towards the touchdown point. While placing them at the touchdown point of the runway may facilitate AI (I don't see how since I don't believe AI use ILS for their approaches), doing so will not provide satisfactory operation when flying the user aircraft. Final approach will be extremely sensitive and you'll lose the localizer immediately upon touching down (unless, perhaps, backbeam is enabled).

But if the approach is not in line with the runway AI aircraft will approach left of the runway

The way it works in the case of the 26 localizer (which is located at the near the 08 threshold) is that the lateral offset from the runway together with the heading offset focus causes the localizer beam centerline to cross the runway centerline at the touchdown point. So, the pilot follows the localizer to touchdown and immediately makes to make a minor course correction in order to remain on the runway.

AI should still land at the touchdown point on the runway, regardless of localizer heading offset. In fact, unless the approach code is tweaked, I don't think AI will even be aware of that heading offset. Certainly VFR approaches won't be. Once an IFR approach is completed, I suspect the runway heading becomes prime, so AI should stay on the runway after touchdown. I think you'll find VFR approaches will be straight in regardless of localizer offset/location. If you want AI to follow the offset path, you'll probably have to tweak the approach code and be limited to IFR approaches. Maybe Jim Vile can clarify.

Don

 

[SubLogical]

I have some additional information that might have a bearing on why I'm not getting a full compile to a desktop folder:

1) Win 10 computer ... ADE ver 167.5684 ... airport ver 02.00.5703 ... ADE reinstalled on different drive ... result of compile - no change only CVX and GP completed

2) Win 7 computer ... same same no change " " - same files completed EXCEPT ERRORS see attached

Ken

 

[gadgets]

Ken, since those other guys are asleep by now, I suggest the attribute error is indicative of the wrong compiler. As for the fence errors, it sounds like there's a few fence elements out in the "boonies" somewhere. With those errors the airport .bgl certainly won't be generated. I don't know whether Jon calls the ADE-GP compiler before or after the main compile. But, given its absence, I suspect it doesn't get called if there's an airport .bgl compile failure.

Don

 

[Lane Street]

Ken, looking at the screenie in your last post I see two files, are you expecting to see the *_alt.bgl there?

I would assume (yes, I know the implications of doing so) that ADE will send the *_alt.bgl to ...\Scenery\World\scenery for P3D as it does for FS9 and FSX.

cheers,
Lane

 

[SubLogical]

Don ... I've got the FSX compiler set in the options as I believe that was the setup instruction for P3d ... it surprised me that the P3d wasn't used although I downloaded and placed it inside the LM folder .... am I set up wrong ?

Hi Lane,
Here's the four files that until recently compiled in the D:\Lockheed Martin\Prepar3D v2\Scenery\Addon Scenery\scenery ... if I've got this wrong too I'd better go back haying!!!

Best,

Ken

 

[gadgets]

The "transparent" error may well be due to the FSX compiler being used. I note that Jon's setup says ADE used the FSX compiler for P3Dv2. But, I'm a little suspicious that text may be out of date. I can't be more definitive since I create all my airports for FSX and use some custom software to generate the 6 variations, e.g., FS9, FSX and P3Dv2 - each with custom or stock lighting. You'll probably have to wait until morning in the UK for further detail.

The "fence" errors are almost certainly indicating a problem in the data.

Don

 

[SubLogical]

Well thanks again Don for all the interest ... what I hate about these matters is when the truth comes out it's usually me that's done something stupid!!!!!!!!!!

When I was a coastal dweller I sailed around the Island several times and Juan de Fuca was usually a hair raising challenge ... I wouldn't mind some of the sea air you're getting.

Ken

 

[blaunarwal]

The placement of the Localizer transmitter (large green triangle) in FS has nothing to do with how the AI Planes align with a runway and where it touches down on the runway when landing.

The FS2004/FSX Localizer Transmitter is for the User Plane gauges

As per my CYKA the user plane flying the offset Localizer will intercept the center line of the runway about 1400 ft. from the threshold of runway 26.

Thanks for your ADE picture. Now I understand how it works. There are a few little questions remaining. What is with the glide slope of runway 26 on your CYKA? I can't see it. There's a checkerbox building close to the antenna, on the little road to the antenna in the curve, which could be the glide slope transmitter.
see pic

Next to the checkerbox building for the glide slope is always a small squared grey building Does somebody know, what this is?

What is the building in front of the localizer antenna (2nd)?

I also found the glide slope checkerbox building for 08 at the other side. On the image used importet into ADE it wasn't clearly visible but in Googleearth I could see it.

Dan

P.S. Yes the AI is not using the ILS as I thought. I think the AI just takes the runway and extrapolates an approach out of it's heading and distance. You can clearly see it in CYKA, when using visible glide path. The AI flies next to the glide path.

 

[blaunarwal]

The "transparent" error may well be due to the FSX compiler being used. I note that Jon's setup says ADE used the FSX compiler for P3Dv2. But, I'm a little suspicious that text may be out of date. I can't be more definitive since I create all my airports for FSX and use some custom software to generate the 6 variations, e.g., FS9, FSX and P3Dv2 - each with custom or stock lighting. You'll probably have to wait until morning in the UK for further detail.

The "fence" errors are almost certainly indicating a problem in the data.

Don

I don't have the fence error on my system. I also checked if fault finder has something to report, result no faults. It's just the standard fence used.

Dan

 

[scruffyduck]

The error in the compile above shows that you are not using the P3D v2 latest SDK and compiler. This article explains what bgl files ADE might create and where they go: https://scruffyduck.screenstepslive.com/s/help_docs/m/20268/l/210825-what-bgl-files-can-ade-create Generally they are all compiled to the same place EXCEPT the altitude change which if created goes into scenery\world\scenery. There are reports of users with Win10 getting caught by the User Access Control. Try running ADE 'As Administrator' Make absolutely sure that P3D is not running when you compile - leave it for a minute after it closes to be sure it has released any file locks

 

[blaunarwal]

Here is a link to the SDK 2.5.12946.0 download

 

[jvile]

Thanks for your ADE picture. Now I understand how it works. There are a few little questions remaining. What is with the glide slope of runway 26 on your CYKA? I can't see it.

Last time I checked Runway 26 does not have a glide slope. Rwy 26 is a 2.2 degree offset Localizer with DME.

There's a checkerbox building close to the antenna, on the little road to the antenna in the curve, which could be the glide slope transmitter.
see pic

The checkerbox building houses the electronics for the Localizer. The smaller buildings (1 and 2) are most likely a generator if electricity fails and approach light (ODALS) control box.

P.S. Yes the AI is not using the ILS as I thought. I think the AI just takes the runway and extrapolates an approach out of it's heading and distance. You can clearly see it in CYKA, when using visible glide path. The AI flies next to the glide path.

The AI planes fly the 2.2 degree offset and then make a slight turn to the left and align with the runway (as per my picture) if you add the Localizer approach code into FSX/P3D. Since Runway 26 is a Localizer DME approach code only with no glide slope it is not a ILS so the weather must be IMC for the AI plane to understand the offset to the runway. If the weather is VMC then Flight Simulator uses a hard code straightin approach with no offset. If the Runway 26 offset Localizer is coded as a offset ILS then the AI Plane will fly the 2.2 degree approach in all weather (VMC and IMC) and use the FAF altitude of 4300 ft until over flying YKA NDB.

 

[jvile]

The fence outside the 5000 meter test threshold is a warning only and will not cause a compiler issue.

WARNING: #C1102 CYKA 8358 BOUNDARY_FENCE_VERTEX 5000 Airport (CYKA) has object (BOUNDARY_FENCE_VERTEX) that is 8358 meters from the ARP with a test threshold of 5000 meters! XML line: 12441.


The following error is stopping the XML from being compiled.

ERROR: 2991, 33, The attribute 'transparent' on this element is not defined in the DTD/Schema.INTERNAL COMPILER ERROR: #C2033: XML Parse Error (line, column, error)

What that means is the following line is missing from the BGLComp.xsd file

<xs:attribute name="transparent" form="unqualified" type="stBool" />

You either have a very old P3D Schema file or using one of the FSX SDK compiler and companion Schema's that does not understand transparent.

 

[tgibson]

Hi,

When the localizer is not aligned with the runway, I assume it can either be placed as you had it, or more likely offset at the far end of the runway so the centerline of the approach crosses the threshold of the runway. Move your green arrow in the second image up a ways, until the red line crosses the centerline of the runway at the threshold.

 

[SubLogical]

The wild goose chase has ended I pray!

1) Upgrading the P3d SDK on the Win 7 produced the same compiler errors and compiled the CVX and GP only.

2) On the Win 10, following Jon's instructions I continued to compile only the above files.


Back on the Win 10 where I now work, I spent another couple of hours (too damned hot to be outside anyway) trying every imaginable alternative that entered my feeble old mind and finally got just plain lucky.

The problem was in the settings and my initial obvious choice was the wrong choice !

Thanks to all for staying with me ...

Best,

Ken

 

[blaunarwal]

Last time I checked Runway 26 does not have a glide slope. Rwy 26 is a 2.2 degree offset Localizer with DME.

The AI planes fly the 2.2 degree offset and then make a slight turn to the left and align with the runway (as per my picture) if you add the Localizer approach code into FSX/P3D. Since Runway 26 is a Localizer DME approach code only with no glide slope it is not a ILS so the weather must be IMC for the AI plane to understand the offset to the runway. If the weather is VMC then Flight Simulator uses a hard code straightin approach with no offset. If the Runway 26 offset Localizer is coded as a offset ILS then the AI Plane will fly the 2.2 degree approach in all weather (VMC and IMC) and use the FAF altitude of 4300 ft until over flying YKA NDB.

Hi Jvile

Thanks for your explanations. I will work on it the weekend and try to add the localizer approach code then check, what AI is doing again.

Dan