Octane Render 1.022 beta2.2 released [OBSOLETE]

[ROUBAL]

Hi,

Updated post below... Can't delete this one.

[SonarPhoton]

Hi

Grate new release, so far the most stable octane. At least on my pc. Thanks:-D

This might be nothing but a one time occurrence, but il report it anyway.

Rendering overnight an interior rendering, ended up on 4770 samples and using 446 of 495MB memory I stopped the rendering in the morning and when i paned the image octane froze.
Im unable to determine the resolution because i did not save after changing it.

[ROUBAL]

Hi,

Thank you for this new release. I have not been at home for 3 days, and I have just tested the new stable Octane version.

Well, I don't like being always a bad guy bringing bad news, but I have noticed several things :

- First (not the most annoying one), like reported since the first versions, the Device Manager and the two animation panels still appear behing the render window when something is rendering on it.

- The Mesh Preview Kernel node output is still not connected until you move it (Not really a problem, but it's just weird).

- When you save a scene using two GPU, and open later the ocs file to continue the work, only one GPU is usable (the default one = the weakest on which are connected the monitors). I found finally that a way of changing that in the device manager is to open the device manager before clicking on the mesh node.

- The most annoying according to my latest tests : Maybe an exporter problem or an Octane problem : When rendering from the Blender Export script, for the same settings events are happening at random :
1 - Export open Octane and display a runtime error.
2 - Export open and close Octane without creating the ocs file.
3 - Export, open Octane and puts the Mesh node and the Preview nodes on a different layer, not allowing to interconnect them !
4 - Export open and close Octane after creating the ocs file, requiring Manual reopening and reloading ocs.
5-Export open Octane and display directly the scene, not allowing to select the GPUs before clicking on the Mesh node.

For me, so far it has worked correctly only on a very small scene with animated cubes. I have tried the same scene with an animate character that I used with RC2, and I have not been able to render an animation with this "stable release".

[radiance]

Hi,

Thank you for this new release. I have not been at home for 3 days, and I have just tested the new stable Octane version.

Well, I don't like being always a bad guy bringing bad news, but I have noticed several things :

- First (not the most annoying one), like reported since the first versions, the Device Manager and the two animation panels still appear behing the render window when something is rendering on it.

- The Mesh Preview Kernel node output is still not connected until you move it (Not really a problem, but it's just weird).

- When you save a scene using two GPU, and open later the ocs file to continue the work, only one GPU is usable (the default one = the weakest on which are connected the monitors). I found finally that a way of changing that in the device manager is to open the device manager before clicking on the mesh node.

- The most annoying according to my latest tests : Maybe an exporter problem or an Octane problem : When rendering from the Blender Export script, for the same settings events are happening at random :
1 - Export open Octane and display a runtime error.
2 - Export open and close Octane without creating the ocs file.
3 - Export, open Octane and puts the Mesh node and the Preview nodes on a different layer, not allowing to interconnect them !
4 - Export open and close Octane after creating the ocs file, requiring Manual reopening and reloading ocs.
5-Export open Octane and display directly the scene, not allowing to select the GPUs before clicking on the Mesh node.

For me, so far it has worked correctly only on a very small scene with animated cubes. I have tried the same scene with an animate character that I used with RC2, and I have not been able to render an animation with this "stable release".

Hey,

We made the choice to move a few minor bugs to 2.3, as we had to release for various reasons. (mostly people awaiting the 2.2 for making reviews)
However, the last issues you mention, eg the blender script ones, can you report these in the blender script forum ? try to provide enough information to reproduce it, so enrico can fix the issues...

Radiance

[john]

Overall, this is the fastest, most stable version, but I have twice gotten the error message below. I can choose "ignore" and continue working without a crash.

[radiance]

Overall, this is the fastest, most stable version, but I have twice gotten the error message below. I can choose "ignore" and continue working without a crash.

can you reproduce it with a procedure ?

Radiance

[SurfingAlien]

Hi Radiance!
I haven't had too much time to play with RCs lately but this new beta is amazing: faster start, quicker scene/objects loading and more stable!

don't know if it's already been reported but 2.2 does indeed solve the problem with multiple GPUs on Macs, so now I can choose among the 9400m, the 9600GT and both of them in multi GPU mode... great! If I use one card for Octane and one for display the interaction is fantastic, and even if I use both cards for Octane it's pretty decent (specially considering these are low end GPUs...). of course in this last case my MBP also marked some new record for GPU temp (77°C) and fan speed (6200rpm)... so I don't think it's an optimal solution for long render times.

so big thumbs up Octane team!

cheers,
Alessandro

[ROUBAL]

Hi,

I have just noticed a weird thing : Moving a node in the graph editor restarts the rendering from 0.

[8Eggar8]

Hey!,

Am Excited about Diggin' in to the new package!
Am a newbie, Stepping in here after somebody in
the Rhino Newsgroup posted your Promo Discount Ad.

Looked into it a few times this afternoon at work (on my System I built which goes w/ me and noticed that after bringing in an OBJ (both on my creations as well as any of the sample Scenes) the Grid Icon is created, the instant I touch it, the system (blanks) crashes out to my desktop, no crash report no bugzilla, no nothing. I made sure SLI modes were turned off. Does Phys X need disabling as well? (just realized that is still turned on). Haven't been able to go further than that after about 10 trys.
I will turn physx off and see if that solves it.

MSI NF980-G65 MB, NVIDIA nForce 980a/780a SLI Chipset, BFG (2)x GTX 260's, 4GB OCZ DDR3, 680Watt, Athlon II x4 620 Propus running on XP64

[8Eggar8]

Nope Turning off the Physx package was a no-go either, wonder why
the render Viewport won't initiate