Havealot
-
Posts
346 -
Joined
-
Last visited
-
Days Won
6
Content Type
Profiles
Blogs
Forums
Gallery
Pipeline Tools
3D Wiki
Plugin List
Store
Downloads
Everything posted by Havealot
-
Those interactive explanations are lovely! Well done!
-
Ah, I wasn't aware of the pairs notation. Good to know. Learned something new 🙂
-
Edges are implicit and don't really have an index of their own. So providing indices or an index range won't work. But you can make use of all kinds of selections in the selection string. "Active" will give you the active Selection, you can drag selection tags in there and put quotation marks around it (like this "MySelection") or you can use one of the selection nodes do either set or store a selection or set the active selection before you apply the chamfer.
-
Did you watch it until the end?
-
You can randomise the clones directly with a random effector / random field (>R19). And since you have a MoSelection node in there, if you can restrict effectors to selection by dragging the selection tag into selection field of the effector. If you need to control the randomisation directly in Xpresso the easiest would be to link the integer port of the random node into the seed port of the random field / random effector. Just drag the field / effector into Xpresso and then drag the parameter that you want to control from the attributes manager to the blue corner of the corresponding Xpresso node.
-
The instance in your sweep is referencing the spline object inside the cloner. Not the clones themselves. The connect merges the clones and therefore contains all the (edited) versions. This is not a Python problem. The only python code I could spot in the setup is in the one node that is supposed to return the cache of the cloner. And that is exactly what it does. If you want sweep your cloned (edited) splines you can just create a dummy spline and dump the cloner cache spline in there as segments of the spline. That should work.
-
Here is a (not very well coded) example with a python node: Scale_2_SourceBB.c4d
-
You could rig an 2x2x2 FFD deformers points to the bounding box of the reference object. That would work for non-primitive objects, too.
-
Welcome to the community. Lite is great to get a first impression. But at some point (holidays coming up?!) I'd suggest to get the trial version. There is way more cool stuff you can do that is not possible in Lite.
-
Here is a quote from the MAXON SP1 announcement: "The installation of this service pack requires a completely new install and is recommended for all users" Installer can be found here.
-
Damn, I was in the process of creating the setup. We need a "claim fix" button 😄
-
Welcome! And don't let your language skills keep you from using a forum like this. Most of the time it is not the language that keeps us from understanding but a lack of clarity in description of a problem. Whether you spell spell you box "kube", "qube" or "cube" doesn't really matter.
-
Or use the python node: import c4d import random #Welcome to the world of Python def main(): global Output1 random.seed(Input1) Output1 = random.random() * 100 Create the python node, copy&paste this code, delete Input2 and feed the User Data into Input1. Output1 will give you a random number between 0 and 100 (in this case).
-
Both the instance object and the cloner handle scale on their own, otherwise you could only ever have instances/clones of the same size. The reason why the scale tool is working in your case is because the cube primitive interprets the scale action differently and adjusts the size xyz parameters instead of the scale. If you want to scale all the clones override the scale in the cloners transform settings or use a plain effector. If you need to scale the instance itself for whatever reason you can disable "Reset Coordinates" in the cloners object tab and set the scale of the instance with Xpresso.
-
I got excited about rumours of an upcoming TFD release one too many times over the past few years. Downloadable demo version or it didn't happen 😄
-
Sorry for the late reply. Didn't find the time to recreate the setup yesterday. I've attached it as an example now. Not very fast as you cannot use instancing in this case. But it looks kind of ok. If you want more complexity you could produce larger patches but that would be a bit more manual labor as you have to do more variations for a plausible result. fake_packing_with_patches.c4d
-
I'll post a scene later. Stay tuned.
-
Completely random packing I fear is not possible without scripting. What you can get is "sort of random" by dividing your setup into premade patches that you then clone randomly and rotate them in 90 degree steps. Depending on your use case this might be good enough and would be completely MoGraph based so you can use effectors to animate it or even to control where each patch is being used. The patches can be broken up into individual pieces using the fracture object. Here is a screenshot:
-
Not sure what is happening in the rendering. It is working as expected for me. Your intended effect should be doable with the approach I used. You'll have to remap the effect a bit. But that will be pretty much the same as in Python.
-
Maybe this example is helpful. I'm using a Fracture object to treat any object as a MoGraph clone and use a time field to drive colorize each object with a black to white gradient. The material reads out that color through the MoGraph Color shader and uses it as Alpha. The linear field is just there to illustrate how you can offset the fading per object. MG_2_Alpha.c4d
-
Not sure what else you tried to achieve this but I would expect there is an easier way to do this than having to code it in Python.
-
Try asking at developers.MAXON.net. The guys there are very helpful. Awesome portfolio btw. 🙂
-
As a last resort you can try caching both the sphere and the cloner with alembic.
-
Not exactly sure when MoGraph caches are evaluated, but setting the Xpresso tag priority to generator did the trick for me.
-
Use blend mode and Effectors / Fields to blend between two states of the cloner input: clones data_0001.c4d