• 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.

base file not accessible error

From your earlier screenshots, it appears you are attempting to use FSX models. However, from the testing I have just done, it appears I have broken something in the creation of FSX models when I added the new P3D capability. Or, perhaps the FSX PAPI model never worked.

Using FSX models, while the lights didn't seem to work as intended during my testing, (perhaps they are always being displayed underground), the 3D models appear in the correct place at 0 elevation AGL. So, I have no idea where your 101' offset is coming from. It's certainly not be caused by the library .bgl file.

Using FS9 models (as recommended in the user manual unless you have special transparency requirements - which would not seem to be the case), operation is as intended.

The reason I had difficulty before in displaying the FSX model had nothing to do with the problem noted above; it was a guid issue. Re your 101' offset, are you sure the guid assigned to your PAPI is unique and that your IS parameters are correct?

I'm not going to go to the trouble of making screenshots. You already know how PAPI's work. If you want to see it in operation, download any of my airports from http://stuff4fs.com and install with custom lighting.

Use FS9 models, position them properly and all should be well. Make sure your guid is unique and specify a method of pilot control, e.g., transponder, code 0066 (that shouldn't be necessary, but just in case ...).

Don
 
I have finally figured out what is going on with FSX models in Development Release 2.0.03.

Development Release 2.0.0.3 was a beta release for P3Dv2 compatibility - which requires that ALFT models be handled as simobjects under the control of Simconnect. While the new development release was intended to have all the capability of version 1.1.03, that didn't quite happen. Because my focus was on P3Dv2 compatibility, I neglected to reinstate the BGL code that controls the lights for FSX models when the models are used as scenery. Consequently, while the FSX 3D models display correctly, there are no lights.

I will be working on a new development release as my time permits to reinstate the BGL code necessary to display lights on FSX models in a non-Simconnect configuration.

Also, in my responses above, I stated that AFLT applies an offset of 100' to make lights disappear. That offset is, in fact, 100m.

Don
 
You must log in or register to reply here.
Back
Top