Refractive Software® is proud to announce the availability of the beta 2.46b release, which fixes a few regressions of the beta 2.46 release candidate.
This version needs OctaneLive. You will find your OctaneLive account information in the customer area. You will find an FAQ here:
http://refractivesoftware.com/forum/vie ... =24&t=4069
IMPORTANT NOTE: Regarding CUDA toolkit use and multi-GPU support
During our migration to CUDA 3.2 we have noticed that due to changes to the CUDA toolkit by NVIDIA, our approach to multi-GPU rendering on Geforce products has been handicapped. As a result using more than one GPU for rendering does not offer a speed increase with the CUDA 3.2 releases.
We are rewriting the multi-GPU feature to resolve this issue, also adding some new features, so as an intermediate solution we will be supplying both CUDA 3.2 and CUDA 3.0 solutions.
- CUDA 3.2: Recommended version with better support for modern GPUs (like GeForce GTX 4xx/5xx), which should be used if you are not rendering on more than one GPU.
- CUDA 3.0: Legacy version for correctly functioning multi-GPU support.
Please note this version requires you to enter your OctaneLive® license information. These can be found as explained here:
http://www.refractivesoftware.com/forum ... =24&t=3095
How to connect to OctaneLive® through a firewall/router
If you have a firewall/router, and you cannot log into the octanelive® service (e.g. the server cannot be contacted), configure your firewall or router to allow outbound connections to the URL named 'live1.refractivesoftware.com', 'live2.refractivesoftware.com' and 'live3.refractivesoftware.com'. (the last one is provisionary)
CUDA drivers/toolkit requirements for Windows
To use this release you should install the latest Nvidia drivers for your GPU. It was built and tested with driver versions 260.99 (GeForce), 266.45 (Quadro) and 266.58 (GeForce).
CUDA driver requirements for Macintosh
The CUDA 3.2 release was built and tested with CUDA Toolkit 3.2.17. To use it you should install the latest NVIDIA drivers for your GPU, plus (in that order)
- the NVIDIA CUDA Toolkit 3.2.17, http://developer.nvidia.com/cuda-toolki ... oads#MacOS
- the NVIDIA CUDA Driver 3.2.17, http://www.nvidia.com/object/macosx-cud ... river.html
CUDA driver requirements for Linux
The CUDA 3.2 release was built and tested with CUDA Toolkit 3.2.16. To use it, you should install the graphics driver NVIDIA-Linux-x86_64-260.19.44 or later, plus the NVIDIA CUDA Toolkit 3.2.16 which you can download from: http://developer.nvidia.com/cuda-toolki ... oads#Linux
The CUDA 3.0 release was built and tested with CUDA Toolkit 3.0. To use it, you should install the graphics driver NVIDIA-Linux-x86_64-260.19.44 or later, plus the NVIDIA CUDA Toolkit 3.0 which you can download from: http://developer.nvidia.com/cuda-toolki ... oads#Linux
OctaneRender for Linux was built and tested on CentOS 5.5 using GCC 4.1.2. Due to that libstdc++ must be of version 4.1.2 or higher.
Download Here:
OctaneRender for MS Windows
Self installing executables (including the TdrLevel registry patch recommended for new users):
- 32bit version for CUDA 3.2: http://www.refractivesoftware.com/custo ... cuda32.exe
- 64bit version for CUDA 3.2: http://www.refractivesoftware.com/custo ... cuda32.exe
- 32bit version for CUDA 3.0: http://www.refractivesoftware.com/custo ... cuda30.exe
- 64bit version for CUDA 3.0: http://www.refractivesoftware.com/custo ... cuda30.exe
or as ZIP archives:
- 64bit version for CUDA 3.2: http://www.refractivesoftware.com/custo ... cuda32.zip
- 64bit version for CUDA 3.0: http://www.refractivesoftware.com/custo ... cuda30.zip
OctaneRender for GNU/Linux
Gzipped/tar archives:
- 64bit version for CUDA 3.2: http://www.refractivesoftware.com/custo ... cuda32.tgz
- 64bit version for CUDA 3.0: http://www.refractivesoftware.com/custo ... cuda30.tgz
OctaneRender for Apple Mac OS X (10.5/10.6)
Installer package:
- 32bit version for CUDA 3.2: http://www.refractivesoftware.com/custo ... cuda32.pkg
- 32bit version for CUDA 3.0: http://www.refractivesoftware.com/custo ... cuda30.pkg
Fixes since beta 2.46
Code: Select all
- fixed memory leak when alpha channel output is enabled
- system macro nodes like "Preview Configuration" can't be renamed anymore
- switching between materials doesn't reset the material ball camera anymore
- fixed crash bug when you try to render the material ball scene in a multi-GPU setup
- fixed problem, that you couldn't load embedded images on Linux and Mac OS, when they have been saved a second time
Code: Select all
- new updated manual
- when material picker is used only the pin of the actual selected material is highlighted
- fixed missing tool tips
- fixed incorrect Unicode handling for image files on Linux and Mac OS
- increased maximum emission power to 100,000
- fixed black text in edit fields
- slider bars are darker now, to enhance visibility of slider triangle
- better display of OctaneLive status on Linux
- improved UV mapping and vertex normals of material ball
Code: Select all
RENDERER
- added light distribution input for emitters, incl. rotation
- light power is now specified as total power
- added support for IES files to be used as light distribution
- generated textures can now be used as environment texture
- new improved material ball scene
- improved shading behind the light terminator
- emitting materials now also work in the material preview, when the directlighting kernel is used
- shifted render camera output by 1/2 pixel
- fixed incorrect north offset calculation of daylight sun
USER INTERFACE
- added new note node
- added new listint node
- added button "Update" to commit manually entered resolutions, which should solve missed resolution changes
- new tab design with close buttons
- toolbars are now customizable and can be placed an the four sides of a pane
- the pane selection is now an icon
- a default scene can now be saved, which will be used as template for all new projects
- improved display of nodes in the node inspector
- fixed crash when the node inspector is resized with the daylight node being displayed there
- fixed incorrect node placement of materials dragged from the LiveDB to the node graph editor
IO / CONTROL
- macros in the OctaneLive material database are now sorted by name
- texture paths and material names can contain now spaces and non-ASCII characters as long as they are encoded in UTF-8
- less strict handling of relative path names that are specified like "/daz_textures/texture.png" (this should make the import of DAZ exports work again)
- added new option to store file paths as relative paths in OCS files (which ON by default)
- proper error handling for too large macros that will be uploaded to OctaneLive (the maximum is now 15MB)
- more robust time-out handling with OctaneLive
- fixed incorrect error messages in authenticatin dialog
- fixed crash when an input node of a loaded macro gets deleted
Please post your experiences and issues with this release in this thread. Your help is much appreciated.
Yours,
The OctaneRender® Team.
