The first shadow implementation allowed to prefix object names with "noshadow" to exclude them from shadow generation. This was considered a bad idea from the beginning, as a name is a name and shouldn't contain instructions. That's why this method was deprecated very early, and a "noshadow" animation was written as the recommended way.
The upcoming release will still support the prefix, but the next (shadow supporting) release after that will not. So this release cycle should be used for the migration of those aircraft which still use the prefix. I added an error message that's output whenever an object with a noshadow prefix is found by the shadow occluder. Sorry for the inconvenience. :-) m. ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
