www.si-community.com

Draise wrote: ↑20 Nov 2017, 22:14 I get Si crashes on a simple scene too (add cube, add grid, add area light, change viewport render preview to cycles = crash). Also after a project.

No pb here it works very well (Tested Render Region and Preview).
Light strengh default need to be improved.
Denoiser : On
AA Sample : 20
Tile size : 128x128 (best choice here)

OS : Windows 7 x64 - 28 Go Ram
Devices
1 GTX 1070
2 GTX Titan

So finally managed to grab 15 minutes to test Cycles4Soft 1.5 and the report is more good than bad.

First for the good. My pair of 1080 Ti's are both seen by Cycles and render times are apt for seeing both GPU's. Nodal shading behaves as it should and the denoiser works well too.

As for the bugs it's still a tad crashy this mainly occurs with real-time updates to the region render and preview render window. If you disable the automatic refresh the crashes go away (but so does much of the fluidity). Also, the region render suffers from missing blocks on a fairly regular basis (but there's no repeating patterns).

The biggest got-yer I encountered with with regard to colour management. You have to disable it in Soft and use ICIO within Cycles. If you don't do this you'll suffer with 8 bit banding issues.

I didn't explore that far into the feature set as I've been spending more time with X-Particles and Cycles 4D this weekend!

All in all very impressed with the improvements since 1.4 and looking forward to 1.6 whenever that lands. But before then I'll dig a bit further as I want to test Cycles4Soft with Senior Mootz's wonderful addons.

Update 1.6. Download it here: https://ssoftadd.github.io/download/Sycles_1.6.xsiaddon
What's new:
1. Some bugfixes
2. Compiled with the latest version of the Cycles render (from 06.05.2018). This leads to the following changes:
2.1. Add new shader node Principled Volume
2.2. Now displacement has a vector format. It means that for bump or displace we should connect scalar value of the displace not to Displacement port of the material's root node, but to Displacement node and it vector output to the Bump Map port of the material. Examples and some descriptions are on the tutorials 5 and 6 on the manual (https://ssoftadd.github.io/manuals/Sycl ... %20Eng.pdf)

Also there are some new addons related to Sycles. The fist one is GESImporter. Download it here: https://ssoftadd.github.io/gesPage.html
This addon not only for Softimage, but also for Blender. Initially, the idea was to create a tool for transferring scenes from Softimage to Blender with all render parameters and materials. For Cycles, of course. For example, for rendering scenes and animations on free render-farm for Blender. Current version of the addon can export scene only in opposite direction - from Blender to Softimage. Actually it exports only static geometry, camera, light sources and, of course, materials. With this tool, you can easily take a shader or material from Blender (there are a lot of them both paid and free), and send it to Softimage. And then used it for rendering in Softimage.

Two other addons are libraries of materials, which was converted from Blender to Softimage by the previous tool.
The first library is from Blendermada site (http://blendermada.com/). Download it here: https://ssoftadd.github.io/blendermadaPage.html
The second library contains shaders and materials from different locations and packs. Download it here: https://ssoftadd.github.io/shadersPage.html

Is there a test file or example file to see what is the interaction between pbr substance and sycles?
This is what I have been waiting for a full year now.
Thanks.

Ps: when you use pbr for cycles export settinhs on substance, does softimage Sycles picks it up with a correct network shader, oppacity, (pbr saavy)?

Thanks for supporting SI
Mootz plug support will be awesome !!
Phil3

sirdavid32 In fact Substance PBR nodes are not related to Substance. It is only the name of nodes from original addon for Blender (https://blendermarket.com/products/pbr-uber-shader). I named these nodes in the same way. There are no any synchronization for textures and shader nodes for maps from Substance Designer or Painter.

wireframex Support of rendering volumetric data is a main big target for future versions of the Sycles. Not only for emFluid but also for ExplosiaFX, openVDB and so on. All these data can be rendered in the same way. But now I don't know how to do this. It needs more investigations of the Cycles source code.

It will be a great thing for the community because all renderer has stopped development like VRay / Arnold ...
Redshift will never support the famous Mootz plugin and Octane seems to be dead... no news from "Face" More than 2 months now...

wireframex wrote: ↑11 May 2018, 21:26 It will be a great thing for the community because all renderer has stopped development like VRay / Arnold ...
Redshift will never support the famous Mootz plugin and Octane seems to be dead... no news from "Face" More than 2 months now...

What aspect of Eric's Mootzoid plugins can't you use with Redshift?

@shekn, Fantastic work fella. I had wondered with it being nearly six months since the last update if you had given up on Soft. But instead you've surpassed my expectations.

I use X-Particles with Cycles 4D and the integration tools you're providing between Cycles/Soft and Cycles/Blender goes beyond what they're providing. There's so much more choose from when it comes to Blender/Cycles farm services than for Cycles 4D. This give your toolset a major advantage for larger production lines.

jonmoore wrote: ↑12 May 2018, 09:30 What aspect of Eric's Mootzoid plugins can't you use with Redshift?

I'd like a full support for Emfluid

And also a multi GPU rendering support (more than 2 GPU card).
Actually I can't test 1.6 because of some holydays but next week
Phil

wireframex wrote: ↑12 May 2018, 22:27
I'd like a full support for Emfluid

And also a multi GPU rendering support (more than 2 GPU card).
Actually I can't test 1.6 because of some holydays but next week
Phil

Apologies for the late reply.

When it comes to GPU rendering of volumes, VDB seems to be the accepted workflow these days. Even Cycles 4D and X-Particles uses a VDB workflow. I would expect that Eric would have to add some SDK elements to emFluid for Cycles Soft to hook into and Eric has made it clear that in giving his plugins away they're fixed in time (more than fair considering his generosity).

If Cycles 4d doesn't render Xplosia sims natively (both maintained by the same company - Insydium), I can't see this happening for emFluid/Cycles Soft. Could be wrong but it seems unlikely. And the VDB workflow provides excellent results so the only difference will be a slightly more convenient workflow.

Thanks for keeping it updated shekn. It looks like this will become the only actively updated renderer for Softimage soon.. outlives Octane, Arnold (and probably soon Redshift)..

So can it work on a laptop? Description says: V1.4 requires the Windows "Fall Creator's Update" and/or the Cuda Tookit installed for some hardware configurations.
I´m on a laptop, win10 x64

It should works without any additional installs and updates.

I looked for sycles volume principled shader.
It´s not there.
I thought I read about the latest implementations on sycles that had the principled volume shader? or did I dreamed it?

rray wrote: ↑06 Jul 2017, 16:52

by the way, who is the author? I did not found his name anywhere..

Angel 07 (and lately Shekn) on this forum, also made this fabric engine retopo tool:
viewtopic.php?f=27&t=5960

He/she seems to prefer to keep it anonymous

Other plugins by him/her
https://ssoftadd.github.io/

Yeah, zero records on the entire internet. I don´t know how to "THANK HIM/HER". But at least we got this forum. Version 1.6 has principled volume shader!!
What other stuff can he do for adapting I/O between softimage and blender?

Principled volume shader on Sycles 1.6!!