OTOY Forums

I will post a fix for the OOC issues in the next 12 hours.

Thanks

Paul

face_off wrote:I will post a fix for the OOC issues in the next 12 hours.

Thanks

Paul

Thanks Paul.

I have updated the installers at the top of this thread with:

2020.1.0.52
- Fixed crash and OOC settings problems introduced in 2020.1.0.51

Thanks

Paul

face_off wrote:I have updated the installers at the top of this thread with:

2020.1.0.52
- Fixed crash and OOC settings problems introduced in 2020.1.0.51

Thanks

Paul

Hi Pail,

Downloaded and did a quick test. I am now able to use the OOC memory slider properly.

Initially I was getting a crash every time I clicked the Octane Viewport. Even with a simple scene of nothing else but just my character and hair. I deleted the Octane settings and the results were still the same.

To narrow down why it is crashing I did the following :
1. Tried a new scene. Loaded a character. Applied the same Kernel and Environment on the scene that was crashing. Clicked Octane Viewport - It rendered.
2. Applied custom skin materials to the character that was using on my character on the scene that was crashing. - It rendered.
3. Closed scene and open the existing scene that was crashing. Clicked Octane Viewport - It rendered.
4. Closed scene and Daz. Did not save the scene.
5. Opened Daz. Directly loaded the existing scene that was crashing. Clicked Octane Viewport - It rendered !

So looked like after the initial successful render, it now is rendering properly.

Out of core issue is still there.
1. Loaded a scene that needs OOC memory. Clicked Octane Viewport - It gave "No device pointer for out-of-core memory" / "Render engine failure". Same scene renders in the Stand Alone that I had reported in viewtopic.php?f=44&t=73445&start=90#p378313.
Can you please check ?

Regards,
Rajib

Update :
I tried to render after some time and faced the same immediate crash issue while clicking the Octane Viewport. I had closed Daz so had started Daz again. I did the same steps. Rendered something first on a new scene. Then without closing Daz loaded the scene that crashed and this time it rendered. So something is going wrong with the initial scene load if the Octane Viewport has not been opened at least once. Maybe something in the Octane data stored with the scene file or something not initialized if it encounters a scene with existing Octane data ? If one does a Show Hidden Nodes under the Daz Scene tab, I can see OctaneRender Scene Data node. Any issue with that ? Dose it get created every time fresh or does it load from the saved scene file ?

RTX ON is creating weird artifacts on the render.... I will post it on the Stand Alone thread.

1. Loaded a scene that needs OOC memory. Clicked Octane Viewport - It gave "No device pointer for out-of-core memory" / "Render engine failure". Same scene renders in the Stand Alone that I had reported in viewtopic.php?f=44&t=73445&start=90#p378313.

An Octane scene in DAZStudio is going to take a lot more RAM, since DAZStudio will be storing the scene in RAM, and the plugin will use memory to store the references between the DAZStudio element and the Octane nodes. I would suggest asking OTOY what the "No device pointer for out-of-core memory" error means (since I assume it's in the Octane Log and therefore coming from the Octane API).

If one does a Show Hidden Nodes under the Daz Scene tab, I can see OctaneRender Scene Data node. Any issue with that ?

Yes, that is the saved Octane data. It should convert an older version of the Octane data to the version the plugin has been compiled with. My guess is that it is loaded when the scene is loaded, rather than loaded when opening the Viewport.

Paul

face_off wrote: I would suggest asking OTOY what the "No device pointer for out-of-core memory" error means (since I assume it's in the Octane Log and therefore coming from the Octane API).
Paul

I have posted the issue in the RC2 thread. Will wait to see what they say.

I have updated the installers at the top of this thread with:

2020.1.0.53
- Compiled with Octane 2020.1 RC2

Paul

face_off wrote:I have updated the installers at the top of this thread with:

2020.1.0.53
- Compiled with Octane 2020.1 RC2

Paul

Thanks Paul. Will do some test.

Paul,

Why has the Smart Unfold been removed ??? Can you not disable features that we are so dependent on. Yes it is buggy but we still used it. Enable it back. it is not there even in the 2019.1.5.51. I can't roll back to 2020.1 earlier version. But at least managed to rollback back to 2109.1.5.49 to get it back.

Regards,
Rajib

face_off wrote:I have updated the installers at the top of this thread with:

2020.1.0.51
- Removed the setting of the Windows TDR Deley setting when the plugin starts up

Thanks

Paul

Hi Paul,

May I know if the code was commented out for the TDR Delay or some values reset to some defaults ? I have been experiencing VIDEO_TDR_DELAY BSOD (system crashes) since I had installed that release. I have never experienced that ever before. I have tried to re-install my graphics driver after running DDU driver removal in safe mode. But on and off am still facing it. I have not been able to go back to the earlier releases of 2020 as they give an error saying not supported during activation. I have finally uninstalled the 2020.x version. Also on the 2019.1.x side I have downgraded to before the TDR changes.

If you are doing some changes to the Windows registry, can you let us know what key and value is being / was changed / added / removed ? .

Regards,
Rajib