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

AFLT3 Final Beta Release Posted

I have developed a simple fix for the issue that seems to work, i.e., bias the display of the light (simObject) towards the user by 1 cm, which should have no apparent effect other than allowing the light to display in front of the 3D model.

I hope to re-release overnight.

Don
 
Development Release 3.0.07 posted to http://stuff4fs.com. It moves the simobject 1 cm further away from the front of the 3D model to compensate for slight differences in position between the display of the 3D based models and their simobject-based light sources. This fix appears to fully address the problem - at least at your airport Michael.

Don
 
It appears the situation reported yesterday by Michael, i.e., lack of registration between some 3d models (scenery objects) and their simobject-based light counterparts is best described as "that's the way it is". In yesterday's release (3.0.07), I applied a fixed 1 cm Y-bias to the simobject position to ensure it was in front of the 3D model. That seemed to be adequate in Michael's situation.

However, given that the situation is outside the control of AFLT, I'm concerned that a fixed amount of bias may not be adequate in all instances. To that end, I have added the ability for users to add a bias (1->n cm.) to each of approach lights, PAPI/VASIs and wigwags (the only models that can be so affected).

Should the situation occur, it's a simple matter to specify a bias for the relevant category and re-make the object library.

I have just posted Development release 3.0.08 to http://stuff4fs.com.

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