#Morph materials
13 messages in this thread
To All,
Does anyone know if there is a way to set morph materials as the default
setting in the keyframer? Also, how why doesn't my resolution in the renderer
come up on my 3ds settings of 720×486? (it comes up with 0x0).
Any ideas?
Jimbo
Hi James,
<< Does anyone know if there is a way to set morph materials as the default
setting in the keyframer? >>
I don't think so.
<< Also, how why doesn't my resolution in the renderer come up on my 3ds
settings of 720×486? (it comes up with 0x0). >>
see pg. 7-205 , first paragraph, of the R3 ref man.
jonas
Jonas,
Thanks for the info, since you're on a roll, do you know why when I render to
my PAR using NDUMP i lose any background image or color (just renders all
frames with a black background)?
Thanks,
Jimbo
Jimbo:
Video Post does not utilize the background in a file. Just put your background
in as the first entry in the Video Post queue, and you'll be back to normal.
Greg Pyros
Greg,
Thanks, you'd think after using 3DS since ver. 1 I wouldn't need help with such
a no-brainer <G>
See ya
Jimbo
Jim hi.
Sorry to jump in here.. but what is NDUMP? I just purchased the PAR and I
love it, except I tried to render to my Micropolis drive on PC 1 (for the PAR)
from PC 2 over a Lantastic Network and the rendered image from PC 2 crashed PC
1. Keep in mind I was rendering separate animations on both machines at the
same time, both saving to the PAR HD, but both saving to different directories.
Is this normal? What would NDUMP do differently? I realize a fix for this
problem would be to send the rendered images from PC 2 to PC 1's C: drive, then
copy the files to the PAR drive as soon as the other animation is done, but I
was hoping for an easier way. Is there one? Thanks.
James Franssen
Imagination Station
James:
NDUMP.IXP is an IPAS program written by us to copy files in order from a
network to the PAR, or any other device which can be controlled from a batch
file.
It works within Video Post, and allows you to continue rendering whenever there
is nothing for it to do.
Greg Pyros
"NDUMP.IXP is an IPAS program written by us to copy files in order from a
network to the PAR"
Great, thanks. So I guess rendering more than one animation to the PAR is out
of the question as Gus mentioned. Is the most effecient way to render, then,
to just render a single animation to the PAR from multiple (2) machines? Or can
this be done? I am not rendering two animations, but one over a network.
Thanks.
James Franssen
Imagination Station
– 72650,3677 @ 18-Sep-1994, 21:50:17
James:
Rendering on multiple machines is always the most efficient way to render with
3DS's network queue feature.
Greg Pyros
You cannot create two animations at the same time. The PAR can only handle one
animation at a time as all frames must be in sequence. On top of that, the PAR
driver does not handle multiple access. That means you cannot have two or more
machines writing and/or reading at the same time. This is due to the fact the
PAR has to convert the images back and forth from YUV to Targa and there is
only a single (1Meg) buffer for it. Your problem has nothing to do with NDUMP.
NDUMP helps keeping the sequence in order. If you have several machines network
rendering (the same animation), you need to be able to save the frames in
sequence. If you let them on their own, faster machines will process frames
faster than slower machines and there is no way to control which frames get
rendered first. By telling all machines to render to a [shared] physical disk
(as opposed to the PAR directly), NDUMP will pick the frames from that disk
and, in order, save them off to the PAR disk (optionally deleting them from the
physical disk to save space).
James, I'd look into the problem possibly being Lantastic oriented. I've never
had great luck with it and lots of drive access from other machines. Never had
any such problems with Novell though. Just a thought…
Dave Mennenoh
James,
greg answered your question. I use the NDUMP routine with on a Lantastic
network of 5 machines and only rarely have problems with it. NDUMP allows each
machine to render a frame and then store them temporarily on a hard drive until
they can be dumped out to the par in sequential order. This works great
because my pentium renders so much faster than the other machines and it allows
it to do the bulk of the work. I hope this helps.
Jim Beyer
Jim:
Glad NDUMP works well for you!
Greg Pyros