OctaneRender™ 2020.1 XB1 [superseded by 2020.1 XB2] Tweet

[karl]

Is the standalone version the only one available or are the plugin modules linked anywhere?
I assumed the C4D plugin would be available since the press release makes a point of noise shader functionality.

Thanks

Please see this thread for the C4D plugin: https://render.otoy.com/forum/viewtopic.php?f=85&t=73352

[karl]

Question ...

Does NVlink work with 4 cards? Meaning a pool of 2 x 2 with total 22GB memory avaiable?

Can anybody confirm?

I can confirm that NVlink memory pooling doesn't work even for one pair at the moment. It probably works only for Quadro and Titan RTX. It doesn't work for any other Geforce card including 2080Ti.

If your scene extend memory of one card and you have disabled Out Of Core - Octane render will fail with out of memory error.

We have identified the cause of this issue and are working towards a fix. It should be available in a future build of 2020.1 (likely not XB2 though), and a future build of 2019.1.

Regarding 4 cards, currently we only support memory pooling with pairs of cards (but you can have multiple pairs). So you could pool memory between cards 1 & 2 and between cards 3 & 4, but you can't have a single pool with cards 1, 2, 3 & 4 all together.

[SSmolak]

Question ...

Does NVlink work with 4 cards? Meaning a pool of 2 x 2 with total 22GB memory avaiable?

Can anybody confirm?

I can confirm that NVlink memory pooling doesn't work even for one pair at the moment. It probably works only for Quadro and Titan RTX. It doesn't work for any other Geforce card including 2080Ti.

If your scene extend memory of one card and you have disabled Out Of Core - Octane render will fail with out of memory error.

We have identified the cause of this issue and are working towards a fix. It should be available in a future build of 2020.1 (likely not XB2 though), and a future build of 2019.1.

Thank you for information. There are many misleading informations especially on Nvidia forum where some people say that NVlink memory pooling is reserved for Quadro and Titan RTX and it will not be supported anymore in drivers.

[rajib]

Hello Otoy Team,

I have an issue with an invisible geometry casting shadow on SSS material which I posted under 2019.1.5. Same issue can be recreated with the 2020.1 XB1. Please take a look at viewtopic.php?f=24&t=73537. Hope it can be fixed. I have included a test scene in that post.

Regards,
Rajib

[OneManVN]

Question ...

Does NVlink work with 4 cards? Meaning a pool of 2 x 2 with total 22GB memory avaiable?

Can anybody confirm?

I can confirm that NVlink memory pooling doesn't work even for one pair at the moment. It probably works only for Quadro and Titan RTX. It doesn't work for any other Geforce card including 2080Ti.

If your scene extend the memory of one card and you have disabled Out Of Core - Octane render will fail with out of memory error.

We have identified the cause of this issue and are working towards a fix. It should be available in a future build of 2020.1 (likely not XB2 though), and a future build of 2019.1.

Regarding 4 cards, currently, we only support memory pooling with pairs of cards (but you can have multiple pairs). So you could pool memory between cards 1 & 2 and between cards 3 & 4, but you can't have a single pool with cards 1, 2, 3 & 4 all together.

I'm glad to hear that, hopefully sometime soon, would be nice. I was told NVLink was a thing for "Enterprise only" So, of course, I went and got a yearly subscription for it, only to find out it still doesn't work.

[SSmolak]

I'm glad to hear that, hopefully sometime soon, would be nice. I was told NVLink was a thing for "Enterprise only" So, of course, I went and got a yearly subscription for it, only to find out it still doesn't work.

It's crucial for me too and for everyone making ArchViz scenes.

[rajib]

Hello Otoy Team,

Can we have an Opacity pin for the hair material so that it can also be used with non strand alpha mask based hair ? Or am I missing something ?

Regards,
Rajib

[nejck]

I'm glad to hear that, hopefully sometime soon, would be nice. I was told NVLink was a thing for "Enterprise only" So, of course, I went and got a yearly subscription for it, only to find out it still doesn't work.

It's crucial for me too and for everyone making ArchViz scenes.

+1 from me on this one ) Really liking 2020 so far though!

[TRRazor]

Hi,

thanks for getting back with me so quickly.

That absolutely did it. I'm usually using coherence values around 0.35, since that was significantly speeding up render speeds before RTX acceleration came around.
I just set it to 0 and wasn't able to reproduce the problem. Same result with my original scene, the opacity now renders 100% transparent, instead of leaving those nasty shadows / lines.
Does that mean, however, that when using RTX, one can't use coherence?

I was using the following values in my scene (according to your questions):
1.) coherence value of 0.35
2.) 5000
3.) As mentioned above, it fixed it.

Thanks again!

Hi,

It's not coherence ratio + RTX acceleration that is causing this issue, but the combination of coherence ratio + opacity is the main cause.

This is because the random numbers are more likely to fall within the same range, so the subsequent random numbers used for surface scattering and medium scattering are inherently different for surface area on the sphere that is being occluded by the transparent torus vs the non occluded area.

This just means that you will need more samples for that difference to go away, generally the guide line is that the higher coherent ratio you use, the less variance you will have on your image, but the required sample count is also higher for you to converge to the correct image.

Thanks,
Wallace

While I was able to fix the issue in the sample scene. The same problem occured in another scene, where the coherent ratio is set to "0", so no coherent ratio at all.
Yet, the eyelashes are being rendering with a shadow, where there should be none. Please see the screenshot attached.

PS: rajib's problem, four posts above mine, is pointing towards the exact same issue. There definitely seems to be something wrong within the rendering of opacity within materials with mediums.

[mojave]

Very strange result on this scene.

scene_for_rtx.jpg

scene_for_rtx_2.jpg

2*2080Ti (NVLink)

Scene - > http://bit.ly/34CjKPn

Hi @andrey.krivulya

Your issue has been fixed. Unfortunately it didn't make it into 2020.1 XB2 but it will be included in the next build.

For now just so you are aware this was an issue related to autofocus, so disabling it from your scene should not fix it completely but mitigate it significantly.

Thank you.