Hi, ok, it does work. It does so at least with osg (2.1.8) simgear and fg cvs as of 20070828 and osgviewer (is it default now?)
Taking into account the hint from http://permalink.gmane.org/gmane.games.flightgear.devel/42953 trying to follow model-howto.html and ripping apart Syd's b1900d, I came up with the attached patch as a proof of concept thing. Some notes: - I found that in order to make the example from model-howto.html work ( starting at "To make a texture replaceable at runtime") one has to specify a valid (i.e. loadable) <texture> in the material animation. - I was not able to sort that stuff out (in simgear's SGMaterialAnimation.cxx). Something about the texture-prop only being considered in UpdateCallback(), osgDB filepaths etc. went over my head, so I'm not sure if there's a bug in the code or documentation or my head. - [ac specific, perhaps Syd is interested in] I roughly sorted out all the objects I think are relevant for livery mapping. I'm not sure if there should be some constraints about the ordering. Also I don't know what effect that has on the plib version. Finally, the line I put into stuff.nas should go into something like systems.nas, but I wanted to keep the changes as separated as possible for testing. - maybe one could think about object-specific nodes below "/sim/model/livery" instead of "all" to be more flexible. (or more suitable names/paths of course) HTH K. Hoercher
livery.patch
Description: Binary data
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
