OctaneRender for Softimage released!
-
Hirazi Blue
- Administrator
- Posts: 5113
- Joined: 04 Jun 2009, 10:15
OctaneRender for Softimage released!
Apparently otoy has officially released OctaneRender for Softimage,
initially as an "open beta" at a reduced price.
Read all about it here.
Hat-tip: face (xsiforum.de)
initially as an "open beta" at a reduced price.
Read all about it here.
Hat-tip: face (xsiforum.de)
Stay safe, sane & healthy!
-
luceric
- Posts: 1252
- Joined: 21 Jun 2009, 22:08
Re: OctaneRender for Softimage released!
Although it's just 3 days old, this is the first time I hear of this. Did these guy release release this and not publicize it anywhere?
Last edited by luceric on 05 Sep 2013, 15:51, edited 1 time in total.
-
Falam
Re: OctaneRender for Softimage released!
I hope they didn't rush it out the door, never tried Octane. The price is reasonable, probably beta users get it for a real sweet price !
-
face
- Posts: 57
- Joined: 10 Jan 2010, 11:28
Re: OctaneRender for Softimage released!
You´re fast ;)
Have post it first in the xsi-forum and had the intention to post it later here.
And no, the date of release wasn´t monday, it was yesterday.
It should be released monday and the forum topic was written, but there was an issue which i had to solve and the topic was offline.
Build now a demo, so that anyone can test it for free...
face
Have post it first in the xsi-forum and had the intention to post it later here.
And no, the date of release wasn´t monday, it was yesterday.
It should be released monday and the forum topic was written, but there was an issue which i had to solve and the topic was offline.
Build now a demo, so that anyone can test it for free...
face
-
ChrB
- Posts: 55
- Joined: 10 Jun 2009, 11:26
Re: OctaneRender for Softimage released!
Full release or....
LIMITATIONS
- The refresh button on the preview windows isn´t supported and will cause a crash.
- It isn´t possible to render instances.
- Softimage ICE particles and strands aren´t supported.
- Shader compounds aren´t supported.
LIMITATIONS
- The refresh button on the preview windows isn´t supported and will cause a crash.
- It isn´t possible to render instances.
- Softimage ICE particles and strands aren´t supported.
- Shader compounds aren´t supported.
Arnold for the masses!
-
Bullit
- Moderator
- Posts: 2621
- Joined: 24 May 2012, 07:44
Re: OctaneRender for Softimage released!
Yeah the limitations are severe.
-
face
- Posts: 57
- Joined: 10 Jan 2010, 11:28
Re: OctaneRender for Softimage released!
Yes, the limitations are severe.
I want to make first the basics perfect before i work on the ice part.
That´s why it is a beta, not a full release.
Instances as example, are a basic and it´s not simple to implement they for me.
Especially when you hide some parts. Other renderers as example, like MR and 3Delight, can´t handle this correct...
And at last, the demo is ready to download at:
http://render.otoy.com/manuals/Softimage/?page_id=331
face
I want to make first the basics perfect before i work on the ice part.
That´s why it is a beta, not a full release.
Instances as example, are a basic and it´s not simple to implement they for me.
Especially when you hide some parts. Other renderers as example, like MR and 3Delight, can´t handle this correct...
And at last, the demo is ready to download at:
http://render.otoy.com/manuals/Softimage/?page_id=331
face
-
mixepix
- Posts: 78
- Joined: 09 Aug 2010, 13:17
- Location: Sweden
Re: OctaneRender for Softimage released!
I tried the demo-plugin and it was pretty nice! How far off is a version that can handle instances and strands?
----------------------------------------
http://vimeo.com/mikaelpettersen
http://vimeo.com/mikaelpettersen
-
cheeseburger
- Posts: 108
- Joined: 20 Oct 2011, 08:56
Re: OctaneRender for Softimage released!
Exactly ! ! !
-
face
- Posts: 57
- Joined: 10 Jan 2010, 11:28
Re: OctaneRender for Softimage released!
I´m working currently to solve a bug in the render preview on downscaled previews.
Also the Render Region is on the plan.
Then i must solve two or three simple issues.
After this is done, i will implement the instances and at last, ice support.
About instances, because i haven´t seen a renderer which handles instances correct, except the hardware renderer, the first implementation will be realy basic.
This means, nested instance groups like the image below will not work.
The best result would be, to get what you see. I hope i can realize that sometimes...
face
Also the Render Region is on the plan.
Then i must solve two or three simple issues.
After this is done, i will implement the instances and at last, ice support.
About instances, because i haven´t seen a renderer which handles instances correct, except the hardware renderer, the first implementation will be realy basic.
This means, nested instance groups like the image below will not work.
The best result would be, to get what you see. I hope i can realize that sometimes...
face
You do not have the required permissions to view the files attached to this post.
-
pezetko
- Posts: 40
- Joined: 08 Jun 2009, 23:58
Re: OctaneRender for Softimage released!
face wrote: About instances, because i haven´t seen a renderer which handles instances correct, except the hardware renderer, the first implementation will be realy basic.
This means, nested instance groups like the image below will not work.
The best result would be, to get what you see. I hope i can realize that sometimes...
face
Default Mental Ray doesn't have any problem with Instances, e.g. with this setup.
Arnold Renderer also works without problem with Instances.
Until Octane has proper instance and Ice tree support with correct motionblur (transformation, deformation and camera blur (also correctly computed in reflection/refraction including glossy one)) I don't think it will be interesting option. Hope you sorted it out soon and provide something that competition doesn't have. Cheers!
You do not have the required permissions to view the files attached to this post.
-
face
- Posts: 57
- Joined: 10 Jan 2010, 11:28
Re: OctaneRender for Softimage released!
Try to hide the marked one...
I haven´t Arnold, only MR and 3delight, sorry. Wouldn´t write which renderes i have tested.
face
I haven´t Arnold, only MR and 3delight, sorry. Wouldn´t write which renderes i have tested.
face
You do not have the required permissions to view the files attached to this post.
-
xsisupport
- Posts: 713
- Joined: 09 Jun 2009, 09:02
- Location: Montreal Canada
Re: OctaneRender for Softimage released!
That all works in Arnold. Or more accurately, the SItoA plugin correctly parses the scene and exports it to Arnold.
Why is this specific setup considered the benchmark of whether or not a renderer supports instances?
BTW, I assume Model_Instance is an instance of ModelFirst, but you changed the name.
Why is this specific setup considered the benchmark of whether or not a renderer supports instances?
BTW, I assume Model_Instance is an instance of ModelFirst, but you changed the name.
-
face
- Posts: 57
- Joined: 10 Jan 2010, 11:28
Re: OctaneRender for Softimage released!
Correct, the Model_Instance is an instance of ModelFirst.
For me this is considered as a benchmark because if i can convert it, then all other messy possibilities should also work, i hope ;)
face
For me this is considered as a benchmark because if i can convert it, then all other messy possibilities should also work, i hope ;)
face
-
pezetko
- Posts: 40
- Joined: 08 Jun 2009, 23:58
Re: OctaneRender for Softimage released!
Thats correct behaviour.
If you hide marked instance, than the Null that represents instanced object si also hidden in the viewport, try it. And in the render everything that is under that hidden instanced model is also hidden.
But on the opposite site, if you hide only the geometry object under original model (e.g. polymesh), than instance representing null is visible but the geometry itself is hidden, which mean that everything else (every other object) will stil be renderable.
Maybe the geometry should be hidden in viewport too (if instance is hidden), becouse it's more expactable behaviour, but it's linked to the original polymesh object (try hide that and you can see that it hides too in the viewport and in the render).
It would requires another connections and switches which would induce another complexity and reduce speed. And it's generaly not good workflow to do nested instances and models in XSI becouse every model name will be in global space always, no matter how deep it's nested under other models.
If you hide marked instance, than the Null that represents instanced object si also hidden in the viewport, try it. And in the render everything that is under that hidden instanced model is also hidden.
But on the opposite site, if you hide only the geometry object under original model (e.g. polymesh), than instance representing null is visible but the geometry itself is hidden, which mean that everything else (every other object) will stil be renderable.
Maybe the geometry should be hidden in viewport too (if instance is hidden), becouse it's more expactable behaviour, but it's linked to the original polymesh object (try hide that and you can see that it hides too in the viewport and in the render).
It would requires another connections and switches which would induce another complexity and reduce speed. And it's generaly not good workflow to do nested instances and models in XSI becouse every model name will be in global space always, no matter how deep it's nested under other models.
-
pezetko
- Posts: 40
- Joined: 08 Jun 2009, 23:58
Re: OctaneRender for Softimage released!
Whats more fun in XSI is is Visibility Override property.
It can be on Polygons (and Clusters), Objects, Groups, Layers, Partitions. And every group (Partition, Layer, Group) has its own Visibility property also. So resolving this conflict is sometimes pretty hard.
Especialy if you hope that Partitions property will always override everythink even the overried properties under them. Group overrides objects and with Layers... hope nobody in team use Layers for forcing to set a visibility flags.
It can be on Polygons (and Clusters), Objects, Groups, Layers, Partitions. And every group (Partition, Layer, Group) has its own Visibility property also. So resolving this conflict is sometimes pretty hard.
Especialy if you hope that Partitions property will always override everythink even the overried properties under them. Group overrides objects and with Layers... hope nobody in team use Layers for forcing to set a visibility flags.