3Dmember.image 2004-02-11 - By Alex da Franca
Back
At 8:52 Uhr +0000 11.02.2004, Danny Kodicek wrote:
>
>I'm afraid to say that I never found a solution to this.
:-(((
> I'm pretty sure that even putting the cast member on stage non-dts
>and taking the stage.image can cause problems.
ups !
do tell.
I didn't come across leaks with the stage image so far.
can you remember what these were ?
>
>The only other thing I can think of that could conceiveably make a
>difference would be to navigate from time to time to a frame that doesn't
>display the 3d member. Maybe that might flush the memory.
I'll give it a try, but I doubt it. the only
thing I can think of would be to delete the 3-D
member and recreate it, to flush the instance of
the w3d xtra, probably.
because if only navigating to another frame would
help, the problem would go away in authoring
between the different tries. buit what I learned,
was, that even restarting director didn't help in
some circumstances, which is seems to be caused
by a REALLY a bad leak in the card driver, caused
by sw3d...
sometimes I wish the intel guys would be still
around in this list and offer some insigths...
remember the precious mails from Allen Hux and
Dan Johnston posting from Gary Baldes account ?
those were the times ;-)
--
|||
a�ex
--
__ ____ ____ ____ ____ ____ ____ ____ ____ ____
Dir3d-l mailing list
Dir3d-l@(protected)
http://nuttybar.drama.uga.edu/mailman/listinfo/dir3d-l
|
|
