Cinema 4D 2024.5.1 windows registry key end in hash instead of major version number
-
Firstly this is a bug, but I wasn't able to post directly into the bug forum.
Secondly this isn't really an SDK issue, but figured this is a fine community to raise the issue in.So the problem I've found is that the registry key for Cinema 4D 2024.5.1 on Windows end in a build hash instead of the major version. This means the registry path is now:
HKEY_LOCAL_MACHINE\SOFTWARE\Maxon\Maxon Cinema 4D 9cac615ccf68a2d4af092ff2cb09640d05c8aa02d3ac06cd4ef5fb474b95fd3e
where on all previous versions it was:
HKEY_LOCAL_MACHINE\SOFTWARE\Maxon\Maxon Cinema 4D 2024This surfaced as it was causing issues in our software since we utilize these registry keys to find installations of C4D. We've now implemented a more robust system to identify installations from registry keys, so we don't actually need this fixed. Just figured it was worth surfacing the error.
Here is a screenshot of the registry of a Cinema 4D 2024.5.1 installation:
-
Hi @kitbash_ave just to let you know that this is not a bug but a on purpose change, since you are free to install multiple version in different location of the same version. Therefor the hash represent the installation path, while with the previous way (aka just the version number) you then have some conflict.
If you want to know the version, now you have to read the DisplayVersion key under this entry.
Cheers,
Maxime. -
Alright! Thats a sweet improvement.
Okay no worries we'd already moved to the method you described!
Does this change back propagate to earlier versions like 2023?