OctaneRender™ Standalone 1.11

[RealityFox]

Awesome! May I ask what version you plan on expanding the UV editing tools? I'm really looking forward to them :3

[cfrank78]

Awesome! May I ask what version you plan on expanding the UV editing tools? I'm really looking forward to them :3

You and many many others . We beged in many threads and very often for it, but no one took care of it so far hehe!

Chris!

[clausgs]

Hi Octane

I see on a earlier topic that there was some problems with V1.11t, I think it was for poser, do this standalone v1.11 have any similar problems or other issues??
I am on the way to download and install the standalone v1.11 update, just want to check with you before i do something that could harm my current setup....???

Claus

[BorisGoreta]

TITAN is giving different render result then GTX690/GTC680 combo.

Second image is TITAN with speckles. How is that possible ? Surface is diffuse with scattering medium.

[LudovicRouy]

It's the new feature called "chickenpox" you need a very powerfull CG to render it

[steveps3]

Ooooh, I want chickenpox... second thoughts maybe not.

[DayVids]

I tried to install it on my macbook pro with GTX 650M, and I get the following error:

Process: octane [7553]
Path: /Volumes/VOLUME/OctaneRender 1.11.app/Contents/MacOS/octane
Identifier: com.otoy.octanerender
Version: 1.00 (1.00)
Code Type: X86-64 (Native)
Parent Process: launchd [134]
User ID: 501

Date/Time: 2013-03-15 21:47:34.033 -0500
OS Version: Mac OS X 10.8.2 (12C3103)
Report Version: 10

Interval Since Last Report: 261069 sec
Crashes Since Last Report: 4
Per-App Crashes Since Last Report: 1
Anonymous UUID: 93105964-5285-C22F-DD82-45629A737C80

Crashed Thread: 0

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
Library not loaded: /usr/local/cuda/lib/libcuda.dylib
Referenced from: /Volumes/VOLUME/OctaneRender 1.11.app/Contents/MacOS/octane
Reason: image not found

[abstrax]

TITAN is giving different render result then GTX690/GTC680 combo.

Second image is TITAN with speckles. How is that possible ? Surface is diffuse with scattering medium.

Can you render the scene with only the 680 (i.e. 1 GPU)? If it renders without speckles I would assume that your hardware has sometimes some calculation errors. But to be 100% sure, could you send us the scene and we give it a shot at the office.

Cheers,
Marcus

[BorisGoreta]

I know what was the problem, I was testing the image rendered with one TITAN versus the image rendered with the rest of the GPUs ( 2 GTX690 and 1 GTX680 ). So with many GPUs the speckles get averaged out because each GPU produces speckles at different pixels.

There is a problem with Octane if I have more then 5 GPUs installed. It won't start. I have to run it in software mode then. But if I run GTX690s in SLI then it works.

Also with more then 5 GPUs and non SLI configuration Photoshop does not have GPU acceleration and OpenGL in 3D software does not work well.

Is there a way to increase max GPU number ?

[abstrax]

I know what was the problem, I was testing the image rendered with one TITAN versus the image rendered with the rest of the GPUs ( 2 GTX690 and 1 GTX680 ). So with many GPUs the speckles get averaged out because each GPU produces speckles at different pixels.

With single-GPU setups or if you want to save HDR images, you may want to the hotpixel filter, maybe 70-80% that should get rid of most of the fireflies. Also try out the caustic blur (maybe set at 0.1 - 0.01 depending on the scene).

There is a problem with Octane if I have more then 5 GPUs installed. It won't start. I have to run it in software mode then. But if I run GTX690s in SLI then it works.

Also with more then 5 GPUs and non SLI configuration Photoshop does not have GPU acceleration and OpenGL in 3D software does not work well.

Is there a way to increase max GPU number ?

Yes, it seems that the NVIDIA drivers have problems with OpenGL on more than 5 NVIDIA GPUs. I don't know why that is, but that was one of the reasons why we added the software viewport mode.

The only way to get around this problem is to use a non-NVIDIA GPU for display, e.g. an onboard Intel graphics.

Cheers,
Marcus