OctaneRender™ 2020.1 XB3 [superseded by 2020.1 RC1]

[ff7darkcloud]

Hello, I am not sure if this is the way it is intended to work but when I enable my render layers, the denoised image is missing environment backplate. Is there a work around for this?

Thanks!

[Hesekiel2517]

Ich rendered some high resolution images and noticed that there is a little shifted pixels in some Areas. This should be a straight line but it looks like some parts are moved.

[enricocerica]

Ich rendered some high resolution images and noticed that there is a little shifted pixels in some Areas. This should be a straight line but it looks like some parts are moved.

Bildschirmfoto 2020-02-05 um 11.14.39.png

Stupid question but hey
Is the view port set to display the image at 100%, I noticed this effect when my image is reduced ...

[Hesekiel2517]

Not stupid at all But it's the final image in Photoshop

[mojave]

Ich rendered some high resolution images and noticed that there is a little shifted pixels in some Areas. This should be a straight line but it looks like some parts are moved.

Bildschirmfoto 2020-02-05 um 11.14.39.png

Would you mind sharing an ORBX scene so we can look into what's causing this?

[mojave]

Hi,
Just noticed that after using the refresh scatters script, I cannot start any render anymore, no error but when selecting a render target or use the restart current render button, nothing happens.

Well, apparently nothing to do with the refresh scatter script. It occurs randomly, at least as I may observe. At one moment, for instance if I add a mesh, or I connect a mesh to the render target I not able anymore to start a rendering. I should stop and restart Octane.
Any idea how to avoid this ?
Thanks

Edit : I have exactly the same issue with the 2019.1.5 version ...

Edit : Ok, did some more scene analysis and finally discovered that the problem seems to come from an instantiated object. I have a grass scattering with about 2.500.000 instances. If I remove it from the scene, the problem does not occur. As soon as I add it again, the UI doesn't respond anymore. The rendering seems to continue where it freezes but the UI is not updated and I couldn't do anything else then restart Octane. I tried to reduce the amount of instances to 1.700.000 and got the same issue and again after reducing to 1.000.000.

If I understand correctly the issue is that it takes a relatively long time to update the scene during which the UI does not respond, is that correct? Can you confirm also this is using standalone?

[enricocerica]

Hi,
Just noticed that after using the refresh scatters script, I cannot start any render anymore, no error but when selecting a render target or use the restart current render button, nothing happens.

Well, apparently nothing to do with the refresh scatter script. It occurs randomly, at least as I may observe. At one moment, for instance if I add a mesh, or I connect a mesh to the render target I not able anymore to start a rendering. I should stop and restart Octane.
Any idea how to avoid this ?
Thanks

Edit : I have exactly the same issue with the 2019.1.5 version ...

Edit : Ok, did some more scene analysis and finally discovered that the problem seems to come from an instantiated object. I have a grass scattering with about 2.500.000 instances. If I remove it from the scene, the problem does not occur. As soon as I add it again, the UI doesn't respond anymore. The rendering seems to continue where it freezes but the UI is not updated and I couldn't do anything else then restart Octane. I tried to reduce the amount of instances to 1.700.000 and got the same issue and again after reducing to 1.000.000.

If I understand correctly the issue is that it takes a relatively long time to update the scene during which the UI does not respond, is that correct? Can you confirm also this is using standalone?

As explained later on, it finally has nothing to do with the scatter script.
The problem seems to be linked with my grass which is about 2.5 million instances. If I render the scene with the grass and I make a change, let's say changing a material or reloading a mesh of the scene while it is rendering with the grass, I cannot do anything else, I cannot move the camera anymore (no effect), I cannot render another render target, I can select it but without any effect, I cannot select a material over the image, ... the render seems to continue rendering the same render target and the only way to get back the control is to restart Octane. If I disconnect the grass node in my scene, I do not meet the problem, at least I couldn't reproduce it. The issue occurs with 2019 version as well as with 2020.

[BorisGoreta]

Is it a known issue that nodes are giving different results when using dirt node compared to local GPUs, where you get the left part of the image slightly darker then the right side ?

[mojave]

Is it a known issue that nodes are giving different results when using dirt node compared to local GPUs, where you get the left part of the image slightly darker then the right side ?

If you are using network rendering this could be the cause of RTX being enabled by default in render slaves and dirt not being supported with RTX accelerated geometry. In this case dirt will be evaluated as a black texture and could be producing the results you report. This will be addressed in the next release.

[mojave]

As explained later on, it finally has nothing to do with the scatter script.
The problem seems to be linked with my grass which is about 2.5 million instances. If I render the scene with the grass and I make a change, let's say changing a material or reloading a mesh of the scene while it is rendering with the grass, I cannot do anything else, I cannot move the camera anymore (no effect), I cannot render another render target, I can select it but without any effect, I cannot select a material over the image, ... the render seems to continue rendering the same render target and the only way to get back the control is to restart Octane. If I disconnect the grass node in my scene, I do not meet the problem, at least I couldn't reproduce it. The issue occurs with 2019 version as well as with 2020.

Is there any chance you can share a repro scene so we can look into this?