finally some answers:roro_sab wrote:I have noticed several issues after working with the octane plugin for Daz Studio. I hope that the developers can explain why these issues are occurring and check if it is due to some wrong settings or some other reasons or bugs.
- as octane/cuda has some limits for the number of textures to use, the plugin needs to qualify what to use if the limit is exceeded; opacity maps have low priority this might lead them to be missed if the total number of maps is to high; you can check the number of maps that octane uses in the system tab (needs to start the render once to have octane report back the statistics)
- this is also most likely because of exceeded memory and/or textures limits.
- this is unfortunately due to limits in the studio save data methods; the next update will use a completely other method to save octane data to avoid this.
- to overcome this you should go to the preferences tab and down there in the texture settings switch the diffuse type from "auto" to "image" - this will always create (rgb)image nodes for diffuse maps.
- if your plugin build is .2312 (printed on the system tab ~ the middle of the page) you might try to download the installer again from your octanelive account download page; it contains a .2320 version that should fix a few memory issues which might help in this case
- what you can try is to update particular scene objects using the according viewport tool (last in the row).
- animation issues: some of them again sound like exceeding memory/texture limits. what might help is this: http://render.otoy.com/forum/viewtopic. ... 08#p159308