OTOY Forums

aoktar wrote:

pxlntwrk wrote:hi,
this release is highly unstable on my side.
I notice that the interactivity is very reduced the objects(obj,mat, param...) that we manipulate are not always updated in the Liveviewer.
Sometimes when we change a parameter on an object, all the cpu are loaded at 100% and we have to wait for octane to give us back control, sometimes several minutes.
All in all here's a collection of some bug reports if that helps.

ps:These concerns appear with this version 2020.2, everything works fine with 2020.1.5.

thanks

I don't know what's the issue on your side BUT there is NOT ANY Changes in plugin side to cause these kind of issues. Please be more specific and tell is it for one scene or many? And give more info, what's OS/C4D versions, GPUs, RTX usage.

EDIT:
I see some logoutputs, thanks for that. I see only render failures in one log, there's nothing for error in others.

pxlntwrk wrote: I just noticed, that the vram is full and the ooc doesn't want to kick and boom..
and another thing plugin side, when i remove AOV input the pass stay visible in the live viewer and and don't want to leave until I insert a new input.

pxlntwrk wrote:Yes, I removed the objects that saturate the vram and I found my ease;),
but it's still strange that the OOC does not want to start up?
For the new feature I understand that you have in a hurry to make a release (what the hell all these branches ) ... no problem it was just to postpone.

take your time and do a good job as usual..

VVG wrote:Where to get information on new nodes?

How to work with them?

- New texture nodes: composite, channel [invert / map / merge / pick], rayswitch, spotlight_distribution and etc


Where is the explanation of how to work with tonemapping now?

Thx

Mikla wrote:

aoktar wrote:

Mikla wrote:Driver: 457.30 3080 and 1070ti

please send me the scene if you can

I'm tryıng to replicate the error with another scene as I'm not allowed to share the one I'm working on.

It's a heavy scene with lots of instances, geometry and scatter. Getting this on the console:

mojave wrote:
Hi Mikla,

You might get this type of errors on the log if the scene needs more VRAM than you have available, have you tried enabling out of core?

If you did already, we would need more information to be able to replicate the issue, usually a sample scene and your HW setup and device settings would help so if you can share those that'd be greatly appreciated.

Thank you.