Thanks again
Here is the video:
http://vimeo.com/11380551
Now i will cleanup the code and compile for x86 and x64...
mlody47 wrote:WOOOOHOOOO instaling right now
Yes, i know.[gk] wrote:you should contact radiance and get info on how to layout a predefined User interface. If you do so and the script can do -exactly - what they want it to do ( not what you think would be nice ) there is a good chance it will be a part of the software package at one level or another.
viewtopic.php?f=21&t=1455
[gk] wrote:You can do all those things in 3dsmax via scripting, im pritty sure you can in your host as well.
You need to read the plugin guide line which explains the workflow.
Build your tool around the flow.
You dont need to have a a clean "octane" scene to do this, you can write your code so it takes care of everything automaticly.
The reason why all plugins should have consistency from start off is that its way easier to support.
Letssay you write your tool and its completly different than any o the others, it will be more difficult do act on support.
If all plugins has same buttons same places, doing the same thing, it doesnt matter which host app are beeing used.
Also, documentation is ALOT easier to come by.
+ it will feel more proffesional that the UI and functions are the same cross host apps
You cna write your tool in any way you want, but eventually the uniform one will have to be made, so why not do it from start off?
face wrote:[gk] wrote:You can do all those things in 3dsmax via scripting, im pritty sure you can in your host as well.
You need to read the plugin guide line which explains the workflow.
Build your tool around the flow.
You dont need to have a a clean "octane" scene to do this, you can write your code so it takes care of everything automaticly.
The reason why all plugins should have consistency from start off is that its way easier to support.
Letssay you write your tool and its completly different than any o the others, it will be more difficult do act on support.
If all plugins has same buttons same places, doing the same thing, it doesnt matter which host app are beeing used.
Also, documentation is ALOT easier to come by.
+ it will feel more proffesional that the UI and functions are the same cross host apps
You cna write your tool in any way you want, but eventually the uniform one will have to be made, so why not do it from start off?
I know that i can do that with scripting, but it´s not clear for me, how i can set the objects, which i will export, with a single click on a checkbox.
I don´t know how the export in Max works.
When you enable a checkbox and then click on export, then you have the chance to pick the objects, lights, camera which you will export?
The same with some values, eg focaldepth. After i click on export, i can type in the value?
I find it easier to select things i want to export, before i export. And in Softimage, i have the chance to do that only one time.
After i have selected the objects, i can change anything in the scene and can then simple hit the render button. I must spend no more time again with selecting.
The only thing which is easier, is that i must spend no time to write a documentation.
But, a good plugin in Softimage, has it´s own helpfile, which will displayed, when i click the "?"
When are changes in Octane i must change my sourcecode. Whether the UI is identical or not.
I think, why should i don´t use the features i have? I can eg keying every value i make in the UI, rightclick on them and let me show the interpolation curves.
What is, when users want to animate the samples? For that i must change only one parameter. Should i don´t use it, because the guidlines that don´t allow?
Face
Return to Resources and Sharing
Users browsing this forum: No registered users and 52 guests