#METABALLS PROBLEM
15 messages in this thread
When I use the OBJECT/SNAPSHOT to create a long trail of metaballs and then use
MSHAPE there is a considerable gap between the original spheres and the new
metaballs model. Am I doing something wrong or is this a flaw in the program.
Any help appreciated.
Don
71053,1664
Don,
<<there is a considerable gap>>
try increasing the number of snapshot objects you create – you CAN create more
objects than the frame segment you have defined. So, for example you can
create 60 snapshot objects over a 30 frame segment, and you'll get an object
every .5 frames.
My guess is that you're creating, say 10 snapshot objects over a 30 frame
segment, and you're getting too few objects. remember, in order to get a
flowing metaballs shape, you need to have many metaballs.
-Kyle
Unfortunately, I've already tried that. Let me explain. When I use
OBJECT/SNAPSHOT I've created a tail with plenty of spheres, sometimes twice the
number of frames but I still end up with a metaballs shape that is much larger
than the original spheres. But if I create multiple copies, manually, of a
sphere in the EDITOR (a slow and tedious process) and create a metaballs shape
it fits over the original spheres much tighter. I have noticed that as the size
of the spheres are increased so goes the gap between them and the new metaballs
shape.
ahh . . much clearer now
Here's what's happening (I think) – if you have multiple metaballs that lie
within a tight area, the metaballs multiply the size of the resultant mesh. to
alleviate this unwanted size increase in the mesh, you can use a harder color
for the balls.
If you're still having troubles with the mesh – send me the file and I'll have
a look at it.
-Kyle
PMJI, but as a definite future MetaReyes owner I'm interested in this thread.
I was going to wait for version 2.0 (due in "three weeks") but from what you
said I get the impression I can use Snapshot modeling with the present version.
Is this true? Maybe I shouldn't wait, since I know 1.0 users get the upgrade
for free, but I was just assuming that 2.0 would be more integrated and it
wouldn't do me much good to learn a whole new system. Any thoughts?
>you CAN create more objects than the frame segment you have defined
I've used Snapshot a lot, but I've always found that, assuming you have even
velocity on your path keys, you can't make more objects than frame segments and
have them lie anywhere differently on that path. In other words, if you have
300 frames and make 600 objects, you're only going to get 300 different object
positions. I always run Tempo on my paths for Snapshot modeling so I get even
spacing, and thus the max number of frames is the limiting factor. (You could
run the Script that manages keys to get the same effect).
Hi Mike,
<< I can use Snapshot modeling with the present version. Is this true?>>
yes!
As you probably already know, the Snapshot command it just a tool for creating
a individual object that carries the positionsl info, as well as the rotation,
scale, and morph position at a certain frame. The use we metaballers are
getting out of it is being able to create a uniformly spaced 'string' of
reference spheres that will come out very smooth once we apply Mshape to them.
<<I've used Snapshot a lot, but I've always found that, assuming you have even
velocity on your path keys, you can't make more objects than frame segments and
have them lie anywhere differently on that path.>>
where did you come about that conclusion?
Do this: create a sphere. go into the KF and move it to a different position
on frame 30. Then increase the scale at frame 30. Hit Object/Snapshot and
click on your sphere. then turn RANGE on, make sure is says from 0 to 30
frames and insert, say 90, in the # Copies field. Hit OK and if you still have
any questions write me back. 🙂
-Kyle
>being able to create a uniformly spaced 'string' of reference spheres that
will >come out very smooth once we apply Mshape to them.
Ah, this raises an interesting issue. If you create, say, 100 metaballs, do
you have to go in and assign MShape to each of them, or can you simply assign
it to the first object and have Snapshot copy it. I'm fairly sure you can't do
it with scripting, and I think the effort of doing this would mitigate in a
large degree the use of Snapshot (what about the 600 Mball T-Rex!!! Just the
thought of all that typing makes my wrists ache!).
>Then increase the scale at frame 30.
Ah, we're talking apples and oranges here. Try your same experiment, only
don't change the scale. You won't get any more POSITION changes than 30, no
matter how many copies of the object you make.
You're talking about scaling, which is a whole different ballpark. Since I
only use Snapshot modeling (so far) for position-type work, I don't get any
advantage to using more copies than I have frames. But at least it's good not
to get locked into that way of thinking when I start using MBalls, as I
obviously will need to Scale (and rotate, and all kinds of things).
Still don't like the thought of all that assigning…
Mike,
I think you're making this more complicated than it is.
The Massign program just changes the color of the object – it doesn't assign
some hidden value or other thing to it inside 3DS. I don't even use Massign
any more, I just assign the color value that I want. (In the Massign menu, it
gives you the color #'s that it uses to identify reference spheres) So, I just
create my spheres, select the ones I want, and change their color.
<<Ah, we're talking apples and oranges here.>>
nope – we're all the same fruits 🙂
<<Try your same experiment, only don't change the scale>>
ok – did it
<<You won't get any more POSITION changes than 30, no matter how many copies of
the object you make. >>
uh, yes I do. Try sending me a file that doesn't do it correctly.
You ARE using R4???
-Kyle
Ah, thanks for the info. I was just assuming (I know – it isn't the first time
I've gotten into trouble) that in order to use MBalls I needed to assign a PXP
to the object itself: thus I envisioned a lot of assignment typing. I guess
what you're telling me is that MShape just allows me to use color assigns,
which I can definitely do all at once. I guess I should just buy this current
version and start having fun. Wonder who sells it?
I went back and looked at my position stuff — you're right. All of my
examples had spheres which were of a size that did not make any difference in
the numbers I put in. But I tried it with smaller spheres (and a larger path)
and saw the difference.
Mike,
<< I guess what you're telling me is that MShape just allows me to use color
assigns, which I can definitely do all at once.>>
you got it 🙂
<<Wonder who sells it?>>
Schreiber Instruments.
<< I tried it with smaller spheres (and a larger path) and saw the
difference.>>
Glad you got it worked out – I was beginning to worry! 🙂
-Kyle
Hello Don,
What is your current MSHAPE version ? (From the Mshape menu).
-Javi
MSHAPE is version 1.01b for 3-D Studio v. 3.
Don
71053,1664
The latest release 1 version of Mshape is 1.01c . You should update
to that. If that doesnt solve your problem you better wait for
release 2.0 that is almost HERE.
How much is your Metaballs Ipas for 3DS?
L8R,
Fred Nilsson
MetaReyes is $495 within the U.S.A and $595 foreign orders.
-Javi