aoktar wrote:Chriz wrote:Hi,
thanks for the latest built.
My question: a previously working scene now causes octane to crash. Log:
----------
Started logging on 30.04.21 09:38:52
OctaneRender Enterprise 2020.2.3 (10021500)
Up-sampling error: CUDA_ERROR_ILLEGAL_ADDRESS: an illegal memory access was encountered
CUDA error 700 on device 0: an illegal memory access was encountered
-> failed to copy pitched memory from device
----------
With other scenes i don´t have this issue.
C4D R20 / Rendering on a single 3090 RTX / newest Studio driver
Is this a plugin related mistake or indicates the log file that there is something wrong with the c4d file?
Thanks a lot in advance!
Best, Chris
Not a plugin thing for my opinion. What's GPU usage for VRAM and temperatures?
Hi Aoktar,
thanks for replying. Meanwhile i found a solution. Somehow the old file got corrupted (while laying on the SSD?! O_o), but copying the elements into a fresh file worked fortunately.
Sorry for bothering you with such a low level problem
FYI, don´t know if this is of any value for you:
1. Lately (this octane version) assigning one material unnoticed two times to the same object, made it impossible to render (big archviz scene). Took me a while until i found this "mistake"
Deleting one of the two material-tag was all i had to do... (all iremember it was some specular mat)
2. Rendering on camera in a bigger archviz scene (still fitting in the 24GB VRAM) in the picturviewer works most of the times (3 of 4) without a crash, but trying to render a different cam right afterwards most often results in a C4D crash and program closure. This happens so consistent, that i often restart C4D for the next rendering, instead of waiting for the crash first
I am not using any fancy plugins other than laubwerk in this scene.
Anyway, thanks a lot for your great work. Most of the time everything works as aspected.
Have a nice day, Chris