Hi Dirk,
Dirk Reiners wrote:
[measuring graphics card memory]
Nope, there isn't, at least not easily. There are performance tools from
the manufacturers that can do it, but not many and not in a general way.
Yep, that's what I recon. We did ask at some point but never really
got any satisfying information .. there are - in this case - nv-specific
tools that do this and more, and the *more* probably was the problem in
releasing it, if I remember correctly ;)
[bin-files]
I tried loading that but couldn't. Can you save that as an .osb? .bin is
tied to a specific OpenSG version and is very brittle, osb is more
tolerant.
ok, I've changed to .osb. Although - I've written this with 1.6.0 and
didn't seem to have a problem to read it with 1.4.0 (a few error
messages). 1.2.0 failed, unsurprisingly.
only thing is: If I use osgSceneViewer to 'save as' a .osb, it seems
to write something like a .bin anyway .. at least, if I try to load it
again, it complains about the file not being in 'OpenSG Binary v1.0
format' ;)
Anyway, the new file is:
http://www.syrophenium.de/files/tmp/opensg/2bmw.osb (again, not for
the faint of heart, memorywise)
On big iron complete with a quadro fx 3400 graphics card this renders
at a whopping 0.9 to 2 fps when viewed full. If I let the view frustum
gradually cull parts of the geometry away, it suddenly jumps up to 60+
fps. The geometry isn't too complex and I wouldn't consider the amount
of texture data (opensg shows 34 megs) as a challenge for a 256 MB card.
By default OpenSG uses Display Lists for everything, those will rpobably
eat up more memory.
Sure, but to this extent? I've also tried disabling displaylists with
setDListCache - but this didn't help any, unfortunately.
I can render the same situation with different scenegraphs (perf**mer,
OpenSceneGraph) at 20 fps on a much lower-spec system and at near 40 fps
on the system mentioned above.
Not sure what they are doing.
Displaylists (if enabled) for performer, vbo's for OSG ..
What surprises me the most are the sudden changes in fps, the trigger
in between about 1 fps and 60 fps seems to be only at < 50 triangles
drawn more or less.
That sounds very much like memory thrashing.
Yep, I thought so ..
[npot-textures]
I don't think so. They are supported (and have been forever), but by
default OpenSG scales them up to the next power of two, we don't use the
NPOT textures as they have some constraints on most hardware.
Yes, that's what I assumed from looking at some code excerpts - so I
never bothered to do it manually. If it's any use, I'll do it of course?
Actually, I was able to load (a lot) more data with OpenSG at some
point in the past and still run smoothly. The same models now drop down
to about 1 fps :(
I have just tried on a win32 system with a FX3400 256 mb card and
older (6682) nv drivers and there it is, running smoothly at 30+ fps.
Strange. An identical system under linux (SuSE 9.3, FX3400, 7676) gives
me 3 fps. *sigh*. I will shortly try a windows version on that exact
same machine and with a newer driver revision ..
Best regards,
-.jan.-
--
Jan Wurster :: developer
IC:IDO GmbH :: Jurastr. 8 :: 70565 Stuttgart :: Germany
http://www.icido.de :: phone +49 711 27 303 163
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
