OTOY Forums

HTK421 wrote:

"Activate it from Settings/c4d shaders->use osl for c4d noise/gradient"

Im a bit confused,... do we CHECK or UNCHECK this box to use C4D shaders?
The wording suggests that when the box is checked we are using OSL instead of C4D

Also, do we CHECK or UNCHECK 'Enable C4D Shader Baking ?
Having this checked suggests that we are still baking noises instead of making them procedural

c4d shaders.jpg

Thanks

CHECK it! Then it will use OSL script for C4D shaders.

VVG wrote:

aoktar wrote:

frankmci wrote: This is an XB build, undergoing rapid development by very busy people. Not every question will be answered, or should be answered. This is triage. It's a bit different with an officially stable release, but for this thread, cool your freakin' heels, dude.

It's a truth. Also I cannot work if I try to spend much time on every questions or problems. Thanks for explanations!

I do not ask stupid questions every 5 minutes. I've been here too long.

Who else do I need to ask about the announced new features 2020.1 if even core dev are silent how they work?
Are they just gone (Vectron Volumes)?

It's not available in C4D plugin and it's working with some scripted nodegraph in standalone. It's not implemented because of some hardnesses and having problems to able to do that. It will be available when I/we can solve that.

aoktar wrote: It's not available in C4D plugin and it's working with some scripted nodegraph in standalone. It's not implemented because of some hardnesses and having problems to able to do that. It will be available when I/we can solve that.

Well, that answer is enough.
And there was no need to create problems with my behavior.

We, as users, should be aware of what is planned, what is already at the moment in integration.

Thanks

VVG wrote:

aoktar wrote: It's not available in C4D plugin and it's working with some scripted nodegraph in standalone. It's not implemented because of some hardnesses and having problems to able to do that. It will be available when I/we can solve that.

Well, that answer is enough.
And there was no need to create problems with my behavior.

We, as users, should be aware of what is planned, what is already at the moment in integration.

Thanks

Luckily there is a forum that has the latest updates and road-maps for us, users, to read at our leisure. Our money pays for the use of the program not the rights to instant recognition. I get anxious too so I feel your energy but these peeps just wake up and do work like the rest of us. Try and show some empathy and see the big picture. I am just as excited for the stable release but it's all in time.

Thanks!

VVG wrote:

aoktar wrote:

VVG wrote:ok

viewtopic.php?p=375244#p375244

If you don’t have an answer, say so. I have no answer to this question yet

Yes you do have your answer. Be patient. Its a beta test (look at the heading - EXPERIMENTAL).

Being rude to the developers isnt going to get any favors done.

BadBilly wrote: Yes you do have your answer. Be patient. Its a beta test (look at the heading - EXPERIMENTAL).

Being rude to the developers isnt going to get any favors done.

Do you want to explain to me what and how it works on this forum? )) Good luck and optimism to you.

Did the function of the ALT key change in the node editor in R20?

R19
LBM + Click Node - Node Option
MMB - Pan

R20
LMB MMB - Pan
Alt+Click Node - Node Option


R21
LBM + Click Node - Node Option
MMB - Pan

eyeonestudio wrote:Did the function of the ALT key change in the node editor in R20?

R19
LBM + Click Node - Node Option
MMB - Pan

R20
LMB MMB - Pan
Alt+Click Node - Node Option


R21
LBM + Click Node - Node Option
MMB - Pan

No, just build same code for different versions. It's working as should be on me

aoktar wrote:

eyeonestudio wrote:Did the function of the ALT key change in the node editor in R20?

R19
LBM + Click Node - Node Option
MMB - Pan

R20
LMB MMB - Pan
Alt+Click Node - Node Option


R21
LBM + Click Node - Node Option
MMB - Pan

No, just build same code for different versions. It's working as should be on me

Ok. Thanks. I will check again.

There is still bug with cloner related to "one instance". Last time cloner didn't displayed first instance. Now cloner doesn't display instance if it count is set to one