From: Erik H. <er...@eh...> - 2014-01-19 09:28:24
|
On 01/19/2014 12:42 AM, grtuxhangar team wrote: > Hello, Erik > > Ok, i understand why i have some models which get some strange behaviour. > > Looking at your code within jsbsim.cxx i find the following: > > static SGPropertyNode_ptr terrain_nas = > fgGetNode("/fdm/jsbsim/environment/terrain-hight", false); > if (!terrain_nas && material) { > > thus the condition at ("/fdm/jsbsim/environment/terrain-hight", false) > makes fg terrain taken in account or not. > Unfortunately "/fdm/jsbsim/environment/terrain-hight" is not ever > present it depends on the aircraft and the age of the models ( older > have not that property). > > So the condition cannot be hardcoded on it. That's a real pity. I'll see if I can come up with another solution. > > We must define a flag which will be used by every JSBSim Aircraft. > > Bertrand is right the feature could be disabled by default, and the > flag if present will enable the feature > That's the best way to be sure we don't break the others models (jsbsim). This is basically suggesting: the maintainers of 150 aircraft should do some work to work around a problem created by a few other aircraft which took the opportunity to circumvent a missing feature the wrong way. I think that's short sighted an I'm not comfortable with that. Erik -- http://www.adalin.com - Hardware accelerated AeonWave and OpenAL for Windows and Linux - AeonWave Audio Effects software for DJ, Instrumentalist and Vocalist |