OctaneRender™ Standalone 2.15

Wed Dec 17, 2014 3:08 pm

Hello

Here is an example exemplifying the problem, when you connect each texture to the diffuse pin they show the correct size, but through the mix node it inherits the scaling of the first texture.

Kind regards
Filipe

Thu Dec 18, 2014 10:38 am

Hi all
we're using the octane plugin for revit at the office. We have 3 standalone licenses + plugin licenses. Everything works fine and wanted to start networking. I downloaded the latest 2.xx version of the standalone and slave plugin. When I'm in Octane the slaves come up in the networking preferences window. But when I'm in the revit plugin nothing appears on the master screen. I was wondering whether this is due to the fact that I have the latest version of the plugin for revit - 2.0 - and that it's not compatible with the 2.15 version of the slave daemon? If so is there a 2.0 version?
Thanks!

Thu Dec 18, 2014 11:29 am

Hi,

on my iMac 10.10.1 OSX when i try to switch to fullscreen mode... octane freezes. Anybody has this issue on Mac with the release of Octane Standalone?

Beppe OctaneRender™ Italia Blue Sky · Thu Dec 18, 2014 11:50 am

hi,
here is the workaround suggested by abstrax:

There seems to be an issue with the OpenGL viewport which got introduced with 2.14. We try to fix it with the next release. In the meantime, please use the software viewport (File -> Preferences... -> Application -> Viewport).

it works well for me, i hope it works also for you

ciao beppe

Thu Dec 18, 2014 4:36 pm

When changing a texture in the Node Inspector it often happens that you can't Undo it. Sometimes it even clears the node completely.

Thu Dec 18, 2014 9:16 pm

People who have been trying to use network rendering on OSX may have notices that the slave and daemon didn't work. The reason were a missing file and a linker bug in the slave. I rebuilt the OSX package which should fix this problem.

Thu Dec 18, 2014 11:06 pm

Zay wrote:When changing a texture in the Node Inspector it often happens that you can't Undo it. Sometimes it even clears the node completely.

Unfortunately I wasn't able to reproduce the problem. Could you give us a step-by-step description of what you do? Thanks.

Mon Dec 22, 2014 4:08 pm

Another annoying bug is when you want to change a texture and click on "Load New Image" in the Node Inspector, the dialog pops up to pick an image. If I double click on the image I want it will pick another texture that is behind the dialog window before it closes and you are wondering why nothing happens to the texture you just loaded while fiddling with the settings until you realize it's the wrong material you are working on.
So it seems that the Material Picker is still active in the dialog browser and can pick what is behind it in the viewport.
This doesn't happen in Octane 2.06.

Mon Dec 22, 2014 8:23 pm

Zay wrote:Another annoying bug is when you want to change a texture and click on "Load New Image" in the Node Inspector, the dialog pops up to pick an image. If I double click on the image I want it will pick another texture that is behind the dialog window before it closes and you are wondering why nothing happens to the texture you just loaded while fiddling with the settings until you realize it's the wrong material you are working on.
So it seems that the Material Picker is still active in the dialog browser and can pick what is behind it in the viewport.
This doesn't happen in Octane 2.06.

Hmm, I can't reproduce it here. To recap: You are using the material picker tool in the viewport and then click on "Load new image" of an image texture node and then select a file via a double-click. The file is then chosen and the material at the mouse position is picked, too?

You are sure that you just do a double-click on the file name? Could you check if the problem occurs in the OpenGL viewport and in the software viewport (File -> Preferences... -> Application -> Viewport)? Which operating system do you use?

Mon Dec 22, 2014 9:57 pm

abstrax wrote:You are sure that you just do a double-click on the file name? Could you check if the problem occurs in the OpenGL viewport and in the software viewport (File -> Preferences... -> Application -> Viewport)? Which operating system do you use?

Since it works fine in 2.06 I don't think it's more than a double click. Sent you a PM.