Hi there!
Since I updated C4DtoA from 2.3.x to 2.4.x, Cinema 4D doesn't start any more on two of my three machines and gets stuck on start screen, saying "initializing plugins". I tried it with 2.4.0, 2.4.1 and 2.4.2. Downgrading to 2.3.1.3 works.
Machine it DOES work on:
Machine it does NOT work on:
Machine it does NOT work on:
Any suggestions? I have all the latest drivers and updates installed, tried it with latest versions of R19 and R20, same results.Thanks in advance!
Can you run this kick command and post the log header?
"C:\Program Files\MAXON\Cinema 4D R19\plugins\C4DtoA\arnold\bin\kick.exe" -v 5 -i Nul
The log header is this part:
| log started Fri Nov 2 12:11:16 2018 | Arnold 5.2.0.1 [b9c11b0c] windows icc-17.0.2 oiio-1.7.17 osl-1.9.9 vdb-4.0.0 clm-1.0.3.513 rlm-12.4.2 2018/09/10 16:13:30 | running on REMFDXQFB2, pid=6360 | 2 x Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz (20 cores, 40 logical) with 32690MB | Nvidia driver version 391.33 | GPU 0: Quadro K2200 @ 1124MHz (compute 5.0) with 4096MB (2318MB available) | Windows 7 Enterprise Edition Service Pack 1 (version 6.1, build 7601)
Also, Can you send me the nvml.dll from a system where CINEMA 4D does not start?
C:\Program Files\NVIDIA Corporation\NVSMI\nvml.dll
Rename the file nvml.txt and attach it.
Thanks for your help!
Log header:
* Arnold 5.2.1.0 [7c7c9701] windows icc-17.0.2 oiio-1.7.17 osl-1.9.9 vdb-4.0.0 clm-1.0.3.513 rlm-12.4.2 2018/10/19 21:35:58 * CRASHED in nvmlDeviceGetDetailedEccErrors * signal caught: error C0000005 -- access violationnvml.txt
If you rename
C:\Program Files\NVIDIA Corporation\NVSMI\nvml.dll
to
C:\Program Files\NVIDIA Corporation\NVSMI\nvml.bak
does CINEMA 4D start?
It does! Can I leave it as .bak or does it have any negative side effects?
No negative side effects for Arnold or C4DtoA.
Or CINEMA 4D afaik.
But if you had some other sotware using Optix, then it would be an issue
At the moment, I don't, so this seems to work for me 🙂
Thank you so much for your help! I'd have never been able to fix this on my own.
Hello @Stephen Blair, I have the exact same situation as @Gerrit Oosterhof. I tried following the directions that you sent them but it didn't work for me. I'm assuming it's a different scenario for each computer? Should I bump down to a previous version of Arnold or can I keep the updated version v2.4.2? Let me know, thanks.
No, if it is the exact same problem, then the same workaround should fix it.
Can you start a new question, and we'll discuss it there? Include the output of running
"C:\Program Files\MAXON\Cinema 4D R19\plugins\C4DtoA\arnold\bin\kick.exe"-v 5-i Nul
(if you are on Windows)
Hi @Kianna Peppers Can you start a new question, so we can work on your problem?
thanks
Hi @Stephen Blair. Sorry just seeing this, didn't see a notification. You can find it here:
Thank you for getting back to me!