Hi Ferdinand,
Thank you for your help!
I've briefly tried out the solution you have proposed. I already have the registry key set. I've spent a day trying to get our scripts to work with UNC, but unfortunately haven't been able to complete a successful end to end render. Redshift is also important to us, so long path support there would be valuable in our flows as well.
For context, I am from the AWS Deadline Cloud team and we have written an integration to allow users to run Cinema 4D renders (including Redshift workloads) on our product. The current integration code is publicly available here.
One of the reasons that we encounter long path issues so often is that our assets are stored in a directory like C:\ProgramData\Amazon\OpenJD\session-d04e4000a1754907bcb75289655c2a8ff_32sm7o\assetroot-7a6a0443639bf42cdffb\
.
We intentionally chose this path to make the organization of assets clearer between different render jobs. However, it can prepend up to ~100 characters to the file path, depending on the user's path mapping.
While we are also working within AWS Deadline Cloud to allow the asset directory to be configurable (and potentially shortened), the work isn't trivial and so simply having long paths supported on Cinema 4D Python (and Redshift!) would simplify things a lot for us and our customers.
Unfortunately, I haven't been able to get Cinema 4D working with UNC long paths in our scripts after a day of debugging. Adding UNC everywhere doesn't just make it more complicated for us, but also for any contributors that wish to make changes to the adaptor.
So in short: we don't know of any scenarios where long path support in Cinema 4D Python is absolutely necessary, but it would save us and our users a lot of time and headache. We have projects that exceed the default path limit and would benefit from long path support in Cinema 4D Python and Redshift.
Thanks,
Joel