* gerard robin -- Monday 03 December 2007:
> i guess we can keep these deprecated .
Yes, they'll work as usual during this release cycle. But they'll
issue an error message in fg/plib, which you might want to avoid.
As fg/osg doesn't yet support shadows at all, there's also no
error message. But a
On lun 3 décembre 2007, Melchior FRANZ wrote:
> For those who want to avoid the message already now, here's a list
> of models still using the "noshadow" prefix. Note that some objects
> use a "noshadow" *postfix*. This doesn't cause error messages, but
> it will also not discard shadows. Never has
For those who want to avoid the message already now, here's a list
of models still using the "noshadow" prefix. Note that some objects
use a "noshadow" *postfix*. This doesn't cause error messages, but
it will also not discard shadows. Never has.
./A-10/Models/A10-004-015l2.ac
./A-6E/Models/A-
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" animat
4 matches
Mail list logo
