Plugins linking to this thread: (hide)
Sycles 2.4.1Author: Shekn @si-community V 2.4.1 released August 2026 —
This is a full integration of the Blender Cycles renderer into XSI. Version 2.4 is
compiled with Cycles 5.3 (state of July 2026). The second generation of the addon
(since 2.0) is a complete rewrite and works with Softimage 2015 SP2.
New since version 2.1.3 (from the github release notes):
2.4.1: fixed incorrect transforms of instances when the master model has rotation or scale,
repacked with missing DLLs
2.4: Cycles 5.3. New Alpha parameter for the ImageTexture node, Sky Texture with Single
and Multiple Scattering models, Thin Film for Metallic and Glass BSDF, new Raycast
and Scene Time nodes, OSL custom camera, Linear 3D curve shape (also as per-object
override), Geometry Approximation mode for NURBS surfaces, Render Time pass (CPU),
texture optimisation (resolution, limit, tx texture cache) and a detailed scene export
timing log
2.4: renders MaterialX shader trees from the MaterialXSI addon (converted to OSL). Note: OSL shading works on CPU render devices only
2.3.x: Cycles 4.5, OSL support is back, new Metallic BSDF and Set Normal nodes, phase function
for Scatter Volume, Diffuse Roughness for Principled BSDF, more Noise Texture types,
subdivision with motion deform, per-frame texture images, rendering of NURBS surfaces
and curves (via custom properties), tile rendering, fixed shadow catcher, vector input
ports for OSL shaders
2.2.x: nodes of Blender 4.3 (Ray Portal BSDF, Sheen BSDF, Gabor Texture, redesigned Principled
BSDF), current Blender OCIO color profiles, custom velocity grids for VDB primitives,
Particle Info node fed by ICE attributes, denoising of the final passes with OIDN
or OptiX
Supported Softimage features (quoted from the download page):
Polygon meshes and hair geometry
Texture coordinates
Vertex colors
Shaderball preview. For materials, shader nodes and texture nodes
Basic limited support of the following built-in Softimage shader nodes: Phong, Lambert,
Hair Shading, Image, converters between vector, color and scalar
Ambience global environment light
Limited support of built-in Softimage light sources
Model instances
ICE strands geometry
ICE pointcloud instances
ICE geometry attributes (vector, color and scalar) with context per-point and per-object
Volume rendering. In particular supports emFluid, Explosia FX and openVDB for Softimage
volumes
Special VDB Primitive for rendering vdbs without ICE
Output multilayered exr file with all rendered passes
Rendermaps
The following features from Cycles itself are supported:
CPU and GPU rendering. In particular multidevices are supported. This allows you to
use cpu and gpu simultaneously. The libraries for GPU rendering are included in the
package.
All Cycles shader nodes
OSL shaders
OpenColorIO profiles (Blender profile included)
All Cycles output passes (Combined, Depth, Normal and so on)
Color and value shader AOVs
Lightgroups
Cycles camera properties, in particular all panorama modes
Cycles light sources
Denoising by using Open Image Denoise and OptiX denoiser
For more information, full documentation and a list of the available Cycles nodes
see the download page linked below. There is no local backup because the addon is
still frequently updated - the plugin can be downloaded on Shekn's github releases. The source code is available on github there as well.
News concerning 3D DCC business
-
opoppopopp
- Posts: 213
- Joined: 16 Jun 2009, 04:23
Post
by opoppopopp » 02 Nov 2024, 23:58
"Cycles Properties" only work by its default name? (e.g. "CyclesMesh" for polygon)
Names like "CyclesMesh3" won't work?
So that apply properties to Partition/Group can not work?
BTW.
"// INFO : This property can be applied only to polygon mesh object"
So I drag or
"selection(0).AddProperty('CyclesMesh')" to apply it to Group/Partition
-
Shekn
- Posts: 254
- Joined: 30 Dec 2016, 19:18
Post
by Shekn » 03 Nov 2024, 05:15
It seems that the engine now searches for properties by name. It's inconvenient to use. I'll try to understand how it's possible to recognise property by its type. And also add possibility to add property to partition.
-
opoppopopp
- Posts: 213
- Joined: 16 Jun 2009, 04:23
Post
by opoppopopp » 03 Nov 2024, 19:02
Shekn wrote: 03 Nov 2024, 05:15
It seems that the engine now searches for properties by name. ...
Thanks.
Don't know much about C++, but how about search for Name" CyclesMesh
* " instead of "CyclesMesh", so that "CyclesMesh1...etc." fit. Will just solve the problem
Since I do a little scripting, will this help?
https://xsisupport.com/2013/10/30/findi ... s-by-type/
-
Shekn
- Posts: 254
- Joined: 30 Dec 2016, 19:18
Post
by Shekn » 04 Nov 2024, 05:43
Yes, something similar is required.
-
wireframex
- Posts: 425
- Joined: 08 Jun 2009, 21:02
- Location: France
Post
by wireframex » 15 Nov 2024, 17:58
Hi,
I have tried many things regarding invisible GPU with same issues with Blender :
- Blender 4.2.3 LTS --> CPU+GPU --> Ok
- Blender 4.3 release candidate --> CPU --> Ok / GPU --> NOk
- Blender 4.4 Apha release --> CPU --> Ok / GPU --> NOk
I tried theses with :
- 2xRTX 3090 / windows 11 (Desktop)
- 1xRTX 4090 / windows 11 (Laptop)
EDIT:
Sycles 2.1.3 --> CPU+GPU --> Ok
Sycles 2.2.0 --> CPU --> Ok / GPU --> NOk
Sycles 2.2.1 --> CPU --> Ok / GPU --> NOk
I tried also many different things about dll and libraries (Cuda, Nvidia Drivers, ...) without any success
Phil
Last edited by wireframex on 15 Nov 2024, 18:50, edited 1 time in total.
"without mastery, power is nothing" - Softimage Addict User
CPU 3990x 128 Threads / 2 x 3090 RTX - 24 Go / 96 Go memory
-
wireframex
- Posts: 425
- Joined: 08 Jun 2009, 21:02
- Location: France
Post
by wireframex » 15 Nov 2024, 18:17
Found something new
In Blender System Preferences, if I select only CUDA and uncheck OPTIX :
- Blender 4.3 release candidate --> CPU+GPU --> Ok
- Blender 4.4 Apha release --> CPU+GPU --> Ok
This is a very good news
Final word for SI --> need to uncheck OPTIX somewhere --> @Shekn
"without mastery, power is nothing" - Softimage Addict User
CPU 3990x 128 Threads / 2 x 3090 RTX - 24 Go / 96 Go memory
-
Shekn
- Posts: 254
- Joined: 30 Dec 2016, 19:18
Post
by Shekn » 16 Nov 2024, 13:45
Ok, thank you very much for your research. I will try to understand what it means. Maybe using the new Blender release will solve the problem, or maybe some additional tweaks are needed.
-
opoppopopp
- Posts: 213
- Joined: 16 Jun 2009, 04:23
Post
by opoppopopp » 16 Nov 2024, 21:04
Shekn wrote: 16 Nov 2024, 13:45
Ok, thank you very much for your research. I will try to understand what it means. Maybe using the new Blender release will solve the problem, or maybe some additional tweaks are needed.
Previous post just reminds me one question:
In the UI of Sycles we can toggle ON with BOTH GPU devices (with and without OptiX)?
What that means to Sycles?(Cycles standalone API)
because it seem on blender's UI, Only ONE of them can be selected at the same time: None(CPU only),
OR CUDA,
OR OptiX,
OR HIP?
-
Shekn
- Posts: 254
- Joined: 30 Dec 2016, 19:18
Post
by Shekn » 17 Nov 2024, 04:33
If more than one device is selected in the settings, a so-called multidevice is created for rendering. It uses an internal mechanism to schedule rendering tasks between different devices within this multidevice. If GPU and OptiX are selected, the behaviour is the same. More likely, it will use one physical device for all tasks.
-
wireframex
- Posts: 425
- Joined: 08 Jun 2009, 21:02
- Location: France
Post
by wireframex » 18 Nov 2024, 16:08
In the last Alpha Blender build (18 Nov 01:48) maybe they have made an update about Optix.
Now if I check on CUDA and Optix --> CPU+GPU --> Ok
EDIT : I have done an Nvidia update to 566.14
"without mastery, power is nothing" - Softimage Addict User
CPU 3990x 128 Threads / 2 x 3090 RTX - 24 Go / 96 Go memory
-
opoppopopp
- Posts: 213
- Joined: 16 Jun 2009, 04:23
Post
by opoppopopp » 18 Nov 2024, 16:59
wireframex wrote: 18 Nov 2024, 16:08
In the last Alpha Blender build (18 Nov 01:48) maybe they have made an update about Optix.
Now if I check on CUDA and Optix --> CPU+GPU --> Ok
EDIT : I have done an Nvidia update to 566.14
Think there's nothing to do with 4.3+ because Sycles 2.2 not using that version of API.
BTW. even for blender 4.3 RC it is work flawlessly out of the box, with CPU and/or GPU OptiX or CUDA, on all my PC.
-
wireframex
- Posts: 425
- Joined: 08 Jun 2009, 21:02
- Location: France
Post
by wireframex » 18 Nov 2024, 17:55
opoppopopp wrote: 18 Nov 2024, 16:59
Think there's nothing to do with 4.3+ because Sycles 2.2 not using that version of API.
BTW. even for blender 4.3 RC it is work flawlessly out of the box, with CPU and/or GPU OptiX or CUDA, on all my PC.
EDIT : but not for me 4.3 RC and Alpha 4.4 didn't worked. It seems the Nvidia update changed the result.
"without mastery, power is nothing" - Softimage Addict User
CPU 3990x 128 Threads / 2 x 3090 RTX - 24 Go / 96 Go memory
-
tarkovsky
- Posts: 61
- Joined: 05 Oct 2012, 18:02
Post
by tarkovsky » 23 Jan 2025, 11:22
Hi.
How would you go about creating a decal with Sycles? Trying the Mix Color node, but no luck.
-
Shekn
- Posts: 254
- Joined: 30 Dec 2016, 19:18
Post
by Shekn » 24 Jan 2025, 12:56
Here is an example of the setup.
Use MixClosure node and mix actual shader with transparent shader. Cycles ImageTexture node allows to extract alpha of the texture. Use it as the mask for the mix. Transparent colour should be pure white.
-
opoppopopp
- Posts: 213
- Joined: 16 Jun 2009, 04:23
Post
by opoppopopp » 03 Feb 2025, 20:58
Any good news on "try to compile against updated API for GPU detection problem?"
(seems cycles api code base is updating constantly, but not yet a 'release/4.3' tag
)
-
Shekn
- Posts: 254
- Joined: 30 Dec 2016, 19:18
Post
by Shekn » 04 Feb 2025, 05:11
No news yet
