www.si-community.com

That's... seriously impressive.

Was really impressed as well. I expected it would slow down above a few thousand hairs, because Octane uses tube geometry.

I like the look of the rendered images compared to redshift, I runned some test some times ago, same HDR same geo ;-)
The plugin is not so advanced than RS thought...

True, although comparing the plugins isn't fair at the moment. Octane's API itself is limited to building one big node graph using a rather limited set of nodes. It seems to be closer to Maxwell, where photo realism is a priority, at the expense of a lower degree of user control.

Hi,

Here are a few clips from Stephen showing some of the supported things as they came out,
(from 3 weeks, to a year ago)


Octane4Softimage V3


Part9
Deformation motion Blur (Exaggerated)



Part8
VDB's, in this case imported from Houdini,
and probably therefore also suppports ExplosiaFX generated (standard) VDBs



Part7
"RenderMapping" Ao ... Reflections... uv coords.... ... etc ..



Part6
Render Channel support (AOVs)



Part5
Custom "Render Layers"



Part4
RenderRegion Support
Enhanced Environment Shading
and use of "Medium" (fog?) shading.



Part3
Procedural "Daylight" environment shading




Part 1 & 2
Object (and full scene MB from cam motion) motionblur,
and visible BG environment shader.



Intergration seems quite complete, and looks really fast!

Also, Deformation MB and custom AOV support seems to cover the remaining production critical aspects.

While Rendermapping and VDB Support remains definately welcome and not by any means minor features.


Seems a little pricey though, maybe would they consider pricing relative to the "prevented from being sold" status of Softimage (?)

RC2 just released: https://render.otoy.com/forum/viewtopic ... 0&p=322340

FIXED:

• ICE Particle Orientation from Euler Rotation is now correct.
• ICE Point Segment Size wasn´t used, which is fixed.
• Swapped the "Tonemap Type" under the Misc settings.
• Motionblur is now working correct with subframes.

ADDED:

• Added support for deformed motionblur.
• Added parameter for deformed motionblur subframes.
• Added parameter to enable deformed motionblur for each mesh in the mesh properies.
• Added scene for motion blur.
• Added scene for deformed motion blur.
• Added scene for texture baking.
• Added Octane materials to Get -> Material

CHANGED:

• Changed default Point Segment Size from 0.0025 to 0.025.
• Changed the kernel in the render layer scene to info channel / render layer id, to show the layer colors .

with these additions (and quoted posts below), that sounds like pretty good ICE integration..
I'm soo curious!

wireframex wrote: ↑12 Jul 2017, 18:36

xsi_fanatic wrote:Nice ! Curious to know if this support render regions within the SI viewport.

Yes it works

Note : From Demo_Project created by Face (example delivered with Octane 3.0 RC1 for SI)

rray wrote: ↑11 Aug 2017, 16:15 Instancing test 2,000,000,000,000 hairs in Octane for Softimage

Render time <1 minute per image

ICE support is okay. Strands work and ICE instances and volumes do too which are the two most important bits. Attributes are not supported, for transferring color you have to do some trickery with additional UV sets.

No instance shape animation tho like Arnold, and you probably couldn't do advanced trickery like this (Arnold too)



Octane is very fast though, and the ultraphotorealistic maxwellian look

ongoing development: Hair uvws, new environment options..

https://render.otoy.com/forum/viewtopic ... 443155f028

Also, not sure how it's done, but it's now possible to bake a texture and then use the same texture inside the same tree

 
Ambient Occlusion mappable Environment shader
Great for speedy(-er) fake Env lighting exterior shots (among other things)

     

Rasterisation of Procedural gererators
to allow proceduraly drive displacements.
     

     


.. AND yet another important Feature
(not on the linked forum)

ICE Particle Motion Blur

 

Does Octane supports any of the 'Time Source" types, that appear in image sequences? That option is currently not supported in Redshift and probably will never be supported, as the development of the plugin has practically stopped.

Indeed that would be quite useful. (if not already there?)

For Redshift, It seemed to have been tricky to figure out (as far as I can remember on RS Forums), but apparantly not impossible as Arnold and formely 3Delight have done it..

So if some tech guys here have figured out how to access the output of ClipEffects (to crop, colorCorrect etc..image clips) pehaps we could send a hint to RS?

Otherwise while indeed no or little SI specific features pop-up, SI specific bug fixes -do- get adresses, and all new general RS features are promply updated in the SItoRS plugin.

Image sequences are supported.
The next version will also support changed image access, so if you change an image content, the image will be reloaded.

@juanloredo Image sequences work great indeed but getting sequence time from an ICE attribute instead of scene time probably won't work... might be possible to implement for objects but not per point/Instance because Octane itself only supports static objects for instances afaik.

Sad to hear about Redshift Softimage support being slowed down, didn't know that. Sitoa is also currently lagging behind quite a bit.... makes me expect an end of support announcement any minute. If at all...

Thanks for your reply guys. Indeed I was thinking about driving the sequence time by an ICE attribute like in this video https://vimeo.com/67929785, which I think is supper cool, tried it in Redshift and then find out that its not possible. Maybe one day it could be implemented in octane. Anyways, face, thank you for all the work that you have been putting on developing the plugin, I've been following your videos in vimeo and always get exited, I hope I can give octane a try soon.

On the side topic of the development of Arnold & Redshift plugins, I guess I can't blame the devs, they are just following what ever makes sense financially.

not sure, never tried it but this could be a workaround for some cases: