OctaneRender™ 2020.1 XB1 [superseded by 2020.1 XB2]

Forums: OctaneRender™ 2020.1 XB1 [superseded by 2020.1 XB2]
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.

Re: OctaneRender™ 2020.1 XB1

Postby jayroth » Tue Dec 17, 2019 9:43 pm

jayroth Tue Dec 17, 2019 9:43 pm
karu wrote:The current experimental build contains support for exporting renders in "ACES Image Container File Layout" format, which is an uncompressed 16-bit EXR file in the ACES2065-1 color space with some additional metadata. There is currently no support for any other ACES color spaces such as ACEScg, or ACES textures, or ACES interactive preview. It is likely all of these will be made available as a result of further color management work coming in a future 2020.1 experimental build - watch this space.

This strikes me as odd, considering that ACEScg was designed specifically for computer rendered images, whereas all of the other specs were intended as a translation for live action footage. What drove that decision?
CaseLabs Mercury S8 / ASUS Z10PE-D8 WS / Crucial 64GB 2133 DDR4 / 2 XEON E5-2687W v3 3.1 GHz / EVGA 1600 P2 / 2 EVGA RTX 2080Ti FTW3 Hybrid/ Cinema 4D

Is it fast? Oh, yeah!
User avatar
jayroth
Licensed Customer
Licensed Customer
 
Posts: 393
Joined: Fri May 28, 2010 7:29 pm
Location: Orange County, CA, USA

Re: OctaneRender™ 2020.1 XB1

Postby karu » Tue Dec 17, 2019 11:01 pm

karu Tue Dec 17, 2019 11:01 pm
jayroth wrote:
karu wrote:The current experimental build contains support for exporting renders in "ACES Image Container File Layout" format, which is an uncompressed 16-bit EXR file in the ACES2065-1 color space with some additional metadata. There is currently no support for any other ACES color spaces such as ACEScg, or ACES textures, or ACES interactive preview. It is likely all of these will be made available as a result of further color management work coming in a future 2020.1 experimental build - watch this space.

This strikes me as odd, considering that ACEScg was designed specifically for computer rendered images, whereas all of the other specs were intended as a translation for live action footage. What drove that decision?


The ACES Image Container File Layout format is a standardized format (SMPTE ST 2065-4), and it requires ACES2065-1, which is nominally "the" ACES color space for storage and interchange (see https://acescentral.com/t/acescc-vs-acescct/485/6). We chose to implement the standardized format first. This format places specific restrictions on the data (e.g. must be 16-bit EXR) in addition to the color space, and also adds additional metadata so a file can specify that it conforms to the standard. That's why the current option in OctaneRender is simply called "EXR (ACES)" and doesn't give you any choice about color space, bit depth, compression etc.

It appears that the standardized format isn't actually used as widely as some alternatives such as using the ACEScg color space (if I wasn't very new to ACES myself, I might have known this at the time :)). We plan to support arbitrary color spaces (e.g. ACEScg) for all exports (e.g. 32-bit EXR) in the future (images exported in this way will not include the ACES metadata because they aren't "ACES files" as per SMPTE ST 2065-4).

My understanding is that ACEScg was designed to be used internally in RGB-based rendering/compositing to produce more reasonable results when multiplying RGB colors together. This is something OctaneRender doesn't do because it is a spectral renderer, but I can see that ACEScg export will be very useful for workflows that do this.
karu
OctaneRender Team
OctaneRender Team
 
Posts: 77
Joined: Sun Oct 13, 2019 11:26 pm

Re: OctaneRender™ 2020.1 XB1

Postby jayroth » Tue Dec 17, 2019 11:47 pm

jayroth Tue Dec 17, 2019 11:47 pm
Thanks for the explanation, I appreciate it. Interesting bit about Octane being a spectral render, and this not necessarily benefitting from ACEScg due to its RGB-centric design intent.
CaseLabs Mercury S8 / ASUS Z10PE-D8 WS / Crucial 64GB 2133 DDR4 / 2 XEON E5-2687W v3 3.1 GHz / EVGA 1600 P2 / 2 EVGA RTX 2080Ti FTW3 Hybrid/ Cinema 4D

Is it fast? Oh, yeah!
User avatar
jayroth
Licensed Customer
Licensed Customer
 
Posts: 393
Joined: Fri May 28, 2010 7:29 pm
Location: Orange County, CA, USA

Re: OctaneRender™ 2020.1 XB1

Postby mojave » Wed Dec 18, 2019 12:14 am

mojave Wed Dec 18, 2019 12:14 am
funk wrote:I just posted this bug in the 2019.1.4 thread, but it also affects 2020.1 XB1

viewtopic.php?p=374501#p374501 (see post for OCS file)

Layered materials dont seem to work correctly if you have a layer, and the BASE MATERIAL pin comes from a MIX or COMPOSITE material

layered_material_bug.png



funk wrote:Plugging a noise texture into the dirt radius crashes Octane

dirt_radius_texture_crash.png



Hi,

These issues have both been fixed in version 2019 meaning this will be also available for 2020 in the next build.

viewtopic.php?f=24&t=73140&p=374593#p374593

viewtopic.php?p=373566#p373566
User avatar
mojave
OctaneRender Team
OctaneRender Team
 
Posts: 1131
Joined: Sun Feb 08, 2015 10:35 pm

Re: OctaneRender™ 2020.1 XB1

Postby wallace » Wed Dec 18, 2019 1:34 am

wallace Wed Dec 18, 2019 1:34 am
TRRazor wrote:There seems to be a problem with alpha-mapped objects casting shadows onto random walk sss-enabled geometry.
The shadow in this scene shouldn't be visible, since that part of the alpha map (read: the haircap) is transparent. Yet, it is casting a shadow.


Hi TRRazor,

Do you have a scene you can share for reproducing the problem?

Thanks.
User avatar
wallace
OctaneRender Team
OctaneRender Team
 
Posts: 133
Joined: Sun Dec 18, 2016 10:38 pm

Re: OctaneRender™ 2020.1 XB1

Postby mojave » Wed Dec 18, 2019 2:06 am

mojave Wed Dec 18, 2019 2:06 am
Lewis wrote:Hi Again,

I think i found some bug in rendering material with RTX ON.

Here is the simple scene of armchair in simple room. Test with RTX OFF show All good, and with RTX ON my Velvet Fabric is rendered wrong (looks like inverted mix material or so?).
But what is weird here is that IF i put this Armchair outside of the room (just at plain sun) then it's rendering fine with RTX ON also, so it might be some weird combo with windows glass (Fake shadow) + RTX ON and some material settings.

I hope DEVs can find way to debug it properly form this scene, I simplified it as much as possible.

Thanks

attaching image and ORBX


Hi Lewis,

Thank you for reporting this. This will be fixed in the next release.
User avatar
mojave
OctaneRender Team
OctaneRender Team
 
Posts: 1131
Joined: Sun Feb 08, 2015 10:35 pm

Re: OctaneRender™ 2020.1 XB1

Postby funk » Wed Dec 18, 2019 3:39 am

funk Wed Dec 18, 2019 3:39 am
mojave wrote:
funk wrote:I just posted this bug in the 2019.1.4 thread, but it also affects 2020.1 XB1

viewtopic.php?p=374501#p374501 (see post for OCS file)

Layered materials dont seem to work correctly if you have a layer, and the BASE MATERIAL pin comes from a MIX or COMPOSITE material

layered_material_bug.png



funk wrote:Plugging a noise texture into the dirt radius crashes Octane

dirt_radius_texture_crash.png



Hi,

These issues have both been fixed in version 2019 meaning this will be also available for 2020 in the next build.

viewtopic.php?f=24&t=73140&p=374593#p374593

viewtopic.php?p=373566#p373566


Thanks mojave.

You actually quoted a dirt radius crash (which is new to 2020 since we cant use textures in earlier versions), but you have linked to another dirt bug which affected 2019.

I just want to be sure you are aware, and hope the dirt crash will be fixed in 2020.
Win10 Pro 64 / Core i7-975 3.33GHz / 12GB RAM / GTX 1080 Ti + GTX 670 / 2x1920x1200 / MODO 14
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
User avatar
funk
Licensed Customer
Licensed Customer
 
Posts: 904
Joined: Mon Feb 07, 2011 1:24 pm
Location: Australia

Re: OctaneRender™ 2020.1 XB1

Postby Lewis » Wed Dec 18, 2019 9:39 am

Lewis Wed Dec 18, 2019 9:39 am
mojave wrote:Hi Lewis,

Thank you for reporting this. This will be fixed in the next release.


Great to hear, I've run into few more of those with mix material/dirt node so they are probably all part of same issue, looking forward to next release thanks :).
--
Lewis
http://www.ram-studio.hr
Skype - lewis3d
ICQ - 7128177

WS Dual Xeon E5-2698v4, 128GB RAM, Win10, 4 * RTX 2080Ti
RS1 i7 9800X, 64GB RAM, Win10, 3 * GTX 1080Ti
RS2 i7 6850K, 64GB RAM, Win10, 3 * GTX 1080Ti
User avatar
Lewis
Licensed Customer
Licensed Customer
 
Posts: 942
Joined: Tue Feb 05, 2013 6:30 pm
Location: Croatia

Re: OctaneRender™ 2020.1 XB1

Postby andrey.krivulya » Wed Dec 18, 2019 1:35 pm

andrey.krivulya Wed Dec 18, 2019 1:35 pm
Very strange result on this scene.

scene_for_rtx.jpg


scene_for_rtx_2.jpg


2*2080Ti (NVLink)

Scene - > http://bit.ly/34CjKPn
win 10 /64x Intel Core i9-9900K - 2xGeForce 2080Ti (NVLink)

My youtube channel with 3d tutorials ----- >>>> https://www.youtube.com/c/AndrewKrivulya
User avatar
andrey.krivulya
 
Posts: 92
Joined: Wed Apr 06, 2016 6:15 pm

Re: OctaneRender™ 2020.1 XB1

Postby beenout » Wed Dec 18, 2019 1:41 pm

beenout Wed Dec 18, 2019 1:41 pm
I have a RTX 2080 super and the Rtx acceleration is useless (same render time OFF/ON)

Image
beenout
 
Posts: 1
Joined: Fri May 11, 2018 8:09 pm
PreviousNext

Return to Development Build Releases


Who is online

Users browsing this forum: No registered users and 1 guest

Sun Sep 27, 2020 7:07 am [ UTC ]