Cycles for Softimage

[FXDude]

Hi,

First just to say wow! and thanks for these great ICE enhacements! And I will definitely be trying some of them!


And I also wanted to post a preliminary pic of the classic classroom.

This is with the denoiser which I'm attempting to get a denoising process working with it
     ( or in this case -> deblotching process of the pre-denoized out )

Otherwise render is very quick! (quicker than I remember!)

this (currently blotchy) image was a minute long to render,


I also found Bumpmaps to easily look very good and fine at any distance.

_____________
One question though, is there a setting to allow for sampling noise patterns to change between frames?
as it would greatly ease cross-frame sample merging.


__________________________
Otherwise all in all eveything is quite stable and predictable, and everything I tried seemed to have worked great!
But if I can report some bugs (one of which is holding me back)

1- I am having some systematic crashing as soon as the first frame finishes rendering
when specifying more than one aov's in exr format (for me is currently the biggest roadblock)

all ouput AOV's have to be all png out (and therefore clamped) ,
and maybe the main beauty would allow full depth EXR's wiuthout crashing

   ( I also didn't test yest with the latest build )

___________
2- I don't know if it's common to all meshes, or how possible it would be to fix,
but most of the meshes in this classroom had to be triangulated for them to correctly be interpred by cycles.


Anyhoo, thanks again & cheers!

 

[FXDude]

I mentioned you should attach at least 1 example for each node so newbies could get accostumed to what the shader does.
Cheers.

Maybe these links can be usefull :

https://store.blender.org/product/cycles-encyclopedia/
https://www.blenderguru.com/articles/cy ... cyclopedia

Cheers

PS: If using Sycles and havent done so yet, you might want to download the documentation (pdf) on his site.

Which I found to be not only helpful, but quite essential for quick 'to the point' examples of how to get things working!

https://ssoftadd.github.io/syclesPage.html

[FXDude]

To post an a bit nicer pic (also with native denoiser)
more densely sampled at 512 wich took 12 minutes at 1080p



(Very little is textures yet, just a ref for debloching)

[MKXSI]

Next update 1.4. Download here: https://ssoftadd.github.io/download/Sycles_1.4.xsiaddon

What's New:
1. Compiled with the version of Cycles from Blender 2.79. In particular, some render parameters have been added (and some have been removed). In most cases this is technical parameters.
2. Added denoising feature and Shadow Catcher property to polygonmesh object.
3. Standard XSI-hairs render support.
4. GPU rendering. The device for rendering can be specified on the Performance - Additional Settings - Device of the render parameters.
5. Two new tutorials on the manual (23 and 24) about how to render standard XSI-hairs and how to use Ray Visibility.

For testing GPU-rendering I used Nvidia card. I don't know how it will work on Radeon. So, if somebody can test Radeon - it will be great. But there are no guarantee that everything will be fine.

Dosent Recognize AMD Radeon RX VEGA 64. I can see it in the render options but doesnt render. when checked as renderer

[Shekn]

FXDude, I test, and there are no any crashes with rendering and saving several *.exr output channels. Please, make a screen with setup of your output parameters: names of channels, output paths, may be frame resolution. Did you turn on/off parameter Output - Multi-Layer EXR - Combine Render Passes to Single EXR in the render properties?

About non-proper meshes. Please, send me an example object. In obj-format, for example. I will try to understand what you mean and why it happens. It is possible, that the problem not in Sycles, but on Softimage . How it understands input geometry.

MKXSI, does you use the latest version of the Sycles? May be it turns working after version 1.4. But in any case, there is one big problem, why I can't promise anything about Radeon gpu-s - all computers which I can use for tests have Nvidia graphic cards. So, it is hard to find the reason why something does not works.

[FXDude]

It is possible, that the problem not in Sycles, but on Softimage . How it understands input geometry.

Indeed, and it may also be something up with this mesh.


here is a link to the scene I've been using,

    ClassRoom_Sycles_v16.scn


You can try setting one or several AOV outputs to EXR,
here the crashing happens upon writing of the EXR's after the first rendered frame of a sequence (no error messages that I could see),

for the poly issue, at the root is the walls mesh, and if you remove it's triangulation operator, here the mesh tesselation gets mangled in the render,
and similarly, if you 'filter polygons' at an angle of 3 (to untriangulate) any item, tesselation also is affected.

I'm also going to try with the latest build, currently using v1.74

Thanks & cheers, and let me know if there's other elements you need!
 

[Shekn]

Thank you for your scene. Now I see the bug with rendering of non-convex polygons. Also the Softimage crushed when you try to save exr-files into fiolder, which is not exist. I will fix it. If you create folder for files before rendering, then all be ok.

[FXDude]

 Hi, indeed it was the folder creation that it didn't like, by removing the tokens and specifying explicit paths, the render went smoothly!

so thanks, and also great to know it can be adressed on your side!


 

[Shekn]

Small fix update 1.7.7. Download here: https://ssoftadd.github.io/download/Syc ... 7.xsiaddon

Or simply dll-file from here: https://mega.nz/#!VhICiILQ!TOUH78pLYdVN ... N6UKMaCoOA

Fix only to bugs:
1. Correct render of non-convex polygons
2. Create folders for saving output render images, if these folders are not created before.

[wireframex]

Thanks a Lot Shekn

[FXDude]

Hi!

So all concave while untriangulated/cleaned mesh tessalation seem to resolve correctly,
and arbitrary tokens in AOV output paths seem fully stable!

  And talk about fast fixes  Lol!  
 
       
 
                             

 


 Thank you, and nice work!
 

[wireframex]

Hey Shekn

Could you tell me me if Cycles works with RTX graphic cards like 2080 ti ?

Regards
Phil

[Shekn]

No by two reasons. The first - Cycles is not officially support it yet, but Blender team working about it. The second - for using it inside Softimage, *.cubin files should be recompiled for supporting this type of GPU.

[Daniel Brassard]

To complement Shekn response,

The current Cycles will work on a GeForce RTX graphic card but will not use the new RTX realtime ray tracing platform. For that, we will have to wait for the Cycles team to catch up. The Cycles team will need to use the new SDK to program specific instructions that will unlock the RTX platform to Cycles.

I get the same issues between OptiX 5.1(pre-RTX) and Optix 6 (with RTX).

Microsoft also announced DirectX 12 DXR at GDC2019 which will accelerate raytracing on native RTX GPU and provide raytracing to older GTX and AMD GPUs.

https://devblogs.microsoft.com/directx/ ... aytracing/
https://www.nvidia.com/en-us/geforce/ne ... ming-soon/

NVidia tutorials part 1 & 2 can be found here:

https://developer.nvidia.com/rtx/raytra ... ial-Part-1

There is also an important property brought by the adoption of the NVlink that was not there before, the use of the GPU memory. Before NVLink, users with multiple GPU cards were limited by their single cards memory and rendering on GPU was limited to the single card setup (no memory adding). With NVLink, the memory of RTX GPU get added up increasing the amount of memory available to the GPU raytracer.

Interesting time.

[wireframex]

There is also an important property brought by the adoption of the NVlink that was not there before, the use of the GPU memory. Before NVLink, users with multiple GPU cards were limited by their single cards memory and rendering on GPU was limited to the single card setup (no memory adding). With NVLink, the memory of RTX GPU get added up increasing the amount of memory available to the GPU raytracer.

That's why I'm very interested by this amount of VRAM

2 RTX 2080 ti --> 22 Go VRAM but just a little power less

[wireframex]

No by two reasons. The first - Cycles is not officially support it yet, but Blender team working about it. The second - for using it inside Softimage, *.cubin files should be recompiled for supporting this type of GPU.

Hope it will be done soon