srek

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.

What Adrien said. Like Hrvoje i am very much looking forward to the announcement.

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.

It seems the distributor messed up by not canceling your MSA in time. Maybe get in contact With MAXON HQ in germany to clear this up.

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 :)

The Iterator is nothing to fear, check the attached scene. Select the Xpresso tag to see the bool that controls all cubes Enable-Iterator.c4d

You can use a list iterator instead of doing each object nod eindividually.

The COFFEE Nodes are used in the softbox setups you are using

All interviews are usually held by one person from HR and at least the head of the hiring department. This ensures that it is not always the same people doing the interviews. From personal experience, as a cat person ;) , i can say that even within every department people here are quite diverse regarding personality and background. Please don't get me wrong, i'm not saying that we are all a happy little Family from the 50s, there are conflicts and clashes, but the important thing is that we tend to work well together.

Yeah, they even took on idiots like Hrvoje, Igor or me ;)

There is no personality type we are looking for. If you could see the current range of personalities that are working here you would know.

You are overestimating the number of available developers. If we were to post such specific job offers we would find no one. MAXON is very flexible in who we employ, so we can get those that fit the company, not only those that match a specific profile.

UX design goes a good deal beyond thinking about feature improvements, it is however a part of our job. A list of improvement ideas is commendable and certainly useful, but on it's own not that much. The bigger problem is finding someone who is able to take seemingly disparate and clashing things and make them work together in a usefull way. The biggest challenges i get as a UX designer for MAXON is to have certain technical options and limitations and quite different user expectations or worse existing workflow paradigmas that clash with the technical necessities. It can be a fun challenge though :) By any means, apply for this, or any other of the job offers, but if possible go beyond what you showed with the list. Cheers Björn

The help is in the making, unfortunately the english translation isn't finished yet. The german help is available though.

This can be done using asset node materials in R20. You can store single nodes or complete materials in an own asset database and use these assets in any number of scenes.

The Open GL Benchmark is a lot more dependent on the specific scene setup than the rendering benchmark, this is mostly due to it also being dependent heavily on single core CPU performance.In the end iIt is more of a compatibility test than an optimal measure for performance. You can see this in the way Cinebench is used by websites and magazines, the OGL benchmark is barely used at all, while the rendering benchmark is among the most used.

Benchmarks need to be updated when they have to be adjusted to support new hardware. They are about supported hardware features and how efficient they are used, not about features of the software itself. Cinebench has its niche not because it is always including some new software features, but because it is a very reliable benchmark for high core count CPUs. Updating benchmarks often without a technical need only leads to problems since all old testresults are incomparable to the new ones. Cinebench will be updated as needed.

Single rays can be shot, where and what you do with them is mostly up to you. On the left the Context node delivers all current render/shading context data, the Ray node in the middle tells you what kind of ray is currently being processed. On the right side is the Trace Ray node that allows you to cast an own ray. I don't know what kind of sampling scenarios you have in mind. Additonaly to the Trace Ray node you also have Ambient Occlusion for sampling If i remember correctly there were examples for rounded edge shaders build by testers, however due to licensing restrictions we can't provide any of these. Current sampling methods only work for surfaces, not volumes, however you can do some effects that take object thickness into account by casting rays inside of them. This is not a SSS replacement though but might be good for some interesting effects. I used this for X-Ray effects and similar. I think you will be able to tell if this is interesting for you or not, once the Demo becomes available.

QFA I have been using R20 Volumes for modeling for some months now and i basically switched completely to it for 3D printing purposes.