OTOY Forums

Andygraph3D wrote:If I make a panoramic render of a 3d room with a 3d guy in the middle with a light on the ceiling to some extent it illuminate the 3d guy in a certain way, that is, according to the size of the light.
If I re-use the same render as panoramic hdri, removing the room and illuminating only the 3d guy, octane will shed light on the ceiling of a larger size and not the exact size in proportion to the magnitude of the 3d guy.

An option to scale the size of the virtual sphere hdri would be very useful to simulate more correctly the hdri environment of small or relatively small.

2 option need:
infinity (like is today)
and size (with option size for little enviroment)

With the next release you will probably be able to fake it using the new texture projections (preferred) or by placing the HDRI onto a sphere and making the sphere invisible.

hm .. interesting

Sorry for my intromission,

But i didnt understand one thing, we will have a little update this month or only in 2014 something new to try? Really Really sorry for this but im eager to get this update. Thanks so much for excelent job in Octane!

anereton wrote:Sorry for my intromission,

But i didnt understand one thing, we will have a little update this month or only in 2014 something new to try? Really Really sorry for this but im eager to get this update. Thanks so much for excelent job in Octane!

The plan is to start the release candidate cycle leading up to a stable 1.5 this year. We still hope to get to a stable 1.5 release in 2013...

cheers,
Thomas

anereton wrote:Sorry for my intromission,

But i didnt understand one thing, we will have a little update this month or only in 2014 something new to try? Really Really sorry for this but im eager to get this update. Thanks so much for excelent job in Octane!

To add to Thomas' post: What you are seeing in the videos and screenshots is what we currently call version 1.21. It's the first version in the development cycle to stable 1.5. We were hoping to get it out this month (i.e. this week), but there are still quite a few issues to weed out so I'm not too sure if we get it done until this week. But if not this week then very likely next.

It would surprise me if we would get to a stable 1.5 this year, we are definitely aiming for early next year.

D'oh!... thankfully, only us yanks observe Thanksgiving... so you will be working Thursday!!.. and not shopping Friday! Chop-chop Octane Team... Chop-chop!

Speaking of which, this 4-day weekend would be an incredible window of opportunity for myself (and other Octane-using yanks) to test the shit out of Visibility...

Just a suggestion.

Regarding Python scripting binding, Coral-apps is a good example of how easy it is to do Python binding. Coral is an open source project licensed under BSD license (http://code.google.com/p/coral-repo/).

Since the code is in the middle of re-factoring and Octane is targeted towards production use in animation and effects industry (where Python is dominant), it makes sense if Python scripting binding is also considered.

Thanks.

Cheers,

Faizol wrote:Just a suggestion.

Regarding Python scripting binding, Coral-apps is a good example of how easy it is to do Python binding. Coral is an open source project licensed under BSD license (http://code.google.com/p/coral-repo/).

Since the code is in the middle of re-factoring and Octane is targeted towards production use in animation and effects industry (where Python is dominant), it makes sense if Python scripting binding is also considered.

Thanks.

Cheers,

Hi there,

There's a couple of reasons why we chose Lua over Python:
* Lua is way simpler than Python so I guess almost everyone will be able to do something usefull.
* Lua is specifically designed for embedding.
* Lua's footprint is way smaller the Python's
* Lua's not that obscure, heaps of apps use Lua as embedded scripting language.
* ...

Luckily the major refactoring is almost over and we sure ain't going to add more features now for 1.5.

I'm not saying that we never ever will support Python...

cheers,
Thomas

stratified wrote: Hi there,

There's a couple of reasons why we chose Lua over Python:
* Lua is way simpler than Python so I guess almost everyone will be able to do something usefull.
* Lua is specifically designed for embedding.
* Lua's footprint is way smaller the Python's
* Lua's not that obscure, heaps of apps use Lua as embedded scripting language.
* ...

Luckily the major refactoring is almost over and we sure ain't going to add more features now for 1.5.

I'm not saying that we never ever will support Python...

cheers,
Thomas

I'm not a fan of Python either compared to other scripting languages, but the availability of the tools/libraries used in the industry or streamlining a pipeline between the major apps and Octane (3D/compositing/data management/others) should be the priority. Especially when Octane is not a complete end to end tool, and has to work together with other software in a large and often complicated eco-system. As an example, take a hint from Autodesk when Python binding is done across their major applications. Those bindings were done after their managers discussed with their major clients aka "big studios" on streamlining the pipelines used by their customers.

Cheers,

abstrax wrote:

anereton wrote:Sorry for my intromission,

But i didnt understand one thing, we will have a little update this month or only in 2014 something new to try? Really Really sorry for this but im eager to get this update. Thanks so much for excelent job in Octane!

To add to Thomas' post: What you are seeing in the videos and screenshots is what we currently call version 1.21. It's the first version in the development cycle to stable 1.5. We were hoping to get it out this month (i.e. this week), but there are still quite a few issues to weed out so I'm not too sure if we get it done until this week. But if not this week then very likely next.

It would surprise me if we would get to a stable 1.5 this year, we are definitely aiming for early next year.

So any news about the 1.21? i want to use it in a new big presentation, and use the new tools in it.

Cheers