OctaneRender™ 2018.1 RC4

Forums: OctaneRender™ 2018.1 RC4
A forum where development builds are posted for testing by the community.
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.

OctaneRender™ 2018.1 RC4

Postby haze » Wed Feb 13, 2019 9:35 pm

haze Wed Feb 13, 2019 9:35 pm
Hi all

We have done several more fixes for bugs reported since 2018.1 RC3. Please be aware that Studio builds of 2018.1 now support only 1 GPU, and no network rendering.

2018.1 and its XB and RC builds will only be available for customers with a version 4 license while 2018.1 is not yet stable. To try 2018.1 you need to upgrade your version 3 license to a version 4 license. This can be done for free via our web shop: https://render.otoy.com/shop/upgrade.php.

Important: Please don't update your NVidia drivers yet, 418.81 and 418.91 both break Octane, please wait for Nvidia to release a fix, which hopefully will be shortly.

Changes since OctaneRender 2018.1 RC3:

  • Fixed crash when trying to save cryptomatte object layer passes.
  • Fixed emission with mix material.
  • Fixed incorrect render when the same VDB is loaded as SDF and as fog volume.
  • Fixed subdivision with vertex attributes (fixes several ABC loading issues).
  • Fixed missing window titles in Lua dialogs if native window titles are disabled in the application preferences.
  • Fixed LiveDB downloads sometimes failing and OctaneLive getting disconnected.
  • Fixed incorrectly exported 16 bit and 32 bit HDR images
  • Fixed network rendering with deep images.
  • Fixed some incorrect behaviour in the universal material when using IOR=1 / transmission=1 and caustic blur.
  • Fixed tonemap failure if over-under stereo is being used on small resolutions and with the eyes swapped.
  • Fixed transform nodes not updating transformations in the scene when there are linkers separating them from nodes.
  • Fixed render failure when rendering a vectron node with an OSL texture input.
  • Fixed render failure when trying to use vertex attributes with displacement. This is not yet supported, but planned.
  • Fixed using greyscale images as opacity maps.
  • Fixed normals for spheres with motion blur.
  • Fixed crash when cancelling a load from Alembic

Downloads for users with a regular license
OctaneRender for Windows (installer)
OctaneRender for Windows (zip)
OctaneRender for Mac OS
OctaneRender for Linux

Downloads for users with a Studio subscription license
OctaneRender Studio for Windows (installer)
OctaneRender Studio for Windows (zip)
OctaneRender Studio for Mac OS
OctaneRender Studio for Linux

Downloads for users with an Enterprise subscription license
OctaneRender Enterprise for Windows (installer)
OctaneRender Enterprise for Windows (zip)
OctaneRender Enterprise for Mac OS
OctaneRender Enterprise for Linux


Happy rendering,
Your OTOY Team
User avatar
haze
OctaneRender Team
OctaneRender Team
 
Posts: 795
Joined: Sun Feb 08, 2015 8:57 pm

Re: OctaneRender™ 2018.1 RC4 [latest 2018]

Postby Notiusweb » Fri Feb 15, 2019 11:10 am

Notiusweb Fri Feb 15, 2019 11:10 am
Hello, some things:

1) Images are exporting 16-Bit correctly, so Very Good!

2) SSS attempts with the Universal Material are still failing to match Diffuse, as Transmission color still becomes a 'reflective shine' (see image below)

3) The outer cone-shell of a Spectron/Volumetric Spotlight, is there some way to blur, fade it, as it looks too harsh when not extended beyond the camera FOV (see image below)

Karen7_01.png


THX!
Win 10 Pro 64, Xeon E5-2687W v2 (8x 3.40GHz), G.Skill 64 GB DDR3-2400, ASRock X79 Extreme 11
Mobo: 1 Titan Xp, 1 Titan X Pascal
External: 6 Titan X Pascal - 1600W EVGA T2
Plugs: 3DSMax, C4D, Daz, Houdini, Lightwave, Sketchup
User avatar
Notiusweb
Licensed Customer
Licensed Customer
 
Posts: 1128
Joined: Mon Nov 10, 2014 4:51 am

Re: OctaneRender™ 2018.1 RC4 [latest 2018]

Postby PolderAnimation » Fri Feb 15, 2019 11:55 am

PolderAnimation Fri Feb 15, 2019 11:55 am
When using an colour vertex attribute in a specular material in the Transmission octane stops working.

edit: I have send an example file to Marcus.
Last edited by PolderAnimation on Sun Feb 17, 2019 2:00 pm, edited 1 time in total.
Win 10 64bit | 5 x 1080ti | i7 4770 | 32GB
User avatar
PolderAnimation
Licensed Customer
Licensed Customer
 
Posts: 276
Joined: Mon Oct 10, 2011 10:23 am
Location: Netherlands

Re: OctaneRender™ 2018.1 RC4 [latest 2018]

Postby PolderAnimation » Sun Feb 17, 2019 9:00 am

PolderAnimation Sun Feb 17, 2019 9:00 am
I read some time ago that you guys are thinking of making an own caching format. Is that still something you guys are thing about? And in such a system will the compiling of the scene be reduced? Just curious :).
Win 10 64bit | 5 x 1080ti | i7 4770 | 32GB
User avatar
PolderAnimation
Licensed Customer
Licensed Customer
 
Posts: 276
Joined: Mon Oct 10, 2011 10:23 am
Location: Netherlands

Re: OctaneRender™ 2018.1 RC4 [latest 2018]

Postby haze » Sun Feb 17, 2019 7:48 pm

haze Sun Feb 17, 2019 7:48 pm
PolderAnimation wrote:I read some time ago that you guys are thinking of making an own caching format. Is that still something you guys are thing about? And in such a system will the compiling of the scene be reduced? Just curious :).


Yes and yes.
User avatar
haze
OctaneRender Team
OctaneRender Team
 
Posts: 795
Joined: Sun Feb 08, 2015 8:57 pm

Re: OctaneRender™ 2018.1 RC4 [latest 2018]

Postby bagel » Sun Feb 17, 2019 8:17 pm

bagel Sun Feb 17, 2019 8:17 pm
haze wrote:Please be aware that Studio builds of 2018.1 now support only 1 GPU, and no network rendering.


Is this a permanent limitation of the studio subscription version?
bagel
Licensed Customer
Licensed Customer
 
Posts: 41
Joined: Tue Jan 23, 2018 3:38 pm

Re: OctaneRender™ 2018.1 RC4 [latest 2018]

Postby Goldorak » Sun Feb 17, 2019 9:26 pm

Goldorak Sun Feb 17, 2019 9:26 pm
bagel wrote:
haze wrote:Please be aware that Studio builds of 2018.1 now support only 1 GPU, and no network rendering.


Is this a permanent limitation of the studio subscription version?


Nothing is set in stone, but this limit is in place while we review how we will handle NV Link support for subs (and RTX boost shortly) going forward.
User avatar
Goldorak
OctaneRender Team
OctaneRender Team
 
Posts: 1923
Joined: Sun Apr 22, 2012 8:09 pm

Re: OctaneRender™ 2018.1 RC4 [latest 2018]

Postby bagel » Sun Feb 17, 2019 9:30 pm

bagel Sun Feb 17, 2019 9:30 pm
Thanks for the reply! I was concerned!

I'm just going to leave this here: https://render.otoy.com/requests/?qa=46 ... ense-slave
bagel
Licensed Customer
Licensed Customer
 
Posts: 41
Joined: Tue Jan 23, 2018 3:38 pm

Re: OctaneRender™ 2018.1 RC4 [latest 2018]

Postby haze » Mon Feb 18, 2019 10:18 pm

haze Mon Feb 18, 2019 10:18 pm
PolderAnimation wrote:When using an colour vertex attribute in a specular material in the Transmission octane stops working.

edit: I have send an example file to Marcus.


Fixed for next release.
User avatar
haze
OctaneRender Team
OctaneRender Team
 
Posts: 795
Joined: Sun Feb 08, 2015 8:57 pm

Re: OctaneRender™ 2018.1 RC4 [latest 2018]

Postby coilbook » Tue Feb 19, 2019 3:10 am

coilbook Tue Feb 19, 2019 3:10 am
now these new errors appear without any reasons. these scenes were rendered for months and all the sudden all these scenes do this. Nothing was changed Even isolating one object this scene does this


I was rendering with these drivers for a long time and all the sudden i cannot even open octaneviewport without an error .

denoiserThread0 : Initialization failed. Restart required
CUDA error 702 on device 0: the launch timed out and was terminated
-> kernel synchronization failed
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to load symbol data to the device(const11)
device 0: failed to upload imager params
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to unregister pinned memory
CUDA error 702 on device 0: the launch timed out and was terminated
-> could not get memory info
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to unregister pinned memory
CUDA error 702 on device 0: the launch timed out and was terminated
-> could not get memory info
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to destroy CUDA event
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to destroy CUDA event
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to deallocate device memory
CUDA error 702 on device 0: the launch timed out and was terminated
-> could not get memory info
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to deallocate pinned memory
CUDA error 702 on device 0: the launch timed out and was terminated
Attachments

[ Play Quicktime file ] crash octane.MOV [ 3.71 MiB | Viewed 1435 times ]

Last edited by coilbook on Tue Feb 19, 2019 4:06 am, edited 1 time in total.
coilbook
Licensed Customer
Licensed Customer
 
Posts: 2395
Joined: Mon Mar 24, 2014 2:27 pm
Next

Return to Development Build Releases


Who is online

Users browsing this forum: No registered users and 2 guests

Mon Sep 23, 2019 11:37 am [ UTC ]