• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

P3D v2 Compiler - not doing all AD4 files

Messages
115
Country
ca-britishcolumbia
I am only getting a partial compile (two bgls) on an AD4 that contains 4 bgls.

The four are:- CKYA_ADEX_TST.bgl, ...TST_Alt.bgl, ...TST_CVX.bgl, ...TST_GP.bgl

The two that compile are:- TST_CVX.bgl and TST_GP.bgl

There are no errors. The AD4 was created by a friend and his compiler compiles all four files.

What could I be doing wrong that would cause this compile shortfall?

Ken
 
I should have mentioned a "Black Box" notification and the "Background Imagine not attached" which I clicked "compile" and "ignore" in that order.
 
When you click compile now open the more options button. In Conditional Compile make sure all 4 boxes have checkmarks.
 
Hello Jim,

As you can see from the pic all four buttons are checked.

Appreciate your interest,
Compile Options.png
Ken
 
Ken,
Can you click on the little red box in the bottom left corner and see what that says........
 
Ray is right - you have compiler errors and that would stop some parts of the compile happening. Perhaps you should attach the .ad4 project file here to a post so that others can confirm what is happening
 
Ahhh the little red box in the corner tells the story even though I don't know what it means ... see attached pic
Error Found.png
 
The error suggests to me I may have the wrong P3d file in use ... I added "Projects" into the ADE165 "P3d" directory and I see there is an empty "Projects" file in the "P32" that seems to be referred to in the error ... Is this my mistake?

Ken
 
It means that ADE is looking for a file called Plate.mdl in the path shown. Without it the compile fails
 
The error suggests to me I may have the wrong P3d file in use ... I added "Projects" into the ADE165 "P3d" directory and I see there is an empty "Projects" file in the "P32" that seems to be referred to in the error ... Is this my mistake?

Ken

No It means that the project contains a reference to a user model and ADE can't find it. This is a common problem if you open someone elses project and they have not supplied the models. You can go to Lists > Models and see if you can either remove the requirement for the model or assign the right path to it.
 
I seem to have spoken too soon regarding a resolution of the compile failure to include all files.

The offending "plate" model was removed and the AD4 compiled the two missing files (the main bgl and the Alt bgl) but did not overwrite the CVX and GP which were retained from the previous compile. This was confirmed by the different dates in the compiled scenery folder.

I deleted all the compiled files and tried again "fresh" and only the CVX and GP compiled. I tried compiling to a New Folder Desktop with the same results. Something went awry after my deletion of the first compile although there are no errors and the little box in the bottom left corner shows green.

I am attaching the AD4 and will send the Log in the hope that more experienced users will spot the problem.

Ken
 

Attachments

Ken, don't know what you mean by "the offending plate model". But, I've just compiled your airport and all expected files were generated. Perhaps you have told ADE to place them elsewhere.

I couldn't help but notice the unusual placement of your localizers (i.e., on the runway surface). Generally localizers are well off the ends of the runways. Also the Rwy 08 localizer heading is about 2 degrees different from your runway heading, which is going to make bad-weather landing a little difficult unless it is offset from the runway centerline.

Finally those aprons in the northeast corner are in an unflattened area and hence, may create hills or valleys depending on the mesh elevation in that area. Of course, that may be your intent.

Don
 
Hi Don

The scenery was made by me on an initial project from Ken. The localizers are according to the manuals always on the opposite side. Maybe you can explain me why. Since the approach is about 2 degrees rotated to the runway line up, the localizer hast to be on the touchdown point or the aircraft approaching Rwy 8 will be flying a path left of the runway, coverging with the runway at the 26 end, where is to late to land. The rotation is according to the real world setup, allowing to fly over the ndb Kamloops, which is set in the default scenery.

Yes the aprons in the north east, simulating the collecting ponds for the fuel tanks. Have you a better idea for this?

I already removed the model plate.mdl. It was a remains of trying to add an nameplate of Kamloops. But in the end, it was easier to place it directly with the wizard from ModelConverterX, in its own bgl. I have no clue, why Ken can't compile it.

I added the ad4 file to have a look at.

Dan
 

Attachments

The localizers are according to the manuals always on the opposite side. Maybe you can explain me why.
So that the localizer is available for the entire runway length. Placing them where you have, your 08 localizer position is at the touchdown point for 26. I think you may have them reversed.

In real life, the 08 localizer is directly off the end of 08 (i.e., east of the runway) very close to the fence. The localizer for 26 is offset about 300ft from the runway centerline and is positioned laterally about 1000' inside the threshold of Rwy 08. My chart (Canada Air Pilot) states a 2.2 degree offset, which is apparent from aerial photos. Both are clearly visible in those positions on both Google Earth and City of Kamloops maps.

Yes the aprons in the north east, simulating the collecting ponds for the fuel tanks. Have you a better idea for this?
Its not a matter of a better idea. It may be correct as it is. I was simply pointing out that the area under and immediately adjacent to those aprons would be automatically flattened to the elevation of the ARP, perhaps creating hills or valleys depending on mesh elevation in that area. If that is what you intend, nothing needs be changed. If it's not what you intend, then you may want to extend your flatten into that area.

Finally, I meant to mention before that I created the six flashing beacons around CYKA for a commercial flight-training customer a while back. Ken is welcome to have those to facilitate night-time operation.

Don
 
Hello Dan and Don,

I appreciate this may be a desperately weak contribution but what is the likelihood of this being a Win 10 anomaly, P3d or even an ADE corruption. I can't see these since everything seems to be working including the partial compile of the other two files.

The real mystery is why it compiled properly right after I loaded Dan's most recent AD4 and then quit ... but I'm concerned about the unexpected white sheet of data asking me if I wanted to continue transferring the data (?) after I had deleted the CVX and GP from the scenery file ... as they were from a previous compile. I answered no and when this msg vanished I went ahead with a new compile to have all files on the same date and you know the rest of my story.

Ken
 
Ken, I'm afraid I can't be much help with the "why" of your situation. My intent in replying initially was to confirm that ADE created the complete file set for me - at least all the members I anticipated were generated. (The other stuff was something that I noticed just before pressing the Post Reply button and offered in the vein of being helpful.)

I haven't switched to Win 10 (and don't plan to in the near future). But, frankly, Win 10 is unlikely to have "eaten" your files. You can also dismiss P3D if it isn't running when you compile.

Don
 
Oh I mixed up things. The rwy 26 localizer is rotated 2.2 degrees from the rwy centerline. So the green arrow for 26 is placed on the 26 touch down point.

5TKmUZE.jpg



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. I drawed the flight path of an ai aircraft approaching 26 rotated 2.2 deg. So they touchdown somewhere in the dirt?

wVkcTVd.jpg)

wVkcTVd.jpg


Do you suggest to place the it, where the real world emitters are placed?

Edw9dFz.jpg


About the aprons, it's maybe not correct, since I got some trenches now. But on the other hand, the fuel farm is certainly a flat area. I have no better way to do this. Since you will not taxi around there, it will not be visible. But better technics or new ideas are always welcome.

Dan
 
Ken, I'm afraid I can't be much help with the "why" of your situation. My intent in replying initially was to confirm that ADE created the complete file set for me - at least all the members I anticipated were generated. (The other stuff was something that I noticed just before pressing the Post Reply button and offered in the vein of being helpful.)

I haven't switched to Win 10 (and don't plan to in the near future). But, frankly, Win 10 is unlikely to have "eaten" your files. You can also dismiss P3D if it isn't running when you compile.

Don

Ken, I think that's the best idea, why you don't get a new afcad bgl, that P3D is running and also have a look at the compile path. It works perfectly on my system. Did you reinstall ADE now? I may help to fix things, because you have to reconfigure ADE. Of course you can also just check the settings. P3D needs to use its own SDK compilers. Have you installed the p3d2 SDK?

Dan
 
Well Dan I'm dead in the water at this point and I think I've got my house in order ... including the p3d sdk.

I've managed to compile alright in my present format until recently so perhaps an ADE reinstall might be worth a try. I'll keep you posted.

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

Ken
 
Back
Top