Hi Dirk,
> Seeing that the currently used crop of cards has at least 64 M of
> texture memory (Octanes and Indigos don't count any more ;) I'd say 16 M
> is a safe bet.
What about all those GF3/4 cards with 32 MB? Or do you happen to
consider them "depricated" as well ;-)
> > Could we somehow achieve a graceful behaviour, so that not just
> > a crash or some OpenGL error in OSGImage indicates, that the brick
> > size was too large?
What will currently happen if the specified brick size is too large?
Could you check?
> I would hope that the proxy mechanism is realiable, that why it was
> added in the first place. Currently OpenSG doesn't expose it, though.
Last time I tried the mechanism, is was NOT too reliable, that's why
we didn't consider using it.
> The least invasive solution would be to just make the field public.
> Given that is also the minimal work solution that's what I would propose
> for now. ;)
>
> If there are no objections I'll change the default to 16 and check it
> in.
Make it so.
Manfred.
======================================================================
Manfred Weiler [EMAIL PROTECTED]
Visualisierung und Interaktive Systeme Telefon: 0711/7816-208
Universitaet Stuttgart, IfI FAX: 0711/7816-340
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
