OctaneRender™ 2.2 for LightWave™ - Daily builds

Sun Oct 04, 2015 9:21 am

there is no 32 bit version of the plugin in daily build right....

Sun Oct 04, 2015 11:49 am

Yes, I should put a note in the release notes. We are going to drop the 32 bits builds from this release. Octane 3 is not going to have 32 bits version due to the new architecture, that can need easily more than 4 GB of CPU RAM to store all the buffers data, and at this point we are going to work also only with x64 versions in these last 2.2 plugin releases.

-Juanjo

Thu Oct 08, 2015 5:28 pm

juanjgon wrote:Yes, I should put a note in the release notes. We are going to drop the 32 bits builds from this release. Octane 3 is not going to have 32 bits version due to the new architecture, that can need easily more than 4 GB of CPU RAM to store all the buffers data, and at this point we are going to work also only with x64 versions in these last 2.2 plugin releases.

-Juanjo

YES!
forward ever.
backward never!

snip lwguru

Tue Oct 13, 2015 9:24 pm

How come that memory use/free never amounts to 6GB even if I am using a dedicated display card ?

Tue Oct 13, 2015 9:45 pm

BorisGoreta wrote:How come that memory use/free never amounts to 6GB even if I am using a dedicated display card ?

I think that some of the memory used in the GPUs by Octane (the Octane program itself and perhaps some internal rendering data) is not taken in account for the statistics, but I am not sure. Are you losing a lot of memory?

-Juanjo

Tue Oct 13, 2015 9:51 pm

Use/Free 4452/245
rendering at 3500x1969
is the render buffer included in the Use number ?

Tue Oct 13, 2015 9:59 pm

BorisGoreta wrote:Use/Free 4452/245
rendering at 3500x1969
is the render buffer included in the Use number ?

I think so, but I am not sure Boris. Can you render the same scene at half resolution to see if the reported memory changes? ... Anyway I don't know the internals of the statistics system. I think that if your GPU is not used for display, the available RAM (used+free) should be near the max. memory available, but it is clear from your report that this is not the case.

-Juanjo

Sun Oct 18, 2015 5:09 pm

I am often having problems with activating both render nodes at the same time.

In the workstation I use 1 GPU.

First node has 5 GPUs and the secong 6 GPUs.

If I enable both nodes in the newtork properties only one node starts working.

To make it work properly I need to restart the nodes daemons, enable only one node and then start rendering, when it starts rendering then I need to enable the second node and only then it starts rendering properly. After this I can load other scene, restart renderings and both will render at the same time. There are no errors reported in the deamons. I can record videos of the problem if necessary or provide deamon logs.

Sun Oct 18, 2015 9:59 pm

Hi Juanjo,

I've just rendered out 2000 HD frames over 8 days, 2 X 780 and 1 X 980 TI, with absolutely no issues, crashes etc.
Bloody marvelous plugin! Keep up the good work.

Cheers,
Andrew

Sat Oct 24, 2015 2:19 pm

GPU memory los is not dependant on the resolution, I miss 1GB even before I start Octane so must be Win 10 issue.

viewtopic.php?f=9&t=50826