srek
-
Posts
3,164 -
Joined
-
Last visited
-
Days Won
72
Content Type
Profiles
Blogs
Forums
Gallery
Pipeline Tools
3D Wiki
Plugin List
Store
Downloads
Everything posted by srek
-
I went down that route a while ago, but the results were unsatisfying to me. Maybe someone with a better math understanding than me picks itup.
-
One more example, this time the creation of an own modeling asset using high level modeling operations https://nodebase.info/example/modeling-with-scene-nodes-part-2/
-
Good catch, that was only in the first posting on the topic of weights, i should repeat it in the second one. Any empty field string field will make the modifier use the first dataset found. So if you have only one you can leave it empty.
-
Most example files are now also available from Github https://github.com/bmarl/nodebase/tree/main If you fetch the files to a local disk you can add them via a watchfolder in the asset browser and stay up to date easily if you like.
-
This is a conflict that isn't easily solveable. While you can control by far the most input ports using nodes you don't do this all the time and not always with the same ports. This makes it very difficult to predict which ports should be exposed by default. The general rule is that those input ports that need to be connected for the node to work correctly are shown by default, though there are exceptions. For every other input please check the workflow to Ctrl/Cmd+Click on the small circle in the AM to quickly expose a parameter as a port.
-
Thanks for the info, something went wrong there and i'll fix it as soon as i can. It seems you found that the Aggregate node behaves differently in Stream Mode
-
This is one for those of us that don't like to see the inside of a node editor https://nodebase.info/fundamentals/modeling-with-scene-nodes/
-
1. no, this is not about fields, fields only control the weight map. Scene Nodes don’t know anything about fields 2. Operations is the Operation applied by the average node, you can choose min, max, … instead of average 3. All arrays output by Polygons Info are based on the selected polygons and the element with the index 0 of each array will give you the data matching the first selected polygon. It doesn’t matter on which of the arrays the iteration is based, it just changes which data you get directly from the iterator and which you have to get by using Get Element 4. Not really, as i wrote in the Blog, it’s really only an average
-
Maybe this helps you already https://nodebase.info/example/weight-controlled-poke-modifier/
-
Poke and the other basic modeling operations do not support individual variations per element, you would have to do this by hand by repeatedly applying the operation to individual elements at varying strengths. Edit: Also to work with fields you need point weights as a starting point, direct sampling of MoGraph fields is not available.
-
Update, this time with a bit of a focus on MoGraph Combining Fields and Scene Nodes https://nodebase.info/example/controlling-a-modifier-with-mograph-fields/ And also my addition to a nice Youtube tutorial from Jack Ke https://nodebase.info/general/combining-mograph-and-scene-nodes-voronoi-fracture/
-
Not for the faint of heart, something on Array Collections. https://nodebase.info/example/working-with-arrays-part-4/
-
Iterate Collection delivers the elements of the collection. A for loop is more comparable to the Range node, where the output port Range would be the iterated value (x). Loop Carried value is a generic loop body that can be used for any kind of iteration. Comparisons between code and nodes quickly break apart, the two really work differently. I.e. you can't end an iteration in code more than once, in nodes you can.
-
I haven't gotten a single artistic gene from either side of my family, those are all done using SD locally and some very straight forward and limited prompts
-
The list is getting longer, a lot of stuff regarding arrays was added. Have fun.
-
Thanks, that shouldn't have happened Edit: The culprit was a default resizing from Wordpress
-
The screenshots are all full size
-
Why "Density" and "Mass" values in Dynamics instead of "Weight"?
srek replied to MJV's topic in Discussions
If you create a setup that involves no gravity weight has no meaning. You need mass and density to be able to define a bodies behavior under all circumstances. -
Thanks, that is certainly something to think about. I also added a request form https://nodebase.info/request-a-topic/ No need to repeat what you posted here, that is stuck in my brain 😉
-
As a personal side project to provide more information on Scene Nodes to everyone interested i started a small page. https://nodebase.info Feel free to request topics that should be covered
-
Sorry, it is not my place to comment on anything that might happen to Cinema 4D in the future.
-
In the mean time check out what you can do with in and output ports
-
The scene manager was part of the tech demo and has been retired.
-
You are describing what Xpresso offers
-
i fear you are incorrect. Xpresso and scene nodes solve very different problems and work in different contexts. Xpresso controls parameters, but can’t really change the objects or their geometry. Scene Nodes create or modify objects, but can’t modify the parameters of objects.