Cinema won't start with the latest nightly build

[haniel1107]

Hello, maybe this is happening only to me, but wanted to report.
My cinema won't start with the latest nightly build 31783.
Tried both, archive and install version.

The cinema starting pictures freezes at 100%.
With 31781 it is starting.

Using Win 11 / latest cinema 2023 / vray6

Thanks!

[deyan.hadzhiev]

Hi haniel1107, how much time are you waiting? Sometimes the plugin initialization may take longer.
If waiting more does not resolve the problem, can you try deleting your node material caches? They are located in the following two directories (for C4D 2023): <Preferences>/dc and <Preferences>/description.db .
If that does not help either, we may need a minidump of the process to check what might be happening.

[haniel1107]

Hi deyan.hadzhiev, thanks but this didn't help. Sorry, but could you explain me how to ceate a minidump file? A normal dumpfile is 8GB. Thanks

[deyan.hadzhiev]

I don't think there is an easy way to make a minidump anymore - we will be thinking about how we can make this process easier in the future. But for the time being, the full dump should do.

[deyan.hadzhiev]

By the way, can you also try to rename your entire preferences folder (e.g. adding a suffix to its name)? This will effectively discard all your preferences, but it might fix the problem, because sometimes preferences get corrupted and cause all sorts of problems. Deleting the directory afterwards and renaming back your renamed preferences will restore everything.

[haniel1107]

deyan.hadzhiev, I will try this first. Thanks!

[haniel1107]

deyan.hadzhiev, no nothing helped, build 31781 works, 31783 not.
I will wait for ne the next nightly build and try it again.

If not, is a dump file something where I can post the link public, or are there any personal information included?
Thanks!

[deyan.hadzhiev]

The dump file contains more or less the information that the process stores in memory. It is not a good idea to post it publicly - although it may be fairly difficult, different kinds of information may be extracted from it, and I can't even tell exactly what Cinema 4D might store in memory. So you should only share the link on private messages!

[haniel1107]

The dump file contains more or less the information that the process stores in memory. It is not a good idea to post it publicly - although it may be fairly difficult, different kinds of information may be extracted from it, and I can't even tell exactly what Cinema 4D might store in memory. So you should only share the link on private messages!

Thank you!

[haniel1107]

Hello deyan.hadzhiev unfortunately I have the same problem with the new hotfix version.
I have sent you a link to a dumpfile as PM.

Thanks a lot for your help!

[haniel1107]

Hi deyan.hadzhiev, I have deleted all other plugins and it works with the new version. I put back all other plugins one by one. I don't know why but the latest vray version 6 Hotfix 1) doesn't work together with Turbulence FD.
I tried a fresh installation of Turbulence, but this doesn't help. Maybe you can see the conflict in the dump file? For now I've deinstalled Turbulence, but would be great to have it back again.

Do you have an idea or does it help you to investigate? Thanks!

PS: As mentioned, it started with the nightly build 31783, before this version everything was fine.

[deyan.hadzhiev]

This information definitely helps our investigation, but I can't say yet why it occurs. Your precise information is much appreciated.