face_off wrote:I have updated the installers at the top of this thread with:
- Compiled with Octane 2020.1
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.
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.
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.
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 188.8.131.52.
I have the feeling Nvidia broke something in the almost whole 442-445 driver lineup, when it comes to Optix/neuray/whatnot, cause even their Iray 2019 was falling back to CPU in the Daz Studio betas, that used such Iray. All cause of sudden "memory allocation errors" in the Daz log during switching textures/shaders/material properties in the scene and using Iray preview at the same time. Daz guys fixed some of these bugs, and the program fell back to CPU mode less frequently, but it's unclear, how much they had to improvise to get around it. Maybe something in the drivers also bugs Octane as well?
I could back then (and still can) game on my card with full VRAM filled up with textures, so the card's memory chips aren't at fault, I think.
- 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)