Cycles for Softimage

[I3D]

3080 RTX working, thank you Shekn 🙏

[wireframex]

Works for me
Thanks a lot Shekn

[avalon_70]

Thanks for all the work you are doing Shekn.
Testing the new version I realized one thing, the "image" nodes premultiply the alpha channel by default, among other things without the possibility of choice.
An option to choose whether to use alpha or not would be handy.

[avalon_70]

I found a bug.
I'm famous for this, my fellow programmers hated me for it..
By internally linking the image node in a compound, Sycles crashes.
Even doing the same test in a normal texture crashed the whole computer.

[Maximus]

i've noticed that there are quite some parameters missing, i dont know if they also got removed from the blender cycles but, the progressive render option isnt there anymore, and so the cache geometry option which was handy
everytime i use a render region it takes a bit to load because it probably calculate all geometry in the scene everytime

[wireframex]

Hi Shekn

it seems HDRMaster doesn't work anymore with the last sycles plugin
Phil

[Shekn]

avalon_70: thank you very much. Both your notes are accepted. I will fix it.

Maximus: about progressive mode. By default the render always use progressive mode. In fact there are no other modes in Cycles. But there is some secondary parameter, which allows to mimic the tiling render mode. In Blender you can activate Performance - Memory - Use Tiling and set small tile size (32 or 64). In this case it will render each separate small tile instead of the whole image. Under the hood it store intermediate render results in separate exr-file in the system temp directory (user don't know about it, but this file is created and destroyed after render ends). In Sycles there are some problems with these temporary files, so, this tiling mode is hidden from the UI.

About geometry cache. It does not needed anymore. Sycles use internal Softimage caching system and in some cases it update scene changes without recreating internal render scene from scratch. But in some cases it should do this (recreate the scene). It happens when you create or delete a new object, hide or unhide something, change hierarhy or add property to the object. In all these cases it's more easy and clear to create the new scene for the renderer instead of use the scene from the previous render call. Of course, for heavy scenes it takes some additional time. But if you change materials, camera position, object positions, light sources parameters, then it should only update these changes, and render should start very fast.

wireframex: HDRMaster does not work, because ImageTexture node is changed. This addon should be updated, and it's quite easy. May be when I found some additional time.

[opoppopopp]

...But if you change materials, camera position, object positions, light sources parameters, then it should only update these changes, and render should start very fast...

Can we have a toggle in UI, to force this mode?
(Force NOT to update geometry, but ONLY "materials, camera position, object positions" etc.)
To eliminate any unnecessary scene re-export, in case something dirty the scene wrongly, and trigger that export.

BTW. maybe it sounds useless, but for my daily Sycles experience, it really help me to avoid unnecessary update
Hard to explain its difference than set render region update to manually which I currently rely on.

[avalon_70]

Hi Shekn, I can't find the "background" tab in the render panel.
Was it moved somewhere else?
In the "Denoising" tab there is only the "OpenImage" entry, but I'm testing it with a GTX 1070, is that the reason?

[Shekn]

opoppopopp: I will try to think, is t possible to implement something like "non-accurate update" mode. In this mode we should update only items which should and can be updated, and ignore all other items. As I understand this is exactly you mean.

avalon_70: Background tab is now called World (as in Blender). Background color can be defined by built-in Softimage Ambience parameter.


About OptiX denoising. At the start the addon use built-in Cycles render function to detect what render devices are allowed. If there is some OptiX device, then it show OptiX denoiser in the list of denoisers. But if by some reasons OptiX device is not allowed, then it shows only OIDN denoiser. I don't fully understand how Cycles render detects available devices.

[opoppopopp]

"non-accurate update" mode. In this mode we should update only items which should and can be updated, and ignore all other items.

Yes.
"non-accurate, so that its guaranteed a faster region update"

Because for heavy scenes, in my experiences, many trivial touch here and there, will often trigger a full scene re-export...

[wireframex]

In the "Denoising" tab there is only the "OpenImage" entry, but I'm testing it with a GTX 1070, is that the reason?

When you have an OptiX GPU compatible you will get this :

[avalon_70]

avalon_70: Background tab is now called World (as in Blender). Background color can be defined by built-in Softimage Ambience parameter.

About OptiX denoising. At the start the addon use built-in Cycles render function to detect what render devices are allowed. If there is some OptiX device, then it show OptiX denoiser in the list of denoisers. But if by some reasons OptiX device is not allowed, then it shows only OIDN denoiser. I don't fully understand how Cycles render detects available devices.

Ah, I understand. However, the transparency parameters are missing:


I tried on my laptop which has the RTX 3060, and optix is ​​present (but I had to update the drivers first!)

[avalon_70]

In the "Denoising" tab there is only the "OpenImage" entry, but I'm testing it with a GTX 1070, is that the reason?

When you have an OptiX GPU compatible you will get this :

Thank you

[I3D]

Ah, I understand. However, the transparency parameters are missing:

It's actually in the film tab, just like in Sycles.

[avalon_70]

Ah, I understand. However, the transparency parameters are missing:

It's actually in the film tab, just like in Sycles.

OOkk, thank you.
rather curious position..