Jump to content

Hrvoje

Admin
  • Content Count

    12,618
  • Joined

  • Last visited

  • Days Won

    58

Everything posted by Hrvoje

  1. I am not really in position to say what will be in nest build, however this slider has nothing to do with future. It is just an asset where I make percentage slider with different increments to control values. here is the file, you can convert it to asset and save it in your asset pool for use 80_Slider.c4d
  2. Ah, that is just a slider asset I made and is not there in your asset pool, you can use a value from 0-1 for those
  3. Guilty and thank you very much Regarding account, is it lost password? We did remove a lot of accounts that were not active for years. PM sent
  4. Unfortunately, the inherited performance drop is due to using legacy object manager. If geometry and animation would be originating from Neutron itself it would be much faster
  5. @ilay Have you managed to make the setup?
  6. Original scene is too old for me to open on current machine You will have to change the approach to this since in Neutron you can't reference same object twice (as follower is setup in Xpresso). For this you will need memory node for storing data.
  7. You are welcome. It was an interesting test and again it is just few nodes. It will be really interesting to see what kind of assets will people produce once they get to know the system
  8. Please don't use those, they are not available in nodes asset pool for a reason and were made for testing purposes
  9. Like this? Here an "object field" which extrudes the selection then Object_Field.c4d Which ones you miss? It is likely that such functionality is already there or can be built as an asset
  10. @jonmoore You mentioned Laplace smoothing node in ICE. Here is one made with scene nodes thanks to our resident super dev Ole Dead simple to use, one inputs geometry and sets the smoothing strength Laplace.c4d
  11. There will certainly be some language exposed at some point but we are still deciding what would be the best option, or options. In meantime, Nodes themselves offer huge amount of programming possibilities which are yet to be exhausted before using some language
  12. Thanks, much appreciated! You will be pleased to know that most of this is already possible but one has to build it. For example, anything builder related is same logic and hopefully you saw my road builder which is a simple example of building something with predefined blocks. If I recall @srek had some examples of parametric buildings. Now, when you say controlled asset placement you are referring to distributing objects in numerous ways, right? There are many distributions in Neutron plus you can build any you imagine. Way more on your list that can be done already than not
  13. @Shrike @MikeA Guys, when you say "we need to get away from playing and thinking with cubes and spheres, and into something practical," Please give me an example of that so we can try to build it with nodes
  14. Yes, scene nodes are new core. They are a base for everything but will not replace existing workflow. What you now see is core used in nodes. That same core can and will be used for "normal" manager. So you will be able to use nodes, managers or both in future, depending on your preference. The familiar and easy to use object manager workflow we all like will definitely stay.
  15. This node group or asset is created purely by nodes. I made the indicators by constructing lines (splines). Here is the scene file 74_Ray_Collision.c4d Of course, it is just a basic algorithm but it works for most and is good display of what is doable, however it would make much more sense to get a default ,robust raycast and related node
  16. Ah, you want value manipulation on the node itself, yes, of course we are aware of that
  17. I will take a guess and presume you enabled tablet and high res tablet in Cinema prefs? Disabled windows ink in tablet properties?
  18. I am not really into rendering at this moment, but I would certainly expect a synergy with render engine. There is no point being able to have millions of objects running in viewport smoothly and then not being able to render them in reasonable time frame
  19. Can you elaborate your comment a bit more in detail?
  20. But it is legacy, has to be replaced by one which will not suffer from performance issues we want to eradicate
  21. Shrike Thanks for the effort, that is very detailed feedback! Here are some setups with Nodes that are quite difficult to achieve without them in current MoGraph or other context. Sure, the setup is more complex due to it being nodes, however I haven't took the effort to pack the functionality in single asset with simple front end controls, so what you are looking at can in fact be a single node with inputs and outputs Clone Blending Clone_Blending.mp4 Radius Aware cloning Radius_Aware.mp4 Recursion
×
×
  • Create New...