HappyPolygon

It's set by default to search for words in current page. You need to select "All content" from Content Type For me a big disadvantage is the absence of searching words in posts made from a certain user.

It's not always to make a checker-board selection because the way the polygons get selected is structural and not visual. This means that the sequence in which polygons are constructed is not always from left-to-right and top-to-bottom. And it will certainly not work when more than 4 polygons share a common point like bellow. One solution I suggested here some time ago was to use a Shader Field with a checker-board shader but it will still not give the best results.

I wasn't able to track-down that particular developer but found out that Nitro4D is on it so I expect a low-cost plugin. And someone else wrote a script that auto-sends a rendered image to Google Colab to use the Stable Diffusion Model. It's very cheap but subscription based and the "bad" thing with Colab is that it's also subscription-based if you want a fast and high-res output.

Haha I forgot about that, you are right ... Did you write this or was it Deepstory / Dramatron ? 😜

Sorry but I don't use Octane and have no idea how to use it. It is 100% an Octane matter. It probably has to do with the projection methods it uses. As I can see the original gradient is used but not the stepped method or the tilling I described above. You have to recreate the Material in Octane as an Octane Material and probably use the Octane projection mechanisms to achieve the same result. For the gradient see here. I've found an important note on C4D shaders for Octane here that links to the C4D Gradient and the differences between that and the Octane gradient For projection tilling se here or here As I said I have no idea about Octane so my links might not be helpful at all or even my approach won't even work with Octane's logic, for example UV Transform may only work with bitmap textures not shaders and you'll have to recreate the gradient in Photoshop...

Oh... there is nothing exactly like that but there has been a video about an AI-driven liquid simulation.

yeap

sauce ?

Already there

Ubisoft Singapore senior technical artist Mohsen Tabasi has released StableDiffusion_Houdini 2.0, the latest version of his free tool that links Stable Diffusion into Blender. The plugin makes it possible to use the open-source AI image-generation model inside Houdini, in order to use 3D scenes to guide the image that Stable Diffusion generates. With it, users can convert renders of simple blocking geometry into detailed illustrations and concept art. Version 1.0 required an online Stability AI DreamStudio account to generate images, but version 2.0 makes it possible to set up a server based on open-source tool AUTOMATIC1111 and run entirely on a local machine. https://www.cgchannel.com/2023/02/free-tool-mohsen-tabasis-stablediffusion_houdini-2-0/?fbclid=IwAR3CI2Bjm-NxRx5mzFam2ISGKwECCj8Qij-rRpoNvPU6VwmwtEzqIfOb4Hk

Oh that's very clever. I thought I was in the Scene Nodes pit. It took me quite some time to figure out how the hell you managed to delete polygons using fields.

You are right. And it's a quite old bug. R25 old

Damn politics ...

I don't use RS. If ZEROSIXTWOSIX's approach doesn't work with RS try brute forcing it... How many knots does your gradient have ? Make that many copies of the object each with a specific Material color from the gradient. You could also use (if there exists an equivalent in RS) the MoGraph Multi Shader...

I'm not sure if the "technical demo" was a forced (marketing) move due to the release of Blender Geometry Nodes but it definitively was the best move since that gave MAXON the biggest possible feedback. Up until then every new feature was tested exclusively indoors or with close NDA collaborators. Introducing such a big feature (that would definitely be called a module back in 2010) needed a bigger audience, not just people who worked in the field for decades. And the next iteration of Scene Nodes in R25 was a huge improvement. You got an iteration node or conversion node for free when connecting specific nodes together saving you from aimless debugging or logical dead-ends. There's a Scene Root default node. Better search algorithm and of course capsules. Well, I'm not 100% sure if this is really an open question. In order to define the system as Turing-complete you have to define it in mathematical terms and prove or disprove the original hypothesis. From my point of view if there are no equivalent structures between nodes and coding like variables, if, while-do, case etc. then it's probably not Turing-complete (and to be clear, commands like if, while-do, case have nothing to do with the Turing-completeness theorem). My first struggle was with variables. You can define a constant and feed that anywhere but you can't store a value back to it. There's only an output. Maybe I'm wrong and everything does have an equivalent node structure and I'm the one that fails to recognize because I'm not used to alternative paradigms especially plethoric in expression (more than one node/statement). I think nodes are on the right track. They are getting constant feedback and introducing new Capsules like the latest Spline chamfer. Bit by bit all the old handy plugins will be replaced by native tools. I believe that even Ricochet can be reconstructed using scene nodes. The big question is whether Scene Nodes will compete with Geometry Nodes face-to-face providing what C4D is best known for (intuitiveness) combined with the quality and power of Houdini. We expect a lot of improvements in all aspects of C4D but due to NDAs all will be reveled at the right time. And of course God willing concerning war and natural disasters...

The Volume Builder/Mesher is probably the only complete feature in C4D. For everything else there is room for improvement.

Since R23 there was a discussion about how Scene Nodes were supposed to actually help things out. The discussion was mainly philosophical because from the existential point of view (why are Scene Nodes even needed in the first place) there wasn't much backing up of the idea. It seemed that the main reason Scene Nodes were developed was the constant expressed opinion of the public wanting a node-based modeling system like Houdini, just because Houdini is king in CG production (Blender is also known for it's own system but Geometry Nodes were released some months after Scene Nodes so I don't think Blender was a factor). The new (Neutron) project had pitfalls for the following reasons, making the result look like a failure : The public demanding a node-based system had a false perception of what that would look like and how it would work. Mainly because most of them didn't even know how Houdini works, they just knew it was "better". Also many of them (users) weren't familiar with XPresso or Material nodes. So when the system was finally delivered the learning curve seemed overwhelming. Considering the poor documentation made things worse. Many users already knew that a node-based modeling/animation system's biggest advantages are the procedural and parametric characteristics. What they failed to acknowledge was that C4D already had the capability of procedural and parametric setups due to the powerful Object Manager, something that other DCCs are trying to replicate. Considering the above MAXON added the Capsule system. A bridge between the Object Manager and Scene Nodes. Now we know why Scene Nodes are needed and these are the following: Not all C4D operations are procedural or parametric. These operations are positioned mainly in Tools, Mesh and Spline menus. These are operations that are not stackable in the Object Manager. Best examples are the Inset, Extrude, Bevel and Bridge operations. Scene Nodes provide a better space (2D) than the Object Manager (linear) to accommodate for complex groups of operations AND procedural/parametric operations that are not available in the OM. Scene Nodes offer capabilities that XPresso couldn't like UV/color management during modeling and some attribute manipulation mostly with instances that was impossible before. A better graph structure. XPresso had a less restrictive brunching structure which made it prone to logic conflicts when same attributes were manipulated simultaneously by many operations. Scene nodes are less prone to these kind of conflicts due to their "one-way" structure. Personally I have seen very few occurrences of cyclic structures (infinite loop) in Scene Nodes and when that happens it immediately gets detected. The ability to construct new parametric primitives. The ability to construct new tools without diving deep in the C4D Python API. Procedural modelling. Points that are yet to be resolved: Visual aid on selections. Boolean Operations. A better category system to provide better housing for the expanding number of nodes. (sub-categories for example or a tier-based metadata tag filter to better serve users with different experience or type of work (newbies want to see only capsules, techies want the low-level structure nodes) Access to specific Capsules from any custom pallet (I think it has been solved but not sure) More high-level nodes for complex operations (the "bad" thing is that MAXON tries to construct high-level nodes from low-level nodes and not just hard-code new nodes, this is time consuming because it leads to technical difficulties) Nodes are harder to update. I'm talking about high-level nodes like Dual-mesh. It's not the same thing as adding new features to an existing coded feature. Although nodes are scalable, adding new features/mechanics in an existing structure can be much trickier compared to coding. Faster loading times when the node pool is summoned. Make scene nodes a high-level workspace for procedural and generative modeling by adding mechanics to accommodate specific needs. For example Adaptive Grid Space for asset placement - used to create procedural cities, buildings etc. Terrain modeling tools - diffusion, erosion, terrace and many more modifiers are easier to work with in a 2D node space rather in OM. Agent system - for crowd animation, traffic animation or simulating flocks of birds, schools of fish etc. Some philosophical issues still remain open: If Capsules are used like deformers in the OM, why still use them as such and not hard-code them later as regular Deformers adding more functionality to them like having Dual Mesh affect certain regions of geometry using Fields ? Should all features be mirrored as nodes in the node pool ? For example instead of dropping a Cloner in the Scene Node space from the Object Manager, just drop it from the node pool, because you don't want to have the cloner or any other hierarchy chain of native C4D elements in the OM, you just want the result to manifest from the Scene Nodes. Should Selection Strings be adopted to the rest of the app or evolve into a better system with all the benefits from Selection Strings and the usual Selection form ? Should custom icons be made for most nodes in the Geometry Modifiers category ? (what's the point of having the same icon if the icon is not used for identification) Should there be a ready-made Palette with deformer-like capsules and primitive-like capsules for users to select from without having to open Scene-Nodes ? (helps new users to know all available geometry manipulation options making features look system-agnostic (I call systems all node systems and the python interfaces)) Is Scene Nodes Turing-complete ? This levels Neutron with programming. If the system is Turing-complete that means that anything that can be programmed can also be translated to nodes. This is very important because it can save you from chasing your own tail. If I know that something is possible with Python and that Scene Nodes is Turing-complete then I can make the attempt to implement it using Scene-Nodes. This tread has forked more than any other thread 🤣

But you've already did that back in October... is this faster or did you update the project into a capsule ?

I found 2 hours late the new VFX and Chill broadcast today. They tried replicating the exact same scene as you... I we were watching it we could provide some useful insight cause they seem quite lost and didn't really bother making their homework about how exactly they were originally made before trying to tackle the scenes they picked...

Yes, and all modeling tools like extrude, weld, bridge, cut ...

Please fill the appropriate info in your profile. Your case looks like a very good opportunity for the Volume Builder/Mesher to shine. Especially the latest C4D version has the very useful Radius blend. After that you can polish the topology with the ZRemesher from the Remesh generator. It can definitely be modeled using the traditional tools with a Subdivision Surface finish but you need some prior experience. I would not recommend any Boolean operations for this kind of modeling. Do you need a step-by-step guide ? If yes, @Cerbera is our modeling professor. P.S. You forgot to upload the file you mention, unless you're referring to the image.

Before the new update comes available you can try out this HDRI 360 panorama creator. The output is at 1024x512 but you can upscale it using this handy AI resizer https://bigjpg.com/ Currently the output is not seamless but this is expected to be patched in the next version.

What I had in mind was an animated shader. But, yes, it's not meant for interactions between objects unless they can figure out a way to bake the displacement and have it run as a simulation from a point on.

I believe the next evolutionary step to Pyro is implementing a Volumetric Displacement shader like Arnold. I think it's less computationally intensive to have a shader-based volume displacement rather a simulation driven one.

looks perfect to me. Does it work for any polygons ?