OTOY Forums

Hi all,
I have decided to open a topic to avoid repeated wishes and give you a clue about roadmap of plugin.
I'll put planned or required/wished features to this list. I'll give some priority for each entry.
Most wanted or most important entries will have more priority. Please feel free your self to wish unlisted features.
Most possible and essential wishes can found a place in list.
Best regards

My todo list:


changes since Beta 0.3.4
-----------------------------------------
- search unfound texture in project path, tex path
- mat type changed to specular, transmission/relection set to 1.0, roughness set 0.0
- Save project with assets command implementation (works with imageTexture)
- bitmap sequence support started
- material picker(testing, developping)
- import livedb materials (started in first phase)
- Live View render statistics (1. general 2. textures 3.empty)


Next releases
----------------------------
Macos version
render output for info channnels
Compositing support(background/render/info channels)
Object tag (Static/dynamic objects)
undo implementation for sliders
remove unused materials
motion blur
Render selected objects
data/material exchange with standalone
New Octane ShaderLink Gui (similar to standalone)
Node editor implementing or new editor
Geometry update improvements

Having used the C4D plugin for a couple of weeks my immediate needs are:

1) Material previews! I can't properly organise a library of new Octane mats without it.

2) Support for the C4D Region-Render (would save lots of time being able to correct or tweak a small region of the render only)!

Loving the development so far. Thanks again.

Jaybee wrote:Having used the C4D plugin for a couple of weeks my immediate needs are:

1) Material previews! I can't properly organise a library of new Octane mats without it.

2) Support for the C4D Region-Render (would save lots of time being able to correct or tweak a small region of the render only)!

Loving the development so far. Thanks again.

Material previews for Content Browser?

Great initiative, I only have one wish : OCM importer !

Good luck for the future, Aoktar, you really do an amazing work !

César wrote:Great initiative, I only have one wish : OCM importer !

Good luck for the future, Aoktar, you really do an amazing work !

Thanks César, also your plugin is great.

OCM importer: actually has this command but there is a problem to work

This is new tested feature:
A screen shot about converting unsupported textures as a image (on the fly)

aoktar wrote:

César wrote:Great initiative, I only have one wish : OCM importer !

Good luck for the future, Aoktar, you really do an amazing work !

Thanks César, also your plugin is great.

OCM importer: actually has this command but there is a problem to work

This is new tested feature:
A screen shot about converting unsupported textures as a image (on the fly)

Does this mean it will also support the color correction filter?

nehale wrote:

aoktar wrote:

César wrote:Great initiative, I only have one wish : OCM importer !

Good luck for the future, Aoktar, you really do an amazing work !

Thanks César, also your plugin is great.

OCM importer: actually has this command but there is a problem to work

This is new tested feature:
A screen shot about converting unsupported textures as a image (on the fly)

Does this mean it will also support the color correction filter?

does not support runtime calculations. Will do bake most textures which has uv mapping. Also layered texture results. Color correction is not a matter. If you put a non-octane texture, this will convert with all sub nodes. But there are some minus about this option.
You must use only standart nodes in a chain.
More export time to generate textures, not very detailed as runtime calculation of native octane textures.
Limited with memory and texture numbers.
User can't use more than allowed texture numbers.

Is having an include/exclude option too far fetched for the octane light tag or environment?, i know this is a more biased renderer feature

nehale wrote:Is having an include/exclude option too far fetched for the octane light tag or environment?, i know this is a more biased renderer feature

it depends to SDK capability. I cannot found a way for that. If Octane Team put similar features then The Engine will be unbeatable.

Hi Aoktar,

My requests for now are:

- Material Picker
- RGB sliders for the white balance, without clicking color field first (like in Standalone)
- Full export (with models, materials) with OCS for opening in Standalone