Hello Carsten,
"Carsten Neumann" <carsten_neum...@gmx.net> schrieb im
Newsbeitrag news:4c49d799.7090...@gmx.net...
>
> ok, thanks. Honestly I'm a bit overwhelmed with all the files...
>
Sorry, but I simply tried to provide as much information as possible...
>
> hm, comparing the files "Rebuild model/SceneImp_write.txt" and "Read
> rebuild model/SceneImp_read_5.txt" (IIUC these are a dump of geometry
> that looks correct in your app and a dump after saving and loading back
> in, correct?) there are some strange changes in positions, often a 0.5
> change in the Z-coordinate, but other (larger) differences as well.
>
> Since you have this Geometry dumping tool, together with diffs of the
> resulting files it should be possible to make sure that the data is
> correct up to the point it is written - that way we could exclude
> problems in your app.
>
I will do.
>
> Also, to reduce other effects, you could try using
> OSG::OSBDriver::writeFC() to write just the Geometry when writing .osb
> files.
>
Thats new to me. I will have a look.
>
> I guess, they all seem to have a few triangles sticking out. I'm
> assuming all along that is in fact the problem we are talking about in
> this thread, right?
>
Yes, but I have a special memory manager running. My aim was to exclude
problems in that direction.
>
>> 2. Is the write1.osg file correct? Is there a problem with the write
>> backend
>> for this file type?
>
> Which write1.osg is this? I have "Rebuild model/write1.osg" and "Read
> write1.osg/write1.osg".
>
Ups, I was thinking about Rebuild model/write1.osg.
>
>If you think there is something wrong with them,
> please just mention what it is, that way I can much faster check if it's
> really a problem ;)
>
You are right. I did read this file ('Rebuild model/write1.osg') with the
'10loading.exe' example. I did have to insert some code before the osgInit
call, namely
OSG::preloadSharedObject("OSGFileIO");
OSG::preloadSharedObject("OSGImageFileIO");
OSG::preloadSharedObject("OSGContribDataSolid");
to get it work. File reading always results in a root node with a null core
and no rendering. However, ascii file inspection did not reveal a problem to
my eyes. Unfortunately, I couldn't debug the file loading procedure due to
the lex/yacc based parser code.
I would like to know if the layout of 'Rebuild model/write1.osg' is correct
and why I get this null core on loading this file with '10loading.exe'.
Interestingly, I could load this file with my application. As I tried to
explain, I do not use the whole scene graph in my app, but only the tree
branch starting at the '__StaticRoot__' named node. Hence, in this case the
geomerty part is correct! (Not so on doing the same with one of the osb
files). In my application, however, I also get the null core root node on
reading the osg file.
Thank you again for taking your time.
Best,
Johannes
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users
