Which feature do you need the most?

[abstrax]

Guys, please don't forget that we very much need Gradients in SDK as well, so plugs can use them.

This should have been in the poll.. unless you were already planning on adding them very soon.

They are already accessible via the SDK 1.21.

[abstrax]

I wished Object Motion Blur was on the list

Karba did mention Motion Blur along with Displacement in the first post of this thread. I assume he meant Object Motion Blur as Camera Based MB will ship with Octane v1.5.

We are working on full motion blur, but there will be only camera motion blur in version 1.5. It's not the very last version of Octane

[gabrielefx]

hair+fur is a sort of instancing algorithm, I think that in Max is possible to interface Octane with the embedded plugin.
In Octane there aren't forces to bend hair: wind, gravity, attractors, collision detection, etc.

Nobody wants distributed or network render!...that's incredible...

The most beautiful feature that I found in several software was: relight. (maxwell, thea, fryrender, indigo).

Imagine to adjust all the lights tweaking some parameters after the render. We could balance with precision the illumination of the scene.
Yes, Octane is interactive, but sometime, when the render is finished, we say: If I changed the temperature of that light....

[mbetke]

I think most freelancer / students don't have multiple computers. Just one workstation and thats it. I also do renderings on three GPU sometimes and work with the fourth on another project. You are a rare user with your 8+ GPU setup.

Multilight is an awesome feature I really loved in Maxwell beside the lens stuff. But I need other features like mixed HDr/sun more in my kind of work.

[manalokos]

That is why we make this poll. We can see real situation.
Undo has only 5% probably because users mostly use plugins(not standalone) and they have undo in a host application.

Does that mean that all the work you've to refurbish the octane node tree will serve only 5% of the users?
It is too bad, I've got used into working with the standalone and I can say it is far better than any plugin,
the node tree as is in the v1.2 is just amazing, material editing in the standalone is also incredibly effective.
With the improvements set into the v1.5 octane tree, big complicated projects will get incredibly simple.

Regarding multilight, it is even better to do it by hand making single render for each light and mixing it all together, or at least groups of lights.

Regards
Filipe

[MOSFET]

Relevant to this discussion - Nextlimit has posted previews of new Maxwell 3 features which overlap this thread:

Volumetrics - http://www.maxwellrender.com/V3/feature/volumetrics

The new volumetric feature in Maxwell can work in several ways: as a constant density volumetric object - useful for large atmospheric haze effects or thick fog, it can work with particles files in several formats, including RealFlow .bin, and also with density fields/voxels directly from Maya or Houdini.

OpenSubDiv (Bolded text highlights a benefit to Octane's Clound rendering service) - http://www.maxwellrender.com/V3/feature/pixaropensubdiv

The new Subdivision feature allows you to subdivide low-polygon objects into smooth surfaces, by implementing Pixar OpenSubdiv. Because it's subdividing the geometry only at render time - your scene files take up far less space and can be transfered much faster around your network. OpenSubdiv is owned by Pixar. Copyright (C) Pixar. All rights reserved

Deep Compositing - http://www.maxwellrender.com/V3/feature/deepcompositing

Maxwell Render 3 can now render in 'deep image' format, which stores color as well as depth information per pixel, making it much easier to composite rendered objects together as well as eliminating troublesome edge artifacts. You can save the deep info in either .EXR or .DTEX formats, in rgba or alpha

Alembic - http://www.maxwellrender.com/V3/feature/alembic

The Alembic file format allows for very efficient storage of geometry and other scene data, which can now be referenced directly in Maxwell V3. Support for Alembic includes static and animated geometry as well as particles. It also works with the Exocortex CRATE suite of Alembic plugins.

Multilight - http://www.maxwellrender.com/V3/feature/fastml

See your Multilight changes instantly in the main render view. Even Scattering and Dispersion update instantly - thanks to the new GPU accelerated Fast Multilight display!

Blockable Emitters - http://www.maxwellrender.com/V3/feature ... leemitters

Now you can isolate the contribution of each emitter to each individual object in the scene, allowing you to have objects not affected by certain emitters in the scene. This way, you have custom control over the lighting of each object in your scene.

[TBFX]

hair+fur is a sort of instancing algorithm, I think that in Max is possible to interface Octane with the embedded plugin.
In Octane there aren't forces to bend hair: wind, gravity, attractors, collision detection, etc.

I don't think it's about having a dynamic hair and fur system in Octane, it's about being able to render hair primitives, in a memory and geometrically efficient way, that are generated in animation software and exported through alembic, of course it would be even better to have a render time hair generation system that would take dynamic guides from the host application and populate on the fly but lets see what is possible.

Octane is a Renderer and as such should eventually be able to render anything you can generate using the tools available in your 3d software, with or without a plugin.

Nobody wants distributed or network render!...that's incredible...

Yeah that's a bit strange but I guess like me (I also did not vote for this) it's possibly that only people who do a lot of animation see this as important and they probably use a plugin version rather than the standalone and so already have network rendering capability.

T.

[Elvissuperstar007]

Nvidia CUDA Hair demo http://www.youtube.com/watch?v=53Z3VHGQjE8

[j7th]

http://www.geforce.com/games-applicatio ... -hair-demo
https://developer.nvidia.com/sites/defa ... ePaper.pdf

[Seekerfinder]

Karba,
May I suggest giving this post a bit of exposure of the (Release Candidate - EDIT:) General Discussion forum? It seems as though it has reached critical mass now and quite a small proportion of the user base has voted it seems. Perhaps make it a news item on the home page? Even send an email to all users? I think it is critical to get more people involved, not just those who happen to snoop into this forum. Whatever the team will do with the info received will be up to Otoy of course but at least lets get a bigger representation.

Also, I think the plugins vs standalone could complicate things. For instance, I am amazed that so few have voted for internal texture mapping. It's critical for an efficient workflow. But that's probably because most host applications would have efficient texture mapping. But some don't... I, for one still find Standalone a very useful application at times and would love to see this feature there. Perhaps it's only Standalone users like me who also asked for internal TM. There seems to be some sense in splitting the pole in Standalone and Plugins sections. Just a thought...

As a final note, your asking the feature priority question goes a long way in terms of restoring some faith in Otoy's commitment to its users (me included). I really hope you guys will use it (except for internal textures - put that on top of the list...).

Seeker