AFLT3 Final Beta Release Posted

gadgets

Resource contributor
#81
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
 

gadgets

Resource contributor
#82
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
 

gadgets

Resource contributor
#83
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
 
Top