OctaneRender™ Standalone 1.36 RC1

[solomon]

so is motionblur support part of this release, like it was announced for the upcoming 1.5?

[emihich]

It is amazing, Alembic is very well inplemented.
And I am surprised How fast it is in comparison with 1.2 ( using GTX 780 ti)
Hope there will be support features for Alembic imported camera parameters ,
so the matchmoved cameras are consistent in FOV, resolution etc...
It seems right , but , I mean actually control it.

[merid888]

testing 1.36, directlight ambient oclussion, 1000 maxsamples, time 47 seconds,rendering with 1 gtx690

[foxid]

No displacemant, No 400% improvement...disapointed. Its very sad. Should stay on corona render or vray till 1.50++.

[Elvissuperstar007]

bug

[glimpse]

Thanks Guys!

[tglaja]

Thank you Octane Team.

[gabrielefx]

thank you,
I would like to know if all this stuff will be implemented in the Max plugin.

You fixed the ies issue? having only 5 photometric emitters with GTX580s and 10 for The Titans is pure madness.

Imagine to render a large mall with more than 5 different ies....or a museum...

It's easy to implement Alembic, more mathematics for the displacement feature....

I think that Intel did a better job than Nvidia...

I don't see any improvements in any of the gpu based renderers.

I'm very disappointed.

regards.

[suvakas]

So for the most part the improvements for 1.5 are internal changes to node system, LUA support and alembic format?
I kind of understood, that the huge re-write was for the good cause to implement new renderer features?
Octane is at 1.5 and it's still not ready for proper VFX and composition. New features you've implemented don't work as expected. Matte material don't work with reflections, no render passes, turning on/off shadows is buggy, etc. It kind of seems that everything you do lately are cosmetic upgrades to standalone. You also seem to be very excited over your LUA implementation. I have an impression, that a lot of your development time goes into fooling around with LUA.
I haven't seen a useful update in a long time. Octane lacks of innovation. It's a bit like war here. I feel like fighting for every new feature and then when you implement it it's a hack that doesn't work properly. It seems like you are lost in your own development and don't have a clue why users would need this and that.
Now as a programmer, i understand, that coding alembic support was a huge amount of work. Probably an effort so big, that you feel it's a milestone and deserves a major Octane version uptade to 1.5. But please understand, that users do not feel that way. I'm a plugin user and alembic is kind of nice to have, but if that's all what we get after half a year of development time, then it is too small improvement. Users do not care if you tell them that hey, we organised our internal code. It's much nicer to program now.
Seeing how other renderers are throwing out one innovative feture after another I really feel that Octane is standing still. At the moment being fast is the only advantage of Octane. But what's the use of it when we can't use it in production? There are other biased GPU renderers coming to the market that promise to be even faster.

Max plugin is also not ready. A lot of improvements can be done there too. Like adding instancing support to particle flow, proxy meshes, bitmap reloading.. etc etc.. But again.. everything is standing still. Karba compiles the new Octane binaries and calls it a new version.

Anyway..the bottom line is.. please start to develop Octane in user oriented way.
I like Octane and I'd like to use it in the future too.

Thanks for reading..

Suv

[voon]

Well .. I guess a feature not very useful to me is a feature very useful to someone else. I also wish there was more about the actual rendering engine, and less for "surrounding" stuff liek the alembic files .. but that's just my personal needs.

What I'd really want are displacement etc ... really new features to render single images.