OTOY Forums

The TEST Linux version of OctaneRender™ for Blender plugin, 64-bit.




The bundle consists from two parts:
1. OctaneRender™ Server
2. Blender - OctaneRender™ edition.

The first part (server) should be run on the same computer as the second one..
After the server is run - you can start rendering (or open a rendered view) from inside Blender. Before the very first rendering you should fill in the server address (only 127.0.0.1 at the time), login and password (your license key info) to activate the server. After the first rendering the server will remember this activation info, and you will not need to enter it again.

You should use only OctaneRender materials inside Blender scenes - the plugin knows nothing about Blender specific materials and textures (about any Blender nodes, generally speaking).


Installation:
- Just copy the files from archive to root file system (into the same folder-tree as in archive).
- Run the OctaneServer as daemon: - Now you can start blender.
- If you got error messages that blender needs some libBlahBlah.so library - you can run the install_deps.sh script from installed blender folder with appropriate command-line keys. It will download, compile and install all needed libraries. If you dont want to install only the needed libraries - you can install all possible using --with-all key (but be ready it may take a lot of time to download, compile and install them all).


DOWNLOAD
Blender Octane Edition - v1.4 beta Linux (91.8MB archive file)

Work )
thank!

Is there a way to turn the texture? Nod rotation seems not to work

OctaneServer breaks when setting the light source.

"ERROR: Program executed illegal instruction.. terminating"

Just purchased my copy of the plugin. It's working great so far, so much nicer than working with standalone. The only thing I had to do is add "/usr/lib" to the LD_LIBRARY_PATH in my .bashrc file. Once I restarted the terminal, octane server started right up. Thanks,

Octane_Server keeps crashing on me if I leave the render paused for a time. I then have to kill the server and restart it. This is the only error message:
I'm pretty sure that I saw this happen when I was using standalone too. In that case Octane would just die and I didn't have to kill it.

I'm getting lots of these:
Not sure what triggers it

EDIT:
Also, tweaking light emitters parameters crashes Blender all the time.

matej wrote:I'm getting lots of these:

Code: Select all

Traceback (most recent call last):
  File "/mnt/devel/prog/blender-octane/2.68/scripts/addons/octanerender/ui_material.py", line 78, in draw
    row.template_list(ob, "material_slots", ob, "active_material_index", rows=2)
TypeError: UILayout.template_list(): error with argument 1, "listtype_name" -  Function.listtype_name expected a string type, not Object
location: <unknown location>:-1

Not sure what triggers it

It is not integrated plugin's errors. It seems that you have mixed it with exporter or some other scripts - "octanerender" folder and "ui_material.py" are not this plugin's things...

JimStar wrote: It is not integrated plugin's errors. It seems that you have mixed it with exporter or some other scripts - "octanerender" folder and "ui_material.py" are not this plugin's things...

Yeah, octanerender is the folder of the unofficial exporter. My bad, sorry.

I'm having a problem with the absorption medium with specular material in Blender for Octane. It works in standalone but no matter what I do in Blender I can't get it to work. Basically I lose transparency when I hook up the absorption medium and it makes the object completely opaque.

Here is what it looks like in standalone:
And this is how it looks in Blender for Octane:
P.S. absorption is misspelled on the node.

I'm still having problems with Octane_Server crashing on me. It's not the cards overheating as I have been monitoring their temps, they never get above 61C. I have also put an additional fan in my box to help with the temps.

If I leave the server running (Blender is not running) it will crash with the same error as before. It's still running though and the CPU usage goes up to 200%, basically two cores are getting hammered and I have to kill it. I'm not sure exactly how long it takes to crash, but I'm guessing at least a half hour or thereabouts. I will keep track of the memory used in case it is a memory leak.

Well it doesn't look like a memory leak, my memory stayed steady at 3.0 GBytes used out of 8 GBytes.