Page 14 of 29
Re: OctaneRender 2020 for DAZ Studio [TEST and STABLE]
Posted: Sun Apr 19, 2020 11:40 pm
by face_off
I noticed something weird with emissive material. Preview render shows bright light, and final render - totally no light at all... I used pathtracing. I also used that kind of emissive material. By the way, wattage if that light seems way out of range, in the preview this is about 6W bulb. But even 100W emission won't show anything on final render.
Please see Solution 10) at the top of this thread.
Second thing is the weird camera resolution behavior - where did Octane plugin get this 4 x 4 pixels resolution from? It's really hard to workaround (playing around with every parameter I outlined on screenshot), and it's usually coming back after a while, like just now...
Resolution problem seems to apply only to preview rendering, final rendering seems to take one of these camera parameters and use it. It seems to happen, when there's either camera with its own resolution, or because I first remade a couple of shaders in a scene (emissive surfaces aren't converted from Iray at all and there's still glass-water-like conversion issues, so that needed to be fixed by hand) and after that I pressed "Open viewport" button.
I'm sorry, but I have not seen this problem before, and had no other reports of it. I would suggest trying Solution 3) at the top of this thread.
Thanks
Paul
Re: OctaneRender 2020 for DAZ Studio [TEST and STABLE]
Posted: Mon Apr 20, 2020 12:10 am
by mikmod
Thank you, Paul! Indeed, disabling combined mesh helps!
I'll observe, if 4x4 bug appears again after deleting the config file. BTW, it's on the latest DAZ beta 4.12.1.109. Is there a chance for OptiX denoiser to be implemented in Octane, like it's done in latest Blender E-Cycles 2.82 and 2.83? The speedup and results are amazing! It's like your Brigade, at least that fast.
Re: OctaneRender 2020 for DAZ Studio [TEST and STABLE]
Posted: Mon Apr 20, 2020 8:47 am
by Witpapier
Hi Paul, I have this issue where a custom morph will make my character disappear. as I move the slider to apply the morph the character becomes transparent. does not happen with all morphs. No Idea what causes this. works fine in Daz Iray.
Re: OctaneRender 2020 for DAZ Studio [TEST and STABLE]
Posted: Mon Apr 20, 2020 9:09 am
by face_off
Witpapier wrote:Hi Paul, I have this issue where a custom morph will make my character disappear. as I move the slider to apply the morph the character becomes transparent. does not happen with all morphs. No Idea what causes this. works fine in Daz Iray.
I have heard of this happening before, and it was associated with a parenting issue (I think previously it was a prop parented to the eye's?). Hopefully that gives you a direction to pursue. Please let me know if you work out the cause.
Paul
Re: OctaneRender 2020 for DAZ Studio [TEST and STABLE]
Posted: Mon Apr 20, 2020 4:04 pm
by Kanne
face_off wrote:2020-04-18 11:31:42.782 11856 b2020.1.0.53 CUDA error 2 on device 1: out of memory
Looks like you are running out of VRAM.
2020-04-18 11:06:26.174 8276 b2020.1.0.53 Tried to access pin via an invalid ID P_FILM_SETTINGS (311)
This looks like an error associated with opening a very old scene - was that the case?
Paul
It's the same scene/character when i started with Octane 4.02.xx. I allways drag this file with me from each version of octane to the next.
The scene isnt complex. One character and a background plane.
I get a lot of different Cuda 700 errors recently. Interior scene and i only adjustet the position of a light while viewport is open:
Code: Select all
17:42:43.625: +++++ Plugin running.
17:57:48.369: CUDA error 700 on device 0: an illegal memory access was encountered
17:57:48.369: -> failed to copy memory to device.
17:57:48.369: device 0: failed to upload data texture 3 '0:__data4__'
17:57:48.369: CUDA error 700 on device 1: an illegal memory access was encountered
17:57:48.369: CUDA error 700 on device 0: an illegal memory access was encountered
17:57:48.371: -> failed to destroy texture objects
17:57:48.373: -> kernel execution failed(kernel46)
17:57:48.378: CUDA error 700 on device 0: an illegal memory access was encountered
17:57:48.378: Render engine failure occured! (WARNING)
17:57:48.399: -> failed to deallocate device memory
17:57:48.399: CUDA error 700 on device 0: an illegal memory access was encountered
17:57:48.399: -> could not get memory info
17:57:51.380: Render engine failure occured! (WARNING)
Re: OctaneRender 2020 for DAZ Studio [TEST and STABLE]
Posted: Mon Apr 20, 2020 11:03 pm
by face_off
I get a lot of different Cuda 700 errors recently. Interior scene and i only adjustet the position of a light while viewport is open:
Do you have the latest Nvidia drivers installed?
Paul
Re: OctaneRender 2020 for DAZ Studio [TEST and STABLE]
Posted: Tue Apr 21, 2020 8:42 am
by Kanne
face_off wrote:I get a lot of different Cuda 700 errors recently. Interior scene and i only adjustet the position of a light while viewport is open:
Do you have the latest Nvidia drivers installed?
Paul
Yes, i do. Tried with GRD and SD.
Re: OctaneRender 2020 for DAZ Studio [TEST and STABLE]
Posted: Tue Apr 21, 2020 10:43 am
by face_off
Yes, i do. Tried with GRD and SD.
OK, I suggest you report these CUDA error messages in the Octane Standalone 2020.1 release thread.
Paul
Re: OctaneRender 2020 for DAZ Studio [TEST and STABLE]
Posted: Mon Apr 27, 2020 7:17 am
by rajib
Hi Paul,
When will we get the RC4 build ? Also, if you have not re-enabled the Smart Unfold in the NGE already, please do so in the RC4 release. It is something that I and probably many others depend on on a day to day basis. Without that copy / pasting materials and then editing them is a serious pain.
Regards,
Rajib
Re: OctaneRender 2020 for DAZ Studio [TEST and STABLE]
Posted: Mon Apr 27, 2020 8:05 am
by SiliconAya
I've had a few Cuda 700 errors in the last few days as well after upgrading to 2020.1.0.54.
At the moment however, I have a scene I was working on yesterday, that now crashes DazStudio when I open the OctaneRender viewport after loading the scene.
It seems to always crash with the bellow reason.
Code: Select all
Exception Reason:
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\octane.dll" at 0033:00000000869CAF00, Octane::isGreyscalePass()+5682624 byte(s)
The only thing different about this scene is that I used a defuse emission material on some instances of a sphere for candle flames. However deleting the instances, the original sphere and material doesn't stop the crash, so I don't know if that's related.
A workaround I've found is to open the viewport before loading the scene, I can then open the viewport again after the scene has loaded without it crashing DS.