Is there any plans to support instances octane? When?
I'm having problems with exterior scenes.
Is there any plans to support instances octane? When?
-
thiagobulhoes
- Posts: 77
- Joined: Wed Jun 02, 2010 8:10 pm
- Location: Brasil
- Contact:
-
thiagobulhoes
- Posts: 77
- Joined: Wed Jun 02, 2010 8:10 pm
- Location: Brasil
- Contact:
I like octane, but I'm really disappointed. Ehen I tested the Cycles Blender and support instances! ok the cycle is far from being usable, but support instances and there is a button to disable caustic! the new Indigo RT 3.0, is quite complete (instances, SSS, netrender, OpenCL); octane development is very slow.
Thanks for your encouraging words! 
Unfortunately code doesn't grow on trees and sometimes you have to make fundamental changes that allow later changes. The new render framework is one of these. It was a huge chunk of work. When that is done, we will continue with new stuff and instances are very high on the list.
Please also understand that every user has other needs and if your need is not served immediately it doesn't mean that we don't like you, but just that there are
A) other more important things to do
B) it's a complicated thing that takes time to develop
C) it's a big undertaking that depends on other work to be done first
Cheers,
Marcus
Unfortunately code doesn't grow on trees and sometimes you have to make fundamental changes that allow later changes. The new render framework is one of these. It was a huge chunk of work. When that is done, we will continue with new stuff and instances are very high on the list.
Please also understand that every user has other needs and if your need is not served immediately it doesn't mean that we don't like you, but just that there are
A) other more important things to do
B) it's a complicated thing that takes time to develop
C) it's a big undertaking that depends on other work to be done first
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
-
Jaberwocky
- Posts: 976
- Joined: Tue Sep 07, 2010 3:03 pm
Quote " Unfortunately code doesn't grow on trees "
Hey Marcus
Saw this on my last walk......It was a code tree!
Hey Marcus
Saw this on my last walk......It was a code tree!
You do not have the required permissions to view the files attached to this post.
CPU:-AMD 1055T 6 core, Motherboard:-Gigabyte 990FXA-UD3 AM3+, Gigabyte GTX 460-1GB, RAM:-8GB Kingston hyper X Genesis DDR3 1600Mhz D/Ch, Hard Disk:-500GB samsung F3 , OS:-Win7 64bit
Thanks for that. Made my dayJaberwocky wrote:Quote " Unfortunately code doesn't grow on trees "
Hey Marcus
Saw this on my last walk......It was a code tree!
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Jaberwocky wrote:Quote " Unfortunately code doesn't grow on trees "
Hey Marcus
Saw this on my last walk......It was a code tree!
IT farmers, a new breed of geeks are coming!!!genius btw
windows 7 x64 | 2xGTX570 (warming up the planet 1ºC at a time) | i7 920 | 12GB
-
thiagobulhoes
- Posts: 77
- Joined: Wed Jun 02, 2010 8:10 pm
- Location: Brasil
- Contact:
While I concurr that Octane development feels slow, you got to be fair too.
Indigo RT 3.0 does not support SSS and Bidirectional MLT (Indigos strenght) does not work when you enable OpenCL and material creation is not even close to comfortable. Indigo 3.0 supports SSS but costs you 5 Octane.
Also Octane is a pure GPU renderer, not a hybrid, and to parallelize and implement algorithms for a GPU is a non trivial problem and often enough impossible.
You guys always seem to forget that Octane started at Zero and you keep comparing it to new versions of established renderers.
I think Octane is great, and waiting for a great thing, makes the waiting seem even longer.
Indigo RT 3.0 does not support SSS and Bidirectional MLT (Indigos strenght) does not work when you enable OpenCL and material creation is not even close to comfortable. Indigo 3.0 supports SSS but costs you 5 Octane.
Also Octane is a pure GPU renderer, not a hybrid, and to parallelize and implement algorithms for a GPU is a non trivial problem and often enough impossible.
You guys always seem to forget that Octane started at Zero and you keep comparing it to new versions of established renderers.
I think Octane is great, and waiting for a great thing, makes the waiting seem even longer.
[email protected]|GTX 470@750/[email protected]|ASUS P5Q-D|8GB-DDR2|Win7x64 Pro|Ubuntu 10.10 x64|CUDA 3.21|FW 285.38|Octane 252|Blender 2.59b
-
archigrafix
- Posts: 201
- Joined: Tue Jan 26, 2010 5:37 pm
- Location: FRANCE
...yeah job is never so easy to be done but
being able to work on larger scenes is not a only a user demand amongst the others...It is top crucial evolution of the soft:
I of course know that you know about that it's just a "recall"!?
When you get to work on a large scene (not a mega huge one...I was on a sketchup!) and cant find a way to import in Octane
You can go for some serious questions about the soft usage.
It was a long time I didnt tested on Octane for one of my project and today conclusion is simple:
The import file format is crucial: obj is obsolete, you should go for xml or something that can deal with large scenes and advanced meshes properties... where is the interest having top soft functions and all sophisticated math calculations...if I cant get my model inside?
Just to insist there are priorities in the users demand and those ones (instances etc...) will make a big difference and let Octane go to another universe IMO:idea:
So I cross fingers
being able to work on larger scenes is not a only a user demand amongst the others...It is top crucial evolution of the soft:
I of course know that you know about that it's just a "recall"!?
When you get to work on a large scene (not a mega huge one...I was on a sketchup!) and cant find a way to import in Octane
You can go for some serious questions about the soft usage.
It was a long time I didnt tested on Octane for one of my project and today conclusion is simple:
The import file format is crucial: obj is obsolete, you should go for xml or something that can deal with large scenes and advanced meshes properties... where is the interest having top soft functions and all sophisticated math calculations...if I cant get my model inside?
Just to insist there are priorities in the users demand and those ones (instances etc...) will make a big difference and let Octane go to another universe IMO:idea:
So I cross fingers