Hi Ulrich
I think you are right in what was going wrong but for some reason the prox node
does not complain when I delete the file and rewrite it, the key is to delete
it first. The material-modified models can be saved and reloaded with this code:
Code:
void M_model::Update_files(void)
{
HI Patrick,
I'm not aware of any problems with writing of osg::Material objects to a
.osgb file.
Using the spaceship.osgt model from OpenSceneGrapph-Data, that contains
osg::Material instances, I have just done the test:
osgconv spacedship.osgt spaceship.osgb
osgviewer spaceship.osgb
Hi Patrick,
Quoting Patrick Keenan pk...@hotmail.com:
I have an osg::ProxyNode model that I change the material on then I
try to update the file itself so that next time I run the program
the changes persist. If I save it to my_model.osgb then the next
time I go to open it
Follow up:
If '_prox_node' the the ProxyNode referencing the file 'frame_6' then
you will end up creating an infinite recursion by having an ProxyNode
in your original file that references a file with a ProxyNode to itself.
Anyway, just a hunch as I said.
You can verify that by saving to
Hello,
I have an osg::ProxyNode model that I change the material on then I try to
update the file itself so that next time I run the program the changes persist.
If I save it to my_model.osgb then the next time I go to open it
osgDB::readNodeFile locks up trying to read the file, however if I
5 matches
Mail list logo
