OTOY Forums

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


This is the quick-fix release

FIXES AND NEW FEATURES SINCE LAST RELEASE

• One crash bug catched.

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.5 beta (2.70) (58.9MB autoinstaller file)
Octane Server - 1.52 - 4.5 beta (7.8MB autoinstaller file)

Still have the same effects of sorts::

- One render (extensive water caustics) went up to 495/500 samples and then just sat there, never stopping, hogging the GPUs
- Another finished, but never fully released the GPUs (they went down from their maximal 1150 to 890, but never back down)

If you want, I can again log the clock and provide the blend files etc?

System: Windows 8.1 update 1 x64, two 780ti GPUs and the latest Nvidia driver (337.50 Beta).

voon wrote:Still have the same effects of sorts::

- One render (extensive water caustics) went up to 495/500 samples and then just sat there, never stopping, hogging the GPUs
- Another finished, but never fully released the GPUs (they went down from their maximal 1150 to 890, but never back down)

If you want, I can again log the clock and provide the blend files etc?

System: Windows 8.1 update 1 x64, two 780ti GPUs and the latest Nvidia driver (337.50 Beta).

This quick-fix has fixed another bug - the server crashes during the render.
As I remember - we had the bug which you describe here some versions ago, and it was the bug inside Octane PMC kernel which later was fixed in next SDK version. So, if you started to get the same issue in this version - I should check, perhaps something was broken again inside the engine... Or something may be broken in the plugin itself...
So, can you give me the scene where it is reproducible?

It was PMC, yes .. have to send you the files when I get home in the evening.

Sorry... Whatever I do : enable Render in viewport, hit render or animation button, with or without alembic box enabled... I still get immediate crash of the server with message in the console :

Octane : ERROR activate render-server.
octane : Network send error
Octane : Error resetting render server.

I typed again my logins in case it was necessary ... same result.

I deinstalled Blender for Octane and the server one more time. I rebooted the computer to avoid any possible residue in memory.

I installed again, without adding my personnal config folder to avoid any possible conflict with parameters entered by previous releases , Official and Octane. I haven't added any addon.
Typed again my logins and passwords...

As it is, this release still leads to immediate crash... With default scene. No need to load a personnal file. It crashes with default scene with just a cube and a camera.

I am using the most recent Nvidia driver : 335.23. it is compatible with both my GTX 260 display card (compute model 1.3 not used for rendering) and my GTX 380 3GB (Compute model 2.0) used for rendering. In Standalone preferences, this driver is displayed as Cuda 6.00. Is it convenient for this release ?

Signature du problème :
Nom d’événement de problème: BEX64
Nom de l’application: OctaneServer.exe
Version de l’application: 0.0.0.0
Horodatage de l’application: 534e0b33
Nom du module par défaut: StackHash_1dc2
Version du module par défaut: 0.0.0.0
Horodateur du module par défaut: 00000000
Décalage de l’exception: 0000000000000000
Code de l’exception: c0000005
Données d’exception: 0000000000000008
Version du système: 6.1.7601.2.1.0.256.48
Identificateur de paramètres régionaux: 1036
Information supplémentaire n° 1: 1dc2
Information supplémentaire n° 2: 1dc22fb1de37d348f27e54dbb5278e7d
Information supplémentaire n° 3: eae3
Information supplémentaire n° 4: eae36a4b5ffb27c9d33117f4125a75c2

OK new things: I had blender and the server deinstalled and your new versions installed. But it seems the deinstall does not properly deinstall when you have added another addon or so? In the newly installed blender it said 1.52 4.4 in the octane addon instead of 1.52 4.5. I'm not sure why.

Thhen I went to the roaming profiles and deleted the blender directory there as well and reinstalled again. This time it did say 1.52 4.5.

This seems to have cured my problem where it does 495 of 500 samples. The other problem remains:

In IdleWhile it is rendering, my GPUs sit at 324 MHz. When I render, both jump to approx 1120 MHz. When they finish rendering, they go back to 980 MHz and stay there .. they don't fall back to 324 MHz. This only happens, if I stop octane server, then I'm back at 324 MHz.

I attached one of the blend files this happens with (but it also happens with others).

ROUBAL
I see the activation error as the first error in log. Have you activated the plugin and standalone?

Is the network present when you enter the login/pass?..
It seems you are only one who has this problem, so we need to narrow down this... I've just stopped the animation render which worked all night on my work-computer on this last version - no problems at all...

I see the activation error as the first error in log. Have you activated the plugin and standalone?

Yes, both Login and password for plugin and standalone are entered. They are present in the fields when I relaunch Blender.

Is the network present when you enter the login/pass?

Yes.

ROUBAL wrote:Yes, both Login and password for plugin and standalone are entered. They are present in the fields when I relaunch Blender.

They should be present in the fields before you start render. Is it the case?
If yes - check if the file ".octlic" is present in your user-folder (e.g. "C:\Users\<User name>\.octlic").

They should be present in the fields before you start render. Is it the case?

YES.

If yes - check if the file ".octlic" is present in your user-folder (e.g. "C:\Users\<User name>\.octlic").

YES, the .octlic file is present.

EDIT : After many attempts at random, I discovered one thing :

If I first Open Blender and launch the server, or If I launch the server and open Blender in a second time, the first attempt of rendering or exporting an alembic or opening the render preview gives a server crash each time.

I can do it again and again an always get a crash.

NOW, if I don't close Blender after a server crash and relaunch the Octane server, The server doesn't crash next time I hit render or animation or open the render viewport.

I have been able to launch several times the render of one image and of a serie of 10 frames as well as render preview and alembic on an animated cube on 10 frames.

I have to test on a real complex scene.