OctaneRender™ Standalone 2.01 - updated

VIP Information, news and announcements regarding new Octane Render commercial products and releases.
Post Reply
User avatar
roeland
OctaneRender Team
Posts: 1822
Joined: Wed Mar 09, 2011 10:09 pm

Hi all,

This is an update to version 2.00, with fixes to issues reported on the forum, and better rendering performance.

Update (24 June 2014)

We have fixed an issue with the new image texture system causing a GPU crash when a scene contains image texture nodes without a file name set.

Changes since version 2.00

The rendering performance is better than version 2.00, on average we could recover roughly half the performance loss compared to version 1.55. This improvement is dependent on the scene, some scenes may not render significantly faster while others render almost as fast as in 1.55.

Other changes:
  • Fixed intermittent crashes and UI freezes when working with the node graph editor.
  • Fix crash when the FPS value is set to 0 and the shutter interval is set in percent.
  • Removed the limitation on the number of textures, the amount of textures in a scene is limited only by available GPU memory.
  • Improved rendering of motion blur on rotating objects imported from alembic files
  • Fix missing instances from scatter nodes in some scenes.
  • Small changes on how the sliders in the node inspector work: Infinite sliders, which support editing the text with a left mouse click, show a text cursor instead of a default arrow cursor. All sliders can be edited with a right mouse button click.
  • Fixed slider behaviour on translation inputs of transform3D and transform2D nodes
  • Network rendering is disabled by default.
  • Scanning for network daemons uses less network resources and is faster.
  • More clear error message when the scan finds a network slave with a different version.
  • Improved error messages when a slave process crashes.
  • Parameter "parallelism" goes now up to 8, which increases render performance by a couple percent, but you should render at least 500 samples per GPU, because caustics will take longer to appear.
Download

Windows
- 64-bit installer
- 32-bit installer

Mac OS X
- 64-bit installer

Linux
- 64-bit archive

Happy rendering,
Your OTOY NZ Team
gordonrobb
Licensed Customer
Posts: 1247
Joined: Sat Mar 16, 2013 9:08 am

Cool. Can I just check that you mean the maximum number of textures is now no longer based on my cards maximum number, but my cards available memory?
Windows 8 Pro | i7 3770 OC | 32 GB Ram | Single Titan (plus Black Edition on Order) | Octane Lightwave |
User avatar
whersmy
Licensed Customer
Posts: 723
Joined: Thu Aug 30, 2012 7:40 am

Whoooooooooooop! 8-)
Octane 2022.1.1 nv535.98

x201t - gtx580 - egpu ec
Dell G5 - 16GB - dgpu GTX1060 - TB3 egpu @ 1060 / RTX 4090

Octane Render experiments - ♩ ♪ ♫ ♬
User avatar
abstrax
OctaneRender Team
Posts: 5506
Joined: Tue May 18, 2010 11:01 am
Location: Auckland, New Zealand

gordonrobb wrote:Cool. Can I just check that you mean the maximum number of textures is now no longer based on my cards maximum number, but my cards available memory?
Yes, that's correct. There is still a limit of 32766 nodes in the shader system itself, but that shouldn't create major issues.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
prodviz
Licensed Customer
Posts: 543
Joined: Sun Jul 14, 2013 6:00 pm

Hi,

thanks for the update.

The limit for depth in PMC, is set to 32.
Is there a way or an expression to override this?

cheers,

Steve
User avatar
tglaja
Licensed Customer
Posts: 57
Joined: Tue May 04, 2010 8:59 am
Location: Jakarta

"Removed the limitation on the number of textures, the amount of textures in a scene is limited only by available GPU memory."

This alone makes me want to upgrade.
GTX 560 2GB, AMD FX 8350, 8GB RAM, Win7 x64
User avatar
Seekerfinder
Licensed Customer
Posts: 1600
Joined: Tue Jan 04, 2011 11:34 am

roeland wrote: [*]Small changes on how the sliders in the node inspector work: Infinite sliders, which support editing the text with a left mouse click, show a text cursor instead of a default arrow cursor. All sliders can be edited with a right mouse button click.
Oi, thanks fellas!
Seeker
Win 8(64) | P9X79-E WS | i7-3930K | 32GB | GTX Titan & GTX 780Ti | SketchUP | Revit | Beta tester for Revit & Sketchup plugins for Octane
User avatar
resmas
Licensed Customer
Posts: 510
Joined: Thu Aug 09, 2012 10:44 pm
Location: Portugal
Contact:

Thanks Guys :D

cheers
resmas
i7-2600k | SSD Vertex 3 | WD Velociraptor | WS Revolution | 16GB Ram HyperX | PSU LEPA G1600W | 3 X Asus GTX590 |
https://pt-pt.facebook.com/arq.resmas
User avatar
enricocerica
Licensed Customer
Posts: 1012
Joined: Wed Nov 25, 2009 7:32 pm
Contact:

No more texture limit !? Well this is one very good news.
I made a quick test with a scene I'm working on and I meet some issues with at least one opacity texture not working, all the others seem to work fine, strange. I tried to reload it without success, when I use the previous version it works fine. Can't give more details about this problem.

Also, no change regarding the problem I met with the previous version : http://render.otoy.com/forum/viewtopic. ... 60#p191253
Modeling system : I7 32GB Windows 10 & Fujitsu Celsius H720
GPU : 1x Gigabyte GTX580 3GB + 1x MSI GTX780 3GB + 1x PALIT GTX780 6GB +1x Asus Stix GTX1070 8GB
http://www.myline.be
User avatar
abstrax
OctaneRender Team
Posts: 5506
Joined: Tue May 18, 2010 11:01 am
Location: Auckland, New Zealand

enricocerica wrote:No more texture limit !? Well this is one very good news.
I made a quick test with a scene I'm working on and I meet some issues with at least one opacity texture not working, all the others seem to work fine, strange. I tried to reload it without success, when I use the previous version it works fine. Can't give more details about this problem.
We found an issue where "in-memory" image textures will cause the render kernel to fail. Could that be the issue here? If not, if you could provide us with an example scene we can have a closer look.
Also, no change regarding the problem I met with the previous version : http://render.otoy.com/forum/viewtopic. ... 60#p191253
Not much we can say here. BSODs are usually caused by driver issues. Which driver did you install? Maybe try a clean install of a different one (don't forget to disable SLI afterwards). Also keep in mind that you should run the Standalone installer at least once to set up the TdrDelay correctly in the registry. Otherwise you may run into issues using displacement mapping.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Post Reply

Return to “Commercial Product News & Releases (Download here)”