OctaneRender™ for Blender 2.06 - 6.6 Linux [OBSOLETE]

[JimStar]

The 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).


FIXES AND NEW FEATURES SINCE LAST RELEASE

• Internal motion blur is implemented. Subframe motion blur feature is not removed: now you can choose between "Internal" (faster) and "Subframe" (more universal).
• Fixed bug: grainy image in frames without any changes if subframe motion blur was used (reported by aLeXXtoR).
• Minor fixes...

Installation:
- Just run the installer to see its command line keys.
- If you need to run the OctaneServer - run it as daemon:

Code: Select all

# OctaneServer &

DOWNLOAD

Blender Octane Edition - v6.6 Linux (99.1MB autoinstaller file)

[grimm]

Thanks Jimstar, but no support for the 900 series cards? Maybe next time?

[grimm]

Hmm, something is wrong with this version. I set up a simple rigid body simulation and when I try to render it, the image comes out completely black. This isn't because of the autofocus, it's on. I can see the render if I turn on the renderer in the view port, but only if I'm not looking through the camera. I was testing the motion blur but it doesn't appear to be the problem, it renders black with it on or off. When you try to render through the camera either in the viewport or with the render/animation buttons it renders black.

Very strange, I did some more testing. I reset Blender with new to the default cube scene. It renders fine, so I set up a very simple animation with the cube. I set a two location key frames, one at frame 1 and the other at frame 100. This causes the cube to move smoothly between the two key frames. I set the viewport to rendered and scrubbed through the animation. At about frame 35 or so the viewport went black. So I went back to frame one and it started rendering again. I can do a f12 render on the frames before 35 or so, but the frames after only render black.

Jason

[JimStar]

"Autofocus" is not the panacea against not having meaningful focus distance value. E.g. if your autofocus point looks into the infinity instead of some object.
Choose the exact object in this case as the focus or enter the explicit focus distance value.

[kaiwas]

Thanks for the update!
And also thank you for the visit to http: // b3d....
Your fix helped us a lot.

[grimm]

"Autofocus" is not the panacea against not having meaningful focus distance value. E.g. if your autofocus point looks into the infinity instead of some object.
Choose the exact object in this case as the focus or enter the explicit focus distance value.

*sigh* Me being dumb again. Thanks Jim. Now that that is solved I'm still having a problem with the motion blur. Subframe works, internal does not:

Here is one of the images from the animation with subframe motion blur turned on:

And here is the same frame with internal motion blur turned on:

Both are using the same parameters. Am I missing something again? Well they should be the same frame. Part of the problem? Thanks,

Jason

[JimStar]

grimm
Only "movable" types will be motion-blurred on the rendered image.

[grimm]

That worked, thanks Jim. Now I will go crawl back into my hole.

[grimm]

If anyone is interested here is the finished animation, works great (if you know what your doing).

[mib2berlin]

Hi, got Blender 2.06 to work with another symlink to libffi on Opensuse 13.2.
@JimStar, hi, could you please update the source on git?

Thanks for the update, mib