3Dmember.image 2004-02-11 - By Alex da Franca
Back
Hi all,
I remember issues with grabbing the image of a
DX7 (?) rendered 3-D member repeatedly.
I think it was Danny at that time having problems with it (or Lucas or NC ??)
anyway some of you know what issue I am talking about.
like you sometimes get 0 as result of grabbing
the image of a sw3d member, which may have the
same reason, after quite some operations (in my
case 170, but I think it is related to the
dimension of the defaultrect).
if the defaultrect, and thus the resulting image
object, is too big it fails directly from the
beginning.
and still worse: I managed to crash the graphic
card driver completely, since it seems to me,
that there is some kind of VRAM leak, when
grabbing the image of a sw3d member.
can anybody else confirm these findings ?
and more important: is there anything I can do to
prevent the VRAM leak, when grabbing the image or
is w3dmember.image.duplicate() just unusable ??
I need it very badly, since it seems to be the
only way to get my 3D still image antialiased in
a way, that is comparable to viewpoint, which the
client used until now and isn't willing to go
below that quality.
please tell me there is a way to prevent this
leak and the resulting crash or 'image = 0'
thingi !
Danny ??
Lucas ??
--
|||
a�ex
--
__ ____ ____ ____ ____ ____ ____ ____ ____ ____
Dir3d-l mailing list
Dir3d-l@(protected)
http://nuttybar.drama.uga.edu/mailman/listinfo/dir3d-l
|
|
