Detlef Faber wrote: > Am Dienstag, den 19.05.2009, 21:56 +0200 schrieb Melchior FRANZ: > >> * Detlef Faber -- Tuesday 19 May 2009: >> >>> This means while trying to pass beneath a bridge, geo.elevation returns >>> the heigth of thebridge which will obviously stop the walker from moving >>> ahead. >>> >> But geo.elevation() has an optional third argument that defines from which >> altitude >> down the intersection test should be made. Default is 10 km, but you can >> start >> from, say, 1.5 m above the walker's altitude. If there's an intersection, >> then >> s/he can climb up, otherwise it's an obstacle. And that should also work in >> hangars or under bridges. >> >> > I see, I should have monitored the CVS commit messages better :-) >
I missed that one too. Thank you Melchoir! I'll be busy making updates to all my models. >> PS: yes, I forgot to mention this little detail in the geo.nas header. ;-) >> When was this fixed? Does 1.9.0 include this in geo.nas? Stewart ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
