#Interrupted rendering
3 messages in this thread
Yesterday I was rendering a series of 300 TGA's to disk. When I
returned to my computer I found the screen scambled and the following
message: "Cheap stack dump linked in=> no dump Aborting…" The
rendering stopped at frame 234. Today, the exact same thinb
occurred- I decided tomake some changes in the animation and
re-started the rendering. At the same frame, 234, the computer
crashed and the same message ! I re-booted and continued rendering
from 234 to 300. When I began to record that series of TGA's from
disk to VTR, the program only recognized frames 0-233 ! I'm presently
recording the frames from VP after writing an IFL. I noted that on 12
Nov. Tom Anderson got the same error message- Any thoughts on this
phenomenom would be appreciated- Rudy
I might be completely off the mark here, but one answer to one ?: It
seems to me that I've had a similar problem in the past, and VP will
only recognize .TGA's numbered sequentially from 0000 on up. In
other words, if you rendered your second set of frames as 234-300 (ie
????0234.TGA-????0300.TGA) then VP will not recognize these. I have
had to delete all movement up to the affected area and slide all
remaining movement back, so that the second rendering can also start
at frame 0. I haven't done this in R3, only R2 if that matters. Just
my thoughts…
Rudy,
sounds like you have a conflict of some kind. Or you were swapping to disk
excessively and your controller choked on pharlap.