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

[justix]

Hi all,

As promised, here comes the test release with the new render kernel and spectral dispersion. There has also been some under-the-hood work on the internal message system and the way how OCS/OBJ files are loaded. The idea behind this version is to get some early feedback for these changes.

To use the new PMC kernel, you need a device of compute model 1.1 or higher.

This version is a test release and should not be used for production work. Scenes stored in this version may not load in beta 2.46b.

Please do not clutter this thread with wishes, requests and ideas. It's not that we are not interested, but currently we have to focus on the the stuff planned for beta 2.5.

Of course, any feedback on the render kernel and/or problems we might have introduced since beta 2.46b is very welcome and much appreciated.

This release was built with CUDA 4.0, which means that you should install the latest graphics driver (http://www.nvidia.com/page/drivers.html). On Mac OS and Linux you also have to install the latest CUDA 4.0 toolkit and driver (http://developer.nvidia.com/cuda-toolkit-40). We have tested it on Mac with the latest graphics driver provided by the Mac updates. On Linux we tested with NVIDIA driver 270.41.19 and on Windows with NVIDIA driver 275.33.

Since this release does not contain the changes in our render framework, multi-GPU still does not work properly and is not the focus for it.

Here are the archives (to save time we haven't build installers):

Linux 64bit: http://www.refractivesoftware.com/rcdow ... ux_x64.tgz

MacOS 32bit: http://www.refractivesoftware.com/rcdow ... acos32.zip

Windows 64bit: http://www.refractivesoftware.com/rcdow ... in_x64.zip
Windows 32bit: http://www.refractivesoftware.com/rcdow ... _win32.zip

Yours,
The OctaneRender® Team.

Guys..are 275.33 Nvidia drivers Cuda 4.0?(win 7 64) or should I just install devdriver_4.0_winvista-win7_64_270.81_general instead? sorry I'm a bit confused

[face]

Guys..are 275.33 Nvidia drivers Cuda 4.0?(win 7 64) or should I just install devdriver_4.0_winvista-win7_64_270.81_general instead? sorry I'm a bit confused

This release was built with CUDA 4.0, which means that you should install the latest graphics driver (http://www.nvidia.com/page/drivers.html). On Mac OS and Linux you also have to install the latest CUDA 4.0 toolkit and driver (http://developer.nvidia.com/cuda-toolkit-40). We have tested it on Mac with the latest graphics driver provided by the Mac updates. On Linux we tested with NVIDIA driver 270.41.19 and on Windows with NVIDIA driver 275.33.

On Windows you should install minimum driver v275.33.
There is no need for a dev driver.

face

[falcon76]

On Windows you should install minimum driver v275.33.
There is no need for a dev driver.

face

I'm having problem installing the new v275.33 driver on my system. I have a dual GPU: Quadro (for display) and GeForce GTX470 for CUDA. Actually, with driver 266.58 WHQL, I have no problem (for both GPU).

While installing the new driver the video goes black and nothing else happen. Someone with a similar configuration have succeed in installing the new driver? Can be CUDA 4.0 installed with driver 266.58?

Thanks
Luca

[face]

I have issues on Octane with Linux.
PMC gives me a wired result.
The image has 256 samples.

An other issue is, the save or load screen freezes Octane when i move it around.

Process info:

Stack info:

stack.tar.gz

(1.4 KiB) Downloaded 156 times

Pmap info:

pmap.tar.gz

(1.84 KiB) Downloaded 111 times

Fedora Core 14, GNOME 2.32.0, Kernel 2.6.35.13-91.fc14.x86_64, NVIDIA driver 270.41.19, CUDA Toolkit 4.0.8.

face

[GeoPappas]

Can be CUDA 4.0 installed with driver 266.58?

No. The first NVIDIA drivers with CUDA 4.0 support are the 270 series of drivers.

Here is a quote from the 270.51 Beta driver (http://www.nvidia.com/object/win7-winvi ... river.html):

Adds support for applications using CUDA 4.0 features such as Unified Virtual Addressing (UVA) and GPUDirect™ v2.0.

[r4ytrace]

I'm dismayed to see that even the latest of the 'movie acclerating' nvidia drivers is causing me BAD hangs - I thought theyda have fixed it by now :/

[justix]

Guys..are 275.33 Nvidia drivers Cuda 4.0?(win 7 64) or should I just install devdriver_4.0_winvista-win7_64_270.81_general instead? sorry I'm a bit confused

This release was built with CUDA 4.0, which means that you should install the latest graphics driver (http://www.nvidia.com/page/drivers.html). On Mac OS and Linux you also have to install the latest CUDA 4.0 toolkit and driver (http://developer.nvidia.com/cuda-toolkit-40). We have tested it on Mac with the latest graphics driver provided by the Mac updates. On Linux we tested with NVIDIA driver 270.41.19 and on Windows with NVIDIA driver 275.33.

On Windows you should install minimum driver v275.33.
There is no need for a dev driver.

face

nice

[radiance]

I have issues on Octane with Linux.
PMC gives me a wired result.
The image has 256 samples.

PMC.jpg

An other issue is, the save or load screen freezes Octane when i move it around.

Process info:

Screenshot.jpg

Stack info:

stack.tar.gz

Pmap info:

pmap.tar.gz

Fedora Core 14, GNOME 2.32.0, Kernel 2.6.35.13-91.fc14.x86_64, NVIDIA driver 270.41.19, CUDA Toolkit 4.0.8.

face

Hi face,
this is very strange, what's the result with pathtracing ?
Also, could you zip up your entire scene and PM us a dropbox link or something, so we can check it ?

Thanks,
Radiance

[face]

Hi face,
this is very strange, what's the result with pathtracing ?
Also, could you zip up your entire scene and PM us a dropbox link or something, so we can check it ?

Thanks,
Radiance

Pathtracing looks fine.
Hm, realy strange, it's not scene specific.
I import only a mesh, switch from directlight to PMC and have the result shown as above.
But, sometimes it works. When it works, i change the maxsamples and i become the same messy result.
Then i can switch forth and back the render kernel, playing with the maxsamples and sometimes it works.

Have also seen on one specific imported mesh, the diffuse and speccolor is black, the result looks shiny white.
And that is under the directlight kernel.
If i play with the colors, it looks good.

I can also not exit Octane.
If i hit the X or use the file exit dialog, i become the message to save the file, thats then all and Octane hangs...
It works only, if i open Octane without anything to do. Then i can quit...

The next thing, i can't reload an other mesh.
After reload, i will see the old one and can play with them.

I think there are some issues with my GTX285 and Cuda 4.0 under Linux.
Under Windows all works good.

I should test an earlier Octane version and check if it works...

face

[DayVids]

Have the pathtracing and Direct Lighting Kernels been optimized further?

They seem to be reaching a point of acceptable appearance on my current render at around 200-400 samples rather than 600 or so?

I'm rendering a Logo icon spinning with HDRI Map light only. Either way, it's reaching a higher sample's/pixel faster, and it's seeming to converge removing the grain faster as well. I'm Very pleased with this release.