srek

In the new context, that is currently in its infancy, the scene nodes will do everything Xpresso offers and immeasurably more. Whatever features future Cinema will have, they will be controllable by the node system.

Just to make it clear, Scene Nodes can not and will not replace Xpresso, especially not in the context of old Cinema 4D scene setups. Within the new contex Scene Nodes go way beyond Xpresso since they define the complete behavior of this (sub)scene.

Scene nodes come at the very end of the order of execution, they simply cant have any influence on the scene, otherwise they would need to be a part of the old object system, which they are meant to replace later on.

Please get in contact with MAXON support. In some cases it can happen that the access was not enabled automatically.

Not that i am aware, but you can check 23 itself and the help once it is available later today.

Yes of course. Both normal and Node materials work. If you use node materials you can also control parameters of the material individually. Bottom image uses the same material for each sphere, upper image as well, but with the seed value of the material connected to the index of the cloned spheres. Of course you need 23 for the attached scene 🙂 Node Material 01.c4d

You can apply Standard and Node materials to Scene Node geometry. It is even possible to control parameters of materials individually

There is no R22. R indicates a version available to subscribers and perpetual users, S indicates a subscription only release. The numbering is continous. Pricing and 23 itself should become available later this day in the MAXON Shop.

It is way to early, but there will be access to scene nodes for plugin developers and i fully expect them to make good use of it. The level of integration with the core was a lot better and deeper with ICE than it is currently for Bifrost. The difference is that Neutron does not use the core, it is the core. Even below the user acessible nodes there is another layer of coded nodes. Neutron / Scene nodes is more than you see in the node editor.

ICE, similar to Bifrost, is working on top of the core of the main app, Neutron/scene nodes is different, it is way closer to houdini since it is not an addition to the system, but at its heart.

It is Neutron, not Neutrino 😉 As was pointed out in the Live Session by Rick, Neutron uses the new modeling kernel. It is not available in an identical manner in the Tech demo though, but the quality and speed advantages are there. The use and display of high object/poly counts is possible due to two main things. The blazing speed of Neutron when it comes to processing them and the equalliy impressive speed of the new viewport that Rick demoed with the fishes. The new viewport is part of the Tech demo and like the rest of Neutron not a feature yet. As was shown in the webcast you can make use of objects modeled in classic Cinema 4D, like the Elephant, and modify them using Neutron.

The new core is not a singular thing. All the development that went into it was also the base for Neutron, the two go hand in hand.

A direct comparison to MoGraph would not be valid, but there is some overlap. For the time being Neutron is a Tech Demo, what it will become in the future we will see.

CA is not in the scope of the tech demo, but i am confident that it will deliver sufficient performance.

API for nodes is available to 3D party renderengine developers. I have no idea if and when this finds it way into more common uses.

Sounds like something that we might aim for when Neutron is not only a tech demo anymore.

What do you want to do with Python? For actual shading it is way to slow, thats why specialised shading languages exist.

For now Neutron is a Tech demo, not a feature. There is no plan to create a nodes only workflow for Cinema 4D, the final goal is a new Cinema 4D based on the Neutron core but with a high level workflow that inherits all the good traits from classic Cinema 4D.

Writing into the application folder is a huge nogo under Windows 10. Either use the prefs folder or any ohte ruser controlled folder. Windows does keep tight reins on appliaction installations to prevent malware attacks.

This is the first time i have ever heard of a problem like that. Did you check with MAXON support?

While i understand the sentiment it would mean that each and every feature request would need to be assigned to a development item, which is a huge load of work especially since most of the time the descriptions and requested function do not fully match the development goal.

We do listen and we even like to listen. Beside issues of timing and development priorities there are a couple of reasons why seemingly straight forward things sometimes take ages. The biggest issue is that there are as many opinions on how stuff should work out there as there are users. Some have slightly diverging ideas, others just plain want the opposite. Derriving at a solution that will serve most without alienating many is hard work and costs a lot of time. Another big issue i that many ideas simply go against the technology behind it. We can't implement them without braking other stuff. Our continued work on the new core has helped adressing a host of issues already, but it can't solve everything. A very time consuming issue is that many of the small issues have pretty big consequences and just making sure we are not making things worse costs a huge amount of time. So please keep ideas coming, be it via the hopefully soon available again webform, trade shows, support mails or even on the forums. But please understand that we can't react indivudally to every input we get, it would add quite a bit to our workload and delay things further.

R20, or even any specific version or feature, didn't have much of an impact on the decision. This is about the over all usefulness and what it helped to create, not about some specific features.

The result node can show you values per frame, for multiple values per frame use the print node asset.

About 30 seconds that will help us to know what you want. https://docs.google.com/forms/d/e/1FAIpQLSfTSisNMlEEzmDMRlwaaOUWxmv1bXSElaMF6oUPBg2gxRXc6A/viewform?fbclid=IwAR1ZNh7vIrpsvet8QJ8VCD7Vx7RT6NSb5tlJsO7DJqjXPeTkwdsF901vQtA Thank you :)