OctaneRender® 1.024 beta 2.45 (lin/mac/win) [OBSOLETE]

[yoyoz]

Thanks Marcus.

Still some issues in multi-GPU. Note this only happen when the viewport has changed (zoom or move camera). I can render clean images if save/exit/reload and then let run without touching anything. This has happened in the past, so it's not new to 2.45.

[yoyoz]

My 'reference' bad mesh also still makes octane crash at import with "ERROR: Program executed illegal instruction.. terminating"

Cheers,
Lionel

[abstrax]

Thanks Marcus.

Still some issues in multi-GPU. Note this only happen when the viewport has changed (zoom or move camera). I can render clean images if save/exit/reload and then let run without touching anything. This has happened in the past, so it's not new to 2.45.

Does it always happen or only sometimes in specific scenes? Does the chess scene render correctly? I just tried it here with a GTX 470 and a GTX 460 and it renders fine.

Cheers,
Marcus

[yoyoz]

Here's some additional info that might help you:
- demos scenes and small scenes seems to always work fine
- it only happens when the 2 GPUs are activated
- I increased the polys on a working scene and couldn't reproduce the issue (trying to make a relationship with memory usage)

This is not critical for me, just annoying, but I'm curious to know where it comes from.

Configuration:
- GTX295 with 260.19.36 drivers and cuda 3.0
- xorg.conf is set up with Option "MultiGPU" "None"
- desktop resolution 1920x1200x24
- no desktop effects and no compositing

I'll be on holidays tonight so plenty of time ahead if you want I make additional tests (also got dual-boot to W7 available if you need I try to reproduce on Windows).
Cheers,
Lionel

PS: I like the new material preview background a lot - Looks very clean and is much more informative!

[abstrax]

Hi Lionel,

Thanks for your efforts. I tried it on Cent OS. I while ago I have seen something similar: Different auto-focus settings for both GPUs and similar weird effects. Unfortunately this went away after the next Octane launch and never came back, so I'm not exactly sure what went wrong since I couldn't reproduce it.

It would of great help, if you have a scene where this problem is reproducable.

Cheers,
Macus

[face]

Have found two other issues...
Only one time i has a problem with setting the y resolution. It was not possible to change it.

The other thing is if i delete the mesh node, the mesh is present in the memory and shown in the renderwindow.
I can zoom, pan and rotate it and after a moment, Octane close without an error...

face

[garak]

Hello,

As far as I can see, nothing has changed to previous versions. I have made a fix now, that when you drag a material from the LiveDB onto the node graph editor, it gets the name of the LiveDB entry and not the original name the macro had, when it was added to the LiveDB. I hope that is ok.

That is a very much OK for me.

I never took a closer look at the Object material node names (what are they call actually?), i always used the tooltips.
I really appreciate this new build.

Cheers,

Bernd

[yoyoz]

It would of great help, if you have a scene where this problem is reproducable.

Thanks for investigating, I'll PM you a link for the watch scene (7z, 36GB).

Kind regards,
Lionel

[Jaberwocky]

Abstrax

One thing also to think about.If this next build 2.45B is going to also be the demo fownload for prospective customers.You will need to update the manual with the new added features and package that in with it.The one packaged at the moment states beta 2.3

Looking forward to the update on Monday

Cheers

[grimm]

Looking good, thanks Marcus.

I have had the following problems so far:

The tooltips are missing for both the interface and node pins. I think others have noticed this too.

When I loaded a OCS file the render window resized on it's own and took over the display. The OCS file has a resolution size that is greater then my display resolution might have had something to do with it. I first thought that it had maximized the render window but when I clicked on the expand button it just tried to get larger. I ended up having to manually resize all the windows.

I'm having a tough time setting blackbody emission values to look right. I'm probably doing it wrong, but I have to set both the power and efficiency sliders to 100% to get a reasonable amount of light to appear. And it isn't very bright. The temp slider only appears to change the color.

I will test some more tomorrow.