Octane standalone is dead?

[stratified]

Nope, we aren't going to maintain this script. We maintain the blender plugin.

We're willing to provide some guidance on what will and will not work.

cheers,
Thomas

[pixelrush]

Right so don't tell us our 'unofficial' script needs to die in favour of the 'official' script Refractive/Otoy provided but don't/won't maintain and is obsolete Eventually blenderheads will decide what to do here, don't worry.

[steveps3]

So the options are use the unofficial script or use another unofficial script. Not much of a choice.

[ephdot]

Nope, we aren't going to maintain this script. We maintain the blender plugin.

We're willing to provide some guidance on what will and will not work.

cheers,
Thomas

To that end, I was thinking that the plug-in should have this as an option. For the times where we would like to work in the standalone version, it would be nice to have a button labeled as Export (within Blender) that sends a command to the Octane Server to write the currently loaded scene to an OCS file. I would think that would be fairly simple to implement.

[pixelrush]

OK so in respect of Blender-Octane scripts Otoy have inherited Refractive's own 2.49 script deemed the 'official' one although plainly others could have been produced by other parties. This script was intended to conform to a 'spec' as to appearance and features etc. This is now obsolete/redundant/broken for later Blender releases. Most probably it can be deemed legacy or dead. In respect of Blender 2.5+2.6x Otoy do not have a script of their own for their customers. The Blender community have provided one for themselves thanks to the benevolence of Lionel with some follow up tweaks by others. This script exists for what it is, as it is. That is, what it does, how it does it, and how it displays in Blender is not Otoys concern, responsibility or jurisdiction. It is a Blender users initiative to make use of Octane Standalone inside Blender rather than load meshes from inside Octane. If it has reverse engineered .ocs support because Blender users asked for it or the coder thought to include it that's incidental. If someone made it to play Yankee Doodle Dandy at the same time that's the way it is. If Otoy want an 'official' script for 2.5x-2.6x conforming to their ideas they will need to produce their own and maintain it. As it is they have indicated they only want to support their pay-for plugin.
In respect of the current state of fitness of the community script then, given that Lionel is no longer around, and we dont appear to have any strong coders in our midst, we have a few choices.
I'll get to those in another post after I have had dinner...

[mib2berlin]

Hi all, as Blender Octane addon user I use the script not often.
It is may possible to get help or payed help in the Python area of Blender Artists.
There is also a "Payed Work" thread where experienced coder help for money.

http://www.blenderartists.org/forum/for ... -Paid-Work

Latest work was the FBX exporter developed from the Blender developer Champbell Barton.

Python support thread:

http://www.blenderartists.org/forum/for ... on-Support

There is also the Blender Network where you can hire freelancers for script development.
I think it is not a big thing for a python developer who knows Blender well to get the addon up to date for a few $.

http://www.blendernetwork.org/

Cheers, mib.

[steveps3]

I've posted a thread. You never know we may find someone who is kind enough to do the work.

http://www.blenderartists.org/forum/sho ... ost2553709

[enricocerica]

Hi Stevep3, what are you rewriting exactely, if you just need an export script generating the obj file with the materials and starting octane standalone, Lionel script does the trick
Anyway to avoid a plenty of scripts I would suggest the extention of the Lionel's script instead of creating a new one.

[steveps3]

Well I have done a bit of tidying up. I am starting to get the hang of things a bit more now. You never know, at this rate I might make a python coder.

Anyway I have attached a new version. I've removed some more code and cleaned up the code that I removed yesterday. I have also tidied up the UI a bit. I've discovered that the latest versions of Octane do not support the -n command line flag. So there is no way, at the moment, for me to write a .OCS file. I could go back to Lionel's method and write a very basic header file. If this proves to be the only way of doing it then this is what I'll do. Hopefully someone at Otoy can come up with a better solution.

I've called this version 2 just to ensure that it doesn't get confused with any previous exporter scripts.

Let me know if you want anything tweaking. I think that I should be able to manage a few simple changes.

octanerender 2_00.zip

(61.87 KiB) Downloaded 194 times

[steveps3]

Hi Stevep3, what are you rewriting exactely, if you just need an export script generating the obj file with the materials and starting octane standalone, Lionel script does the trick
Anyway to avoid a plenty of scripts I would suggest the extention of the Lionel's script instead of creating a new one.

Unfortunately Lionel's script tried to be too clever. It tried to write the materials to the .OCS file. This is the bit that is broken. The new script doesn't touch the .OCS at all so it should remain Octane friendly.