OctaneRender® 1.025 beta2.58b test release [Obsolete]

[matej]

ctrl+left mouse buton (on a right handed mouse) allows you to extend the selection of nodes, which can also be useful I think. Dragging with the right mouse button should not bring up the context menu.

Yes, I forgot about extending selection. Perhaps the middle mouse button should be used exclusively to pan, then? In big projects with lots of nodes & connections, you sometimes disconnect or move nodes when panning with MMB. Paining with the RMB, otoh, doesn't work if the cursor is above nodes / connections.

basically: the panning control should work everywhere on the GE area, regardless on what is under the cursor and at the same time not do any other actions, so that you dont accidentally restart the rendering.

[bepeg4d]

Does creating other types of macros fail as well (Texture or emission macros) ?

--
Roeland

exactly, all the three macro nodes, emission, material, texture make octane unexpectedly closed.
ciao beppe

[teecee2107]

Does creating other types of macros fail as well (Texture or emission macros) ?

--
Roeland

exactly, all the three macro nodes, emission, material, texture make octane unexpectedly closed.
ciao beppe

I encounter the same problem.

[roeland]

as a side note for roeland, in the osx version is not possible to create a new material macro node without octane crash, every other material nodes works

I have found the problem and I will fix it soon.

--
Roeland

[bepeg4d]

great, thanks roeland
ciao beppe

[roeland]

Two things:

1.) One annoying aspect of rendering with Octane is the focus stealing pop-ups 'loading image', 'voxelizing', etc... which effectively make you computer difficult to use when rendering animations, ie. you can't work on anything else on the comp because the pop-ups are constantly thrown in your face.

Couldn't these information be sent to the STDOUT instead? Or not shown at all, since its almost irrelevant ('loading image' pop-up for every image??). Only show graphical pop-ups when critical errors happen or user input is needed (like not finding texture files). So that the --quiet option would really be quiet, without interruptions for the user.

2.) I was doing two rendering jobs with a python batch script, of which one failed (CUDA device 0: KERNEL FAILED) halfway through. I noticed that in both cases (ie. the one that successfully finished and saved the render, and the one that crashed) the Octane process returns the same value: 0.

It wold be possible that a failed rendering would return a different value, so it could be identified and started again? This would make automation of rendering jobs a bit more effective.

matej, jaminique, are you running Linux? The quiet option works on Windows, but not on Linux. We have tried (and failed) to fix this in the past a couple of times. The problem with stdout is that Octane often doesn't run from a console, and on Windows it is not supported at all.

And the renders where the kernel failed: did you manually close those windows or did Octane crash?

--
Roeland

[matej]

Hi, I'm running Linux, yes. If the --quiet doesn't work as supposed on Linux, could we have a switch that would disable all the feedback, so that the popups would be never triggered? For advanced users only . In my case Octane does start minimized, but those dialogs keep showing nonetheless.

I always run Octane from the console, when doing batch rendering jobs and also when run from inside Blender, since Blender itself is started from the console. Most of the programs I use write output & errors in the console, so I got accustomed to use it. Of course this should not be expected from Windows users.

For the second problem, in that particular case Octane closed (I started it as a sub-process from a batch rendering script). If I start Octane separately, then the Octane window remains opened when a kernel failed happens. If it's possible for Octane to report a failed rendering back to the parent process it would be helpful. I would like to optimize my batch rendering script, so that jobs that fail are then restarted - so that my computer is not slacking off during the night

EDIT: I suppose I can verify if some render job failed, by checking if files were written. If there are no files, then Octane probably crashed for this particular job which would then need to be repeated.

[Zay]

I don't know if this has been mentioned before, but when working with more than 5 area lights, sometimes adding a new area light will kill the light of another area light you just set. It's on - but very very low light effect. To fix it you have to either redo the light or reload the scene.
But in some cases I don't see it before the entire scene is rendered.

[colorlabs]

I'm getting a crash, I've attached the scene and OSX crash report.

[colorlabs]

I get the same crash with 2.57