OctaneRender™ 2020.1 RC2 [superseded by 2020.1 RC3]

Wed Mar 11, 2020 9:45 pm

Thanks mojave

Thu Mar 12, 2020 1:21 am

Network rendering from a windows system to a linux system does not work for this version or RC1, I get error 700 illegal access. Tried from Houdini as well as standalone with an ORBx. orbx file I'm rendering is linked below.

Works fine on both systems in both standalone and houdini though, just not via network rendering.

https://www.dropbox.com/s/dx3xjnwayymqa ... .orbx?dl=0

Thu Mar 12, 2020 1:30 am

ptunstall wrote:Network rendering from a windows system to a linux system does not work for this version or RC1, I get error 700 illegal access. Tried from Houdini as well as standalone with an ORBx. orbx file I'm rendering is linked below.

Works fine on both systems in both standalone and houdini though, just not via network rendering.

https://www.dropbox.com/s/dx3xjnwayymqa ... .orbx?dl=0

Thank you for the report, we will look into this.

Thu Mar 12, 2020 4:40 am

network rendering still fails which will kill the master session, same situation as in 2020.1.RC1,
viewtopic.php?f=33&t=73978&start=40

Fri Mar 13, 2020 2:49 am

mojave wrote:
rajib wrote:Hi Otoy Support / Dev Team,

Seams still appearing at the UV edge in SSS / main render pass.
We are aware of this and is on top of our priority list, it just didn't make the cut for this release.

Happy to hear that

.

I would like to highlight another issue. This is related to the OOC Memory issue that I have reported I had been facing. As of the RC1 I was finally able to render the scene that need OOC Memory in the standalone but it continues to fail to render in the Daz Studio Plugin. According to the developer, Paul, the error is coming from the Octane SDK and he does not know what is the issue. I can see "Failed to allocate page locked memory. Error 2", "No device pointer for out-of-core memory" / "Render engine failure" messages when I try to render the scene in the plugin that now finally renders in the standalone. Maybe there is an issue in the Octane SDK being used in the plugin ? Or maybe some required parameter is not set by the plugin ? Could someone please work with Paul to fix this issue. If you need someone to alpha / beta test the fix for this issue, just message me. I am more than happy to help test the fix for this issue and provide feedback.

: Daz Plugin Memory Usage and Log

Regards,
Rajib

Fri Mar 13, 2020 3:11 am

rajib wrote: I would like to highlight another issue. This is related to the OOC Memory issue that I have reported I had been facing. As of the RC1 I was finally able to render the scene that need OOC Memory in the standalone but it continues to fail to render in the Daz Studio Plugin. According to the developer, Paul, the error is coming from the Octane SDK and he does not know what is the issue. I can see "No device pointer for out-of-core memory" / "Render engine failure" messages when I try to render the scene in the plugin that now finally renders in the standalone. Maybe there is an issue in the Octane SDK being used in the plugin ? Or maybe some required parameter is not set by the plugin ? Could someone please work with Paul to fix this issue. If you need someone to alpha / beta test the fix for this issue, just message me. I am more than happy to help test the fix for this issue and provide feedback.

There is a known issue using OOC and RTX, could you please check if the same setup works just by disabling it?

Fri Mar 13, 2020 3:21 am

mojave wrote:
rajib wrote: I would like to highlight another issue. This is related to the OOC Memory issue that I have reported I had been facing. As of the RC1 I was finally able to render the scene that need OOC Memory in the standalone but it continues to fail to render in the Daz Studio Plugin. According to the developer, Paul, the error is coming from the Octane SDK and he does not know what is the issue. I can see "No device pointer for out-of-core memory" / "Render engine failure" messages when I try to render the scene in the plugin that now finally renders in the standalone. Maybe there is an issue in the Octane SDK being used in the plugin ? Or maybe some required parameter is not set by the plugin ? Could someone please work with Paul to fix this issue. If you need someone to alpha / beta test the fix for this issue, just message me. I am more than happy to help test the fix for this issue and provide feedback.
There is a known issue using OOC and RTX, could you please check if the same setup works just by disabling it?

Thanks Mojave for the quick response. I will try without RTX and report back.

Fri Mar 13, 2020 3:54 am

rajib wrote:
mojave wrote:
rajib wrote: I would like to highlight another issue. This is related to the OOC Memory issue that I have reported I had been facing. As of the RC1 I was finally able to render the scene that need OOC Memory in the standalone but it continues to fail to render in the Daz Studio Plugin. According to the developer, Paul, the error is coming from the Octane SDK and he does not know what is the issue. I can see "No device pointer for out-of-core memory" / "Render engine failure" messages when I try to render the scene in the plugin that now finally renders in the standalone. Maybe there is an issue in the Octane SDK being used in the plugin ? Or maybe some required parameter is not set by the plugin ? Could someone please work with Paul to fix this issue. If you need someone to alpha / beta test the fix for this issue, just message me. I am more than happy to help test the fix for this issue and provide feedback.
There is a known issue using OOC and RTX, could you please check if the same setup works just by disabling it?
Thanks Mojave for the quick response. I will try without RTX and report back.

Hi Mojave,

Unfortunately even with RTX OFF, I am still getting the same errors "Failed to allocate page locked memory. Error 2","No device pointer for out-of-core memory", "Render engine failure" in the Daz plugin.

: RTX OFF, Same OOC error.

Regards,
Rajib

Fri Mar 13, 2020 4:17 am

rajib wrote: Unfortunately even with RTX OFF, I am still getting the same errors "Failed to allocate page locked memory. Error 2","No device pointer for out-of-core memory", "Render engine failure" in the Daz plugin.

The error that you see Failed to allocate page-locked memory: error 2 happens in the case that Octane is not able to get the required memory that you scene needs to be setup. To confirm this you could check your RAM usage using the Windows task manager while the scene is loading, if your system runs out of RAM right before you get this error, this would be the reason for it.

Fri Mar 13, 2020 7:04 am

As you can see in the attached screenshot my system still has 66 GB of RAM still available when the error occurs (I have 128GB of RAM installed in my system). So that should not be the issue. Is there any way to check how much memory is being allocated ? Can it be more than 66GB even though the OOC memory is set to around 30+GB ? Can the memory being allocated be logged so that it can give a clearer picture.

: OOC Error, RTX OFF, System Memory usage

Like I have mentioned same scene I can render in the standalone. So the standalone is definitely able to allocate the required memory needed for the scene. If you look at the screen shot "System Memory Usage" it shows clearly that there is enough memory available and also the OOC used / reserved shows 20+ GB still available.