Cinema4D 2022.1-[R10] (Previous stable) (26.03.2023)

[SSmolak]

Using mix in Albedo channel cause huge 10-15 seconds ( depends of scene complexity ) lag, freeze of whole C4D while editing nodes. Other channels like specular, metallic works fine with mix. Tested in Universal and Standard Material

Image Adjust node, brightness adjustment - these sliders value ranges are totally out of way. Most of them should have values from -1 to 1. There is no way to adjust using sliders. I reported this many times...

[SSmolak]

Another 15-20 seconds lag :

LAG.zip

(3.98 MiB) Downloaded 121 times

This is terrible... I will try to isolate this in scene and check using previous studio driver.

[MyDearestHao]

Using chaos to mix non-repetitive textures in two shaders, an error occurs, and more than two cannot be displayed at the same time. Only one can be displayed, the other will be replaced with the same.

[Kalua]

I don't understand: why after working with many takes with the model, I get this weird behavior, different model conditions when rendered on Live viewport window and Pictureview Render.
My .orbx files are not loaded on Production Rendering... they used to, a couple of hours ago... no idea what happened to get this different behavior.
What could cause this sudden behavior? From takes 1-8, .orbx are loaded on Production Render. Take 9 it won't... All setups are the same.

EDIT: so yeah... solved: had to delete the problematic takes and create new ones. No more problems.

[aoktar]

Using chaos to mix non-repetitive textures in two shaders, an error occurs, and more than two cannot be displayed at the same time. Only one can be displayed, the other will be replaced with the same.

I don't think that's about chaos. Maybe a specific bug to detect material assignment for on this small scene. Is that reproducible on a different scene? Always give an example scene

[aoktar]

Using mix in Albedo channel cause huge 10-15 seconds ( depends of scene complexity ) lag, freeze of whole C4D while editing nodes. Other channels like specular, metallic works fine with mix. Tested in Universal and Standard Material

alb_mix.jpg

Image Adjust node, brightness adjustment - these sliders value ranges are totally out of way. Most of them should have values from -1 to 1. There is no way to adjust using sliders. I reported this many times...

Most likely you have something specific to you that's giving lag. Be sure "Faster viewport textures" are ON and alternatively use low viewport texture resolutions for the material. Even make your material from scratch or delete some textures until find the problem.

[lionlee19]

Hi Aoktar,

Please reply to my questions about C4d python here if you have time
I cannot find any resource on the web.
Thank you very much
viewtopic.php?f=87&t=56039&start=30

Using mix in Albedo channel cause huge 10-15 seconds ( depends of scene complexity ) lag, freeze of whole C4D while editing nodes. Other channels like specular, metallic works fine with mix. Tested in Universal and Standard Material

alb_mix.jpg

Image Adjust node, brightness adjustment - these sliders value ranges are totally out of way. Most of them should have values from -1 to 1. There is no way to adjust using sliders. I reported this many times...

Most likely you have something specific to you that's giving lag. Be sure "Faster viewport textures" are ON and alternatively use low viewport texture resolutions for the material. Even make your material from scratch or delete some textures until find the problem.

[MyDearestHao]

It has been reproduced, and the highlights even turn black

[JEEK]

Hadn't received a response so I'll include a screen grab - Shape Field no input option for c4d
2022.1 stable c4d 2022.1 stable SA

It will not support it pretty soon.

Hey Aoktar,

Sorry to bother, but your response in the quote above confused me. Did you mean to say "It will support it pretty soon", or "It will not support it anytime soon"?

Thanks in advance and big thanks for all the updates.

[frankmci]

It has been reproduced, and the highlights even turn black

I can confirm this. It seems like every Chaos node writes to the same texture address space, so that every time one has to re-calculate, it overwrites any previously generated output.