Bretchts New Blender Render Design

[dave62]

..integrating octane into 3d app wo export:
i thought octane renders that fast because of the voxelization!? the voxelization tooks time and needs to be updated each time the mesh changes.
if the voxelization could be multithreaded, it would be a big export speed up.
Anybody know, does cycles, use any voxelization too?

i think rs should focus on the algorithms first to realize a fast unbiased renderer (of course keep future possibillities in mind) and then later focus on direct integration. everything else makes no sense imo

cheers,

dave

[Elvissuperstar007]

Octane is the best! Cycles do not like(

[Scooby3]

Indigo 3?

[face]

Indigo 3?

Speed?
In the preview video you can see, that network rendering is used, with how many computers?

Price?
Nearly 6x Octane...

face

[bepeg4d]

from Indigo news:

Indigo Renderer 3.0 introduces several next-generation features such as interactive scene editing and camera controls, all powered by a supercharged rendering engine which now supports GPU acceleration for both CUDA and OpenCL

ciao beppe

[pixie]

Indigo 3?

Speed?
In the preview video you can see, that network rendering is used, with how many computers?

Price?
Nearly 6x Octane...

face

Don't forget that you get what you pay...

[JoryRFerrell]

No matter the similarities, I for one will continue using Octane. For one, after viewing a few videos, I'm fairly certain he attempted to steal as much of the idea as possible.
As such I will stick to brand loyalty here, and continue support for RS. And second, you guys are already ahead on the learning curve anyways. As stated in an earlier post, you have the drop on how to go about coding new and better features as you are much more familiar with the mechanics than Brecht. Just work to outstrip him.

[SamCameron]

JoryRFerrell, Bretch is not alone, actually patches has been provided from various users, not so many actually, but cycles is at the first stages, what you can consider for certain is than in the next months cycles is going to receive a big push forward from the entire Blender community developers, they are going to bring many things to the core, new tools, new tweaks, patches, and so on... and the Blender community is FAR bigger than the Octane developers which I think they're about 5 or 6 devs if I'm not wrong. The truth is Refractive Software cannot fight against an entire open source community as big as blender has, time to time... you guys will see.

[arexma]

JoryRFerrell, Bretch is not alone, actually patches has been provided from various users, not so many actually, but cycles is at the first stages, what you can consider for certain is than in the next months cycles is going to receive a big push forward from the entire Blender community developers, they are going to bring many things to the core, new tools, new tweaks, patches, and so on... and the Blender community is FAR bigger than the Octane developers which I think they're about 5 or 6 devs if I'm not wrong. The truth is Refractive Software cannot fight against an entire open source community as big as blender has, time to time... you guys will see.

Size´s not everything.
Coding a raytracer is non trivial, coding optimized for parallelism and multithreading is neither. I doubt those contributers have the skill to advance Cycles significant. If there where that many good raytracing coders, the Renderbranch wouldn´t have "died off" after Sintel.
And you have to keep in mind that RS works to deliver a Product with a feature list to customers, with employees, hired for those particular tasks with the given skills, whereas the contributing Blender developers develop features as they have interest in them. Look at Luxray, its a big community dedicated only to a raytracer, they have steady progress, but it´s slow.
Many features in Blender are still buggy, missing or badly implemented, simply because those things are either boring, require a high skill in mathematics and algorithmic or because the actual developer lost interest in it.
Don´t get me wrong, Blender is doing great, love it, using it, but it has it´s downsides, especially in it´s development.

--

As for tight integration, Cycles was planned as 3rd party renderer as said by Brecht. The tight integration simply comes because Brecht modified Blenders render API to integrate Cycles.
Every tool, Maya, 3dsmax, Sketchup, XYZ123 simply has to look into cycles source, enhance their source by an API which connects to cycles and the tight integration "is done" and if it´s not fitting perfectly, adapt cycles. With a good API you can keep your tool closed source and just offer a modified cycles including source without any GPL violations.
As a matter of fact I don´t even want to know how many companies already checked cycles source out and are hacking on it right now.

[kivig]

On all those tight integrations:

I wonder if RS would be interested to get Octane integrated into for instance Autodesk products as MentalRay have. I'm sure Mental doesn't loose money there. And there is a solid support for it from app side.