Manipulator Gizmo in 3.x?

A forum where development builds are posted for testing by the community.
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
Rikk The Gaijin
Licensed Customer
Posts: 1528
Joined: Tue Sep 20, 2011 2:28 pm
Location: Japan

Goldorak wrote:We tried to fit this in 3.0 with the amazing work Joan is doing using the script nodes (more on that in tomorrow's talk) but hit a few walls that need the native C API for plugins in 3.1.

It's a high priority for us. We'd like to see standalone use these tools to become a more powerful VR and scene composition system.
So we won't see it until 3.1? That's a bummer. :cry:
User avatar
Refracty
Licensed Customer
Posts: 1599
Joined: Wed Dec 01, 2010 6:42 pm
Location: 3D-Visualisierung Köln
Contact:

I would say from the 90% of users that does not touch standalone 50% don't touch it because of missing features like Gizmos and keyframe animation. In addition new users are won if you the standalone contains important features like Gizmos, Variants and Keyframes/Graph Editor.

When I have a Rhino Scene I can not bring it in to Maya because of Maya's missing ORBX import features.
So the only whay to save time is to export the scene form Rhino and the animated objects from Maya and merge it in the standalone version.


Goldorak wrote:
Syd_86 wrote:
Goldorak wrote:We tried to fit this in 3.0 with the amazing work Joan is doing using the script nodes (more on that in tomorrow's talk) but hit a few walls that need the native C API for plugins in 3.1.

It's a high priority for us. We'd like to see standalone use these tools to become a more powerful VR and scene composition system.
Have you ever used the standalone version of your software, I do not think.
I use it every day and I love the standalone tool and want it to grow more capable (I use MAX, but much happier doing scene editting in SE). But keep in mind that 90% of users do not touch SE at all, and do everything through the plug-ins.

It's taken some time, but we now have a small but growing team at OTOY dedicated to working on extensions to the SE for authoring and scene editing.

Part of this work is also preparing how SE will be implemented with OctaneEngine coming out the same time as 3.1 (which is also foundation for Octane 4 next year), since the new API is a network stream, not a library or binary.

To that end, we are 50% done rebuilding the entire SE UX in HTML5 which will connect to OctaneEngine and give you the same experience as the app today, but much more flexible. We are adding this in ORC web desktop to allow you edit an ocs in the browser without need to run all of Octane.
User avatar
Refracty
Licensed Customer
Posts: 1599
Joined: Wed Dec 01, 2010 6:42 pm
Location: 3D-Visualisierung Köln
Contact:

Well done Aoktar.

aoktar wrote:Here is my first manipulator implementation for AE plugin editor. It's very useful and effective.
download/file.php?id=51077&mode=view
User avatar
Syd_86
Licensed Customer
Posts: 120
Joined: Tue Oct 01, 2013 11:38 am

Goldorak wrote:
Syd_86 wrote:
Goldorak wrote:We tried to fit this in 3.0 with the amazing work Joan is doing using the script nodes (more on that in tomorrow's talk) but hit a few walls that need the native C API for plugins in 3.1.

It's a high priority for us. We'd like to see standalone use these tools to become a more powerful VR and scene composition system.
Have you ever used the standalone version of your software, I do not think.
I use it every day and I love the standalone tool and want it to grow more capable (I use MAX, but much happier doing scene editting in SE). But keep in mind that 90% of users do not touch SE at all, and do everything through the plug-ins.

It's taken some time, but we now have a small but growing team at OTOY dedicated to working on extensions to the SE for authoring and scene editing.

Part of this work is also preparing how SE will be implemented with OctaneEngine coming out the same time as 3.1 (which is also foundation for Octane 4 next year), since the new API is a network stream, not a library or binary.

To that end, we are 50% done rebuilding the entire SE UX in HTML5 which will connect to OctaneEngine and give you the same experience as the app today, but much more flexible. We are adding this in ORC web desktop to allow you edit an ocs in the browser without need to run all of Octane.
Hello, Goldorak
I do not write code, is difficult for me to understand the amount of work, so do not understand the difficulty in creating a Gizmo. But they are years that is written is a priority.
Typically the standalone version of a software has fewer problems and less shortcomings, you do the opposite, because you have more demand for plug-in. Rightly. We are really so few to have the standalone version? Then, make happy those 4 cats that have the standalone version. It seems you want to bring to closure the standalone version, few users so we can neglect it. Rightly priorities are important but we are talking about a basic function.
At this rate, when it comes out the version 3.1, 3.5 will be told we are at a good point, perhaps the 4. The version 4 will say can not do it....Am I wrong?
User avatar
Syd_86
Licensed Customer
Posts: 120
Joined: Tue Oct 01, 2013 11:38 am

At this point, what is the benefit of having Standalone version? I have to start evaluating...
What's the best combination between octane and software? Cinema4D with OR plugin?
User avatar
Syd_86
Licensed Customer
Posts: 120
Joined: Tue Oct 01, 2013 11:38 am

itsallgoode9 wrote:not having a gizmo is like trying to use a computer without a mouse, or drive a car without a steering wheel. I honestly can't believe that we are still talking about this.
I fully agree. Your answer is perfect in every point!! :o
User avatar
Syd_86
Licensed Customer
Posts: 120
Joined: Tue Oct 01, 2013 11:38 am

manalokos wrote:The Standalone is far more powerful!
It ables you to manage complex scenes, with infinite combinations.
Hello!
The Standalone is far more powerful?... Could you explain the advantage of the standalone version?
If so, already from version 2 it should be added to the gizmo.
The itsallgoode9 answer, this is the correct answer.
manalokos
Licensed Customer
Posts: 441
Joined: Fri Nov 18, 2011 4:43 pm

Syd_86 wrote:
manalokos wrote:The Standalone is far more powerful!
It ables you to manage complex scenes, with infinite combinations.
Hello!
The Standalone is far more powerful?... Could you explain the advantage of the standalone version?
If so, already from version 2 it should be added to the gizmo.
The itsallgoode9 answer, this is the correct answer.
Try working in a big team with a big project, 30 cameras with different enviroments, many people modelling, making scatter nodes, etc...
You can only do it in standalone !
User avatar
glimpse
Licensed Customer
Posts: 3740
Joined: Wed Jan 26, 2011 2:17 pm
Contact:

Standalone is usefull & very powerful tool..but a lot of Guys do not even touch.. & it will remain so untill friendlyness is going to change..Gizmos & small thigns like that are important & if OTOY wish to have more feedback or more of the comunity to use leverage it we do need those little changes. However I do understand priorities & seems other things do overshadow those little things..at least now =) maybe, one day..
User avatar
Syd_86
Licensed Customer
Posts: 120
Joined: Tue Oct 01, 2013 11:38 am

glimpse wrote:Standalone is usefull & very powerful tool..but a lot of Guys do not even touch.. & it will remain so untill friendlyness is going to change..Gizmos & small thigns like that are important & if OTOY wish to have more feedback or more of the comunity to use leverage it we do need those little changes. However I do understand priorities & seems other things do overshadow those little things..at least now =) maybe, one day..
Yes!......maybe, one day.. :?
Post Reply

Return to “Development Build Releases”