#3ds2.00rndering prob
3 messages in this thread
Am in dire! need of info. When animating in fields from 3ds2.0 thru BCD5000
ani. cntrlr an unnacceptable artifact occurs as "frame-to-frame 'stuttering'"
(my term). Best way to describe it is "two steps foward, one step back, two
foward….". We have tried field order adj. We have adj. contrllr timing as
much as we think possble. Have contacted Truevision (ATVista4M)…. And of
course we've talked forever to BCD Associates…NO HELP! Our nearly last hope
is that it is a softwre issue between: BCD5000 – 3ds2.00 , or Stage driver
-3ds2.00 , or ??????. Please advise anyone who would like to keep another
fellow animator from going over….. Much thanks!
Theo:
Saw your message. You are having a field order problem.
Put everything back to normal before you started tweaking it, and set field
order to it's default of 1 in 3D Studio. Now reset your machine before
starting to do a Disk-to-VTR.
There are some other programs which can reverse the field order of the
AT-Vista. What I suspect is that you ran one of them and reversed the board
before taking the animations out to tape.
Simply start fresh and you should be OK. I've seen this before, and that's all
it is!
What driver are you using for the AT-Vista? RDPVISTA.EXP, I hope?
Greg Pyros [Pyros Partnership, Inc] gpyros@pyros.com 21-Dec-93 at 9:58p PST
—->>> Am in dire! need of info. When animating in fields from 3ds2.0 thru
BCD5000 ani. cntrlr an unnacceptable artifact occurs as "frame-to-frame
'stuttering'" (my term). Best way to describe it is "two steps foward, one step
back, two foward….".
Are you rendering from the DOS prompt or with batch files? I ran into a
similar situation awhile back.
I had 3 machines to render, and I made batch files to render frames:
Machine 1 – frames 0-900 STEP 3
Machine 2 – frames 1-900 STEP 3
Machine 3 – frames 2-900 STEP 3
This seems logical, since all frames would be rendered and the machines, if
similar, would sort of keep up with each other. (be around the same section of
the animation together)
BUT, this didn't work. Machine 3 would SAY it rendered frame 2, and even name
the file that. However, the ACTUAL file would be the same as frame 0. When
dropped to tape, this looked like a field order problem – kinda like the
stutter stepping you were talking about. I changed field order and rerendered,
with no luck.
The only way I found to get around it was the render like this:
Machine 1 – frames 0-300 STEP 1
Machine 2 – frames 301-600 STEP 1
Machine 3 – frames 601-900 STEP 1
… which worked like a charm. I don't know if I was doing something wrong or
if it was just a quirk of R2, but there you are.
Good luck,
Oral Friend