OTOY Forums

"Detected that heart beat of Slave stopped --> stopping slave
Stopped logging on"

This is being investigated.

Paul

face_off wrote:

Octane not loading default materials at start up

I am not quite sure what you mean by this. Can you explain more pls? The "default" material is only used the first time a Revit material is converted to an Octane material in a given scene. So if you load a .rvt file, it will load the Octane materials that were previously saved in that .rvt, not the defaults. You can see all the materials which have defaults in your C:\Users\[username]\AppData\Local\OctaneRender for Revit\Defaults folder. The latest release will save defaults in OCS format, and if there is a default for a material in both OCS and XML format, it will load the OCS file (if there is no OCS, it will load the XML file).

(having to load them individually and manually)

How are you doing this pls? What plugin menu items are you using to load them?

Paul

As in when i modify materials in the materials tab in octane i then right click and save as default (I also export the material). But when i open up octane again (as in either it's the first time in the day or I've exited the octane addi-in tab) the materials revert to a previous version that is out dated and I need to reload the default for each (right click on a material in the materials tab and load default).
Thanks

As in when i modify materials in the materials tab in octane i then right click and save as default (I also export the material). But when i open up octane again (as in either it's the first time in the day or I've exited the octane addi-in tab) the materials revert to a previous version that is out dated and I need to reload the default for each (right click on a material in the materials tab and load default).

It sounds like you are loading a scene which already has the Revit materials converted to Octane materials. Defaults are only applied when you run the first the first time for a Revit scene which has never had the plugin run on it before (so it needs to convert the Revit materials to Octane materials).

Paul

Sonnemanntoon wrote:Hi Paul, I've updated the plugins to the latest release - 2.16.25 - on the two computers I'm using at the moment (one slave, one master); I've also updated the graphic drivers on both - to the latest Nvidia release, but unfortunately I'm still encountering the issues - ie Octane not loading default materials at start up (having to load them individually and manually); Slave crashing at pretty much every render when networking.
Computer specs:
Both are HP,
running windows 7 pro
Processor: Intel Xeon, CPU E5-1620 0 with 3.6 GHz
Ram: 12 GB
64 bit OS

Running revit 2015 latest updates installed.

The error message i get on the slave daemon:

"Detected that heart beat of Slave stopped --> stopping slave
Stopped logging on"

This is happening at every render and is really slowing our work down. Hope the info helps
Thanks

The heart beat is a mechanism of the daemon to figure out if the slave hang up somehow, for example due to a deadlock or something other bad. There is an issue when an HDR result is fetched (see http://render.otoy.com/forum/viewtopic. ... 59#p219359), but I talked to Paul and this is probably a different issue.

Does this issue occur in all scenes, even simple ones? Do you use displacement mapping? What's the resolution you are rendering?

The first step in solving the problem would be to enable logging for the master, slave and daemon. Tomorrow I will write a post explaining how to do that and hopefully I will then be able to understand the problem.

face_off wrote:

As in when i modify materials in the materials tab in octane i then right click and save as default (I also export the material). But when i open up octane again (as in either it's the first time in the day or I've exited the octane addi-in tab) the materials revert to a previous version that is out dated and I need to reload the default for each (right click on a material in the materials tab and load default).

It sounds like you are loading a scene which already has the Revit materials converted to Octane materials. Defaults are only applied when you run the first the first time for a Revit scene which has never had the plugin run on it before (so it needs to convert the Revit materials to Octane materials).

Paul

Hi paul, how would i tell octane to convert all the materials from revit to octane at start up?
thanks

abstrax wrote:

Sonnemanntoon wrote:Hi Paul, I've updated the plugins to the latest release - 2.16.25 - on the two computers I'm using at the moment (one slave, one master); I've also updated the graphic drivers on both - to the latest Nvidia release, but unfortunately I'm still encountering the issues - ie Octane not loading default materials at start up (having to load them individually and manually); Slave crashing at pretty much every render when networking.
Computer specs:
Both are HP,
running windows 7 pro
Processor: Intel Xeon, CPU E5-1620 0 with 3.6 GHz
Ram: 12 GB
64 bit OS

Running revit 2015 latest updates installed.

The error message i get on the slave daemon:

"Detected that heart beat of Slave stopped --> stopping slave
Stopped logging on"

This is happening at every render and is really slowing our work down. Hope the info helps
Thanks

The heart beat is a mechanism of the daemon to figure out if the slave hang up somehow, for example due to a deadlock or something other bad. There is an issue when an HDR result is fetched (see http://render.otoy.com/forum/viewtopic. ... 59#p219359), but I talked to Paul and this is probably a different issue.

Does this issue occur in all scenes, even simple ones? Do you use displacement mapping? What's the resolution you are rendering?

The first step in solving the problem would be to enable logging for the master, slave and daemon. Tomorrow I will write a post explaining how to do that and hopefully I will then be able to understand the problem.

Hi, thanks for the response
Looks like it may be the same issue - most of the scenes we're rendering are using an HDR background as environment and are above 1300x732 px. Many also contain displacement maps for textures such as feature walls and cushions or carpet. Last night I was able to successfully render a large scene as described with one slave and am rendering at the moment as well (the same scene). However this took several attempts. I'll take a look at your post tomorrow then.
Thanks

how would i tell octane to convert all the materials from revit to octane at start up?

When you start the plugin for the first time on a scene, it will automatically convert all Revit materials to Octane materials (which will be displayed in the Materials tab), and if any of these material have "default" Octane materials (which were previously saved with Save As Default), that default will be used instead. If you then save that scene and reload it - the Octane materials are saved to the .rvt, and reloaded (so there is no re-conversion).

Paul

Sonnemanntoon wrote: Hi, thanks for the response
Looks like it may be the same issue - most of the scenes we're rendering are using an HDR background as environment and are above 1300x732 px. Many also contain displacement maps for textures such as feature walls and cushions or carpet. Last night I was able to successfully render a large scene as described with one slave and am rendering at the moment as well (the same scene). However this took several attempts. I'll take a look at your post tomorrow then.
Thanks

Just for your information the problem that manalokos reported will be solved in the next stable and development releases, but to be sure that you don't stumble over a different problem, please do the following:

1) Unpack into the directory where the slave is installed. The archive contains two files octane_log_flags.txt and octane_daemon_log_flags.txt. The first one enables logging of daemon and net render messages of the slave and the second one enables messages of daemon. The files are read only once during startup, so you will have to restart the daemon to enable logging. The logging will appear in the console and will also be stored in octane_daemon_log.txt and octane_log.txt.

2) Unpack into the directory where the octane.dll of the plugin can be found. The archive contains the file octane_log_flags.txt which enable logging of net render messages in the plugin. Again, you will have to restart the plugin to enable logging.

Now, when you use network rendering and the slave gets killed by the daemon, you would need to copy the three log files from the master, slave and daemon, before you restart, otherwise the files would be overwritten. When you have a set of log files for the problem you reported, please send them to me via PM. Thanks a lot for your help in advance.

Hi,
Just for info - the slave crashing issue hasn't been recurring in the past 2 days. I haven't changed anything though so no idea why...
Thanks

I have refreshed the installers at the top of this thread with:

2.20.0.26
- Compiled with Octane 2.20 (see Octane Standalone for details)
- Added Tooltips to the Octane pins for all nodes in the Setup and Material trees
- Added Materials tab menu options to Copy Material To Clipboard and Paste Material From Clipboard - to allow copy/paste of materials between the plugin and other Octane plugins or Octane Standalone
- OCS files can now be loaded as proxies (similar to using ORBX files as proxies)
- Added Polygon Side texture node (see Octane Standalone 2.14 release notes for details)

Paul