@Dr-Sassi Thank you so much for your kind and understanding response. I really appreciate the time and effort you’ve taken to address this, as well as the level of support you’ve provided. Unfortunately, during my last interaction with support, I wasn’t able to create a proper log report because of how intermittent the issue is. At that time, everything seemed to be working fine, and I assumed the problem had resolved itself.
Posts made by salt-summer
-
RE: C4D rampant "Incorrect file structure" corruption
-
RE: C4D rampant "Incorrect file structure" corruption
@Dr-Sassi Thanks for the suggestion. I’ve already contacted support, but unfortunately, they weren’t able to help. In my experience, they usually can’t (or won’t) assist if the issue involves anything outside of Cinema 4D itself, like server setups or macOS-related factors. That’s why I wanted to reach out here to see if anyone else has found a workaround.
-
RE: C4D rampant "Incorrect file structure" corruption
@clerk-finish Thanks for responding, I appreciate it! I’m having this issue randomly as well. Sometimes Cinema 4D enters a mode where all files I save get corrupted, then it just stops, only to come back later. It’s super unpredictable. I’ve updated macOS to the latest version, so I’m not sure if that’s part of the problem, but it’s definitely frustrating.
-
RE: C4D rampant "Incorrect file structure" corruption
@clerk-finish said in C4D rampant "Incorrect file structure" corruption:
My only workaround, if the file is still open in Cinema, is to save a copy to a local drive, then copy that back to the project on the server.
Hi,
I’m experiencing a very similar issue, but on a MacBook. For over a year, everything was working fine, but after updating macOS and installing the new Cinema 4D version, I started having problems with Cinema 4D. Files larger than 100-200 MB randomly get corrupted. Interestingly, a Windows computer on the same network doesn’t have these issues.
Did you find a way to resolve this? Or have you identified whether it’s a macOS, C4D, or server-related issue?