Seth Olson
3
AE Expressions Coins
4
COW Coins
Forum Replies Created
-
oh! I will give that a try. I thought that was for the alpha of the individual blades/hairs. Thanks!
-
I’ve had a problem with that, especially if I have set up animation of a null with a camera parented. I was able to solve my issues by copy and pasting the contents of the scene and paste into another. Kinda ghetto, but it is worth a try.
Also, cmd+shift+z actually undoes camera movement, which has been a problem for shortcut happy people like myself. 🙂
-
Ah!
I think I heard that they call it “QMC” now. Should be there under the GI settings. -
It looks like the position of one of the objects is shifting. Maybe you have some bad cache? Weird.
-
I moved the Xpresso tag from the car to a Null called “Xpresso” for easy finding.
The floor and walls are combined, which makes collision detection by Xpresso impossible. I couldn’t find a way to have a concave collision object. You need to have separate objects for each wall and use an “objectlist” with all the parts inside as your collision object.
Collision in Xpresso also requires editable objects (press C to make editable), so I used a hidden collision object in its place that sticks out only on the front and back.
To summarize the Xpresso set-up, I used a collision node to check. If collision occurred, toggle the “flipflip” node. This went to a switch, turning a “1 or 0” to a “1 or -1”. This then multiplied against the desired speed and output to each motor. Each step has a “result” node, so I can see if it was working.
Also, the dynamic tags must have enough bounce to push the object away, otherwise, it will continually switch directions back and forth and get stuck.
Check out the file attached. I have like a month of experience with C4D and would love to hear other possible solutions. Also, please show me what you do with it! 😀
4698_selfmovingcubesso04.c4d.zip
-
Ok, I emailed support at Maxon, and they said the following:
“Unfortunately TP gravity is based on a specific object. Due to the nature of Xpresso, you need a TP Gravity node for each gravity field, and because the gravity node requires an object rather than just a position you must have a physical object for each of those nodes. The one thing you can do is (ab)use the Dynamics Body State node to get the cached object for each MoGraph object instance. You still have to create a Dynamics Body State node (with the appropriate Object Index) and PGravity node for each individual clone. I’ve attached a file showing the setup. This could all be simplified through Python scripting, such as is explained in Cineversity’s Xpresso Maker tutorials.”
https://www.cineversity.com/vidplaylist/xpressomaker/
-
Ah! This might help:
https://greyscalegorilla.com/blog/2011/04/thinking-particles-tpgroups-events/
You can do exactly as you described!
-
I am trying to have the particles that are emitting be drawn towards the variety of spheres. I want each sphere to have gravity of it’s own. As you can see, the particles only orbit the origin of the fracture object, not its children. “Think of the children!”
Thanks for looking at it, btw.
-
Its probably too late, but I wonder if the character had been modeled in a T pose if that would help with your skinning issue.
-
Hmm, Here is the link to the file:
4695_tpexperimenta02.c4d.zip