OctaneRender™ for Blender 1.52 - 4.7 beta Win [OBSOLETE]

[JimStar]

OctaneRender™ for Blender plugin. Windows x64 version.


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. To stop the server - just right-click its icon in the tray.
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

• Bug fixes.

After starting OctaneServer it will take some time before the LiveDB tree and LiveDB material previews will be available from Blender - as OctaneServer caches the LiveDB data from remote server right after starting. But only the materials groups tree will be re-cached every time after server start, LiveDB material preview images will be cached only once - so only the very first OctaneServer start will need some more time before LiveDB tree will be available in Blender.


DOWNLOAD (both distributives must be reinstalled, they depend on each other)

Blender Octane Edition - 1.52 - 4.7 beta (2.70) (58.9MB autoinstaller file)
Octane Server - 1.52 - 4.7 beta (7.8MB autoinstaller file)

[kavorka]

Hey Jimstar, what bug fixes are addressed in this patch?

[JimStar]

Hey Jimstar, what bug fixes are addressed in this patch?

Reported in previous version thread.
Post here please if you'll get some more..

[ROUBAL]

Hi Jim, Thanks for the new release.

Just to be sure, because it is not a problem as we have no reason to do that if the render works, but : If I type the logins/passwords in the fields and hit render after I already did a successful render, Blender for octane freezes like before, and I have to kill the server to be able to close Blender. I don't know if it is the expected behaviour. There is no error signaled in the console, and no log file generated.

An other question, as testing would require some preparation and an alembic export of 5 hours minimum and I have to sleep few hours as it is 04:30 here (since I changed my display GPU for a GTX 580, the heat in the case is higher and I have had to increase a lot the fans speed, and my machine is too noisy to let it run),

so Is this release supposed to fix the problem of alembic file not present in output folder and the node having no pins ?

If not your answer can save me at least 5 hours of useless export.

I will be able to test myself only tomorrow evening at best.

[JimStar]

Hi Jim, Thanks for the new release.

Just to be sure, because it is not a problem as we have no reason to do that if the render works, but : If I type the logins/passwords in the fields and hit render after I already did a successful render, Blender for octane freezes like before, and I have to kill the server to be able to close Blender. I don't know if it is the expected behaviour. There is no error signaled in the console, and no log file generated.

This is normal:

After starting OctaneServer it will take some time before the LiveDB tree and LiveDB material previews will be available from Blender - as OctaneServer caches the LiveDB data from remote server right after starting. But only the materials groups tree will be re-cached every time after server start, LiveDB material preview images will be cached only once - so only the very first OctaneServer start will need some more time before LiveDB tree will be available in Blender.

Every time you reactivate already activated plugin using login/pass pair - it starts to refresh the entire LiveDB cashe again.

An other question, as testing would require some preparation and an alembic export of 5 hours minimum and I have to sleep few hours as it is 04:30 here (since I changed my display GPU for a GTX 580, the heat in the case is higher and I have had to increase a lot the fans speed, and my machine is too noisy to let it run),

so Is this release supposed to fix the problem of alembic file not present in output folder and the node having no pins ?

I have improved this part, so you can check if your issue is gone... Now you at least should have some additional error messages in console if something goes wrong.

[ROUBAL]

Well, before going to bed, I launched two exports of 5 frames of my animated tree.
They were both successful and generated an usable alembic file in the Output folder.

Then I launched an export of 990 frames. It required less time than my complex car animation, and after I slept 1 hour, it is finished :

There is no alembic file in the output folder.
The file in the user\...\livedb\alembic folder gives a node with NO PINs at all.

There is no log file generated.

Blender console says Wrong alembic file, size : 0 bytes, but the invalid alembic file weights 5.122 GB !

Sorry : nothing fixed.

I switch off the machine... back to bed.

[JimStar]

ROUBAL
Can you give me the scene where I can reproduce it?

[Marten74]

Hello!

For the first time since I started to use the plugin I can´t get the installation to work... In the system console I get "Octane: network send error". I have granted access through the firewall. Any ideas? I´m, running the latest build with Blender 1.69 without a problem (thankfully).

Cheers

::mb

[bluerocket]

Thanks Jim!

Regards

[resmas]

Thanks Jim for the hard work.

SOLVED now

Just one question, when i export a camera animation, i set Animation Mode to "Camera Only", and i check the box "export alembic". The alembic file ok, but is created with geometry.

When i open it in OctaneStandalone it has all geometry pins - so i go to alembic file option and uncheck "load geometry" to have a camera animation alembic file.

Camera animations exported to alembic, from Maya have around 150kb. The alembic file exported from blender has 100mb, because it has geometry when I only want the camera parameters.

While blender is exporting the animated camera I can see that its reading/exporting geometry when I set to "Camera Only" and for 500frames it takes about 5 minuts, in Maya it take 5 secunds (no geometry export)

I'm I doing something wrong in the export process?

EDIT: Moving the camera to a separated and empty layer is the trick. - thanks Kavorka

cheers
resmas