Community Forums for OTOY Customers
https://render.otoy.com/forum/
OK, thanks. For testing, may I suggest recording your OutOfCore settings, and also have Windows Task Manager open to monitor your memory. It would be good to see if the crash occurs when you have a lot of free VRAM and system RAM available, and if it only happens if OutOfCore is enabled or disabled.At the time I was using Texture Shaded view with cameras switched in between with Perspective.
I have attached that portion of the log.face_off wrote:Can you post the specific Octane Log when this happens please?However, after using this work around, and avoiding the crash, I have also started seeing CUDA 700 errors randomly occurring, requiring me to restart DAZ.
Paul
OoC settings I have set at 28928MB out of 64GB I have. Kind of overkill, but I'm curious about the scenes that exceed measly 8GB VRAM Nvidia puts in, well, high end cards after all. But that scene wasn't exceeding the VRAM capacity, it was about 75% full at the time. Example on the config/status screenshots has a bit lighter mesh, but still quite a bit of data. DAZ updated the beta to 4.12.1.117 in the meantime, and these screens come from it.face_off wrote:OK, thanks. For testing, may I suggest recording your OutOfCore settings, and also have Windows Task Manager open to monitor your memory. It would be good to see if the crash occurs when you have a lot of free VRAM and system RAM available, and if it only happens if OutOfCore is enabled or disabled.At the time I was using Texture Shaded view with cameras switched in between with Perspective.
Paul
I suggest reducing this, or turning it off, to see if it resolves your crashes.OoC settings I have set at 28928MB out of 64GB I have.
Thanks Paul. Just to let you know the problem with all version of the 2020 Beta and RC that leads to instant crash on render start of old scene is still there in the final release. The workaround of rendering something first - a cube / plane etc and then loading the old scene and render works. But please fix this.face_off wrote:I have updated the installers at the top of this thread with:
2020.1.0.55
- Compiled with Octane 2020.1
Paul
Code: Select all
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\octane.dll" at 0033:000000004D52C740, Octane::isGreyscalePass()+5684448 byte(s)
I had forgotten about this, but the crash situation still happens with a small number of my Daz scenes made in 2018.SiliconAya wrote:I have another scene the causes more or less the same crash.
The same workaround of opening the viewport before loading the scene still works.Code: Select all
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\octane.dll" at 0033:000000004D52C740, Octane::isGreyscalePass()+5684448 byte(s)
I've got this CUDA 700 error just at the end of preview render (three primitive cubes with some snake-skin textures, 200 samples left out of 1000, path tracing, 1400x1500 res) on RTX 2080, Win 7 x64, 445.87 driver, when I enabled AI upsampling as "Upsampler mode 2x2" from the droplist. Rendering never ended and the whole plugin just hung, when I invoked "Rebuild scene", and Daz Studio with it. All this on "they-made-it-stable-in-the-meantime" DS 4.12.1.117.rajib wrote:Thanks Paul. Just to let you know the problem with all version of the 2020 Beta and RC that leads to instant crash on render start of old scene is still there in the final release. The workaround of rendering something first - a cube / plane etc and then loading the old scene and render works. But please fix this.face_off wrote:I have updated the installers at the top of this thread with:
2020.1.0.55
- Compiled with Octane 2020.1
Paul
I also was plagued with the CUDA 700 errors recently with the 2080 Ti RTX but interestingly ever since I started using the Titan RTX I don't get them anymore. I guess it is tied to the OOC memory usage that generates the CUDA errors. With the Titan RTX I never get into the OOC memory because of it's 24GB video ram, so no errors.
Update:
I also don't see the smart unfold. Please enable it. Staying silent even and not enabling even after multiple request have been made is not appreciated.
Update 2 :
Spoke too soon on the CUDA error. Got my first CUDA 700 error whlie using the Titan RTX. It happened during modification of scene object while rendering was going on. I guess it causes some pointer issues. Anyway, now I tend to pause render before I make changes to the scene.
Code: Select all
18:40:59.978: +++++ Plugin running.
19:23:38.976: Up-sampling error: CUDA_ERROR_LAUNCH_FAILED: unspecified launch failure
19:23:38.977: CUDA error 719 on device 0: unspecified launch failure
19:23:38.977: -> failed to copy pitched memory from device
19:23:38.977: Render engine failure occured! (WARNING)