-
Rope simulation crashing C4D when tear occurs
I have a very simple rope simulation with not that many points in the spline or polygons in the mesh with a sweep.
I have a single point weighted to 100% vertex map for the tearing map, and I set the tear past % to 102 so it actually tears. The only issue is that the simulation completely breaks and crashes C4D.
The timeline freezes on the tear, then the frames continue with everything in the viewport frozen. I can still click anything I want, but nothing in the viewport changes, and I have to end task and reload the scene.
I tried only the spline without the sweep enabled, and it still does this, so it’s not simply a calculation error with too many polygons.
I can’t imagine why this is happening.
The simulation works up until the tear. I have an anchor point on each end so the rope is attached on both sides.
replied 1 year, 1 month ago 2 Members · 5 Replies
-
5 Replies
-
Hi Eric,
It may be necessary to record the screen or share the file if possible, I don’t know the method you used to make the rope tear, whether by applying tension from both sides or by dropping something on the rope, I have attached below a tutorial on how to do this by dropping another object and then hiding it, I hope this helps you.
https://youtu.be/DnFLOToXg0M?feature=shared
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
I finally figured out why all my simulations were breaking.
My objects were about 10 km from the origin point of my scene.
Apparently, the simulations completely fall apart if the objects are far away from the origin.
I now have no issues.
-
Oh! 10 kilometers, that’s too much! maybe the units in the project were in kilometers, anyway glad you figure out the problem, calculating simulation data for such a long distance in a limited number of time frames, so each frame might be hundreds of meters of simulation, would have definitely caused Cinema 4D crash as it happened to you, thank you very much for sharing with us, this will certainly be useful to many users.
-
My project is in meters.
I didn’t realize distance made that much difference.
I had a scene in space where the Earth was at the centre and distance was far to make it appear correct size.
C4D should give a warning like it does for low pyro resolution or high poly count for sims.
-
I don’t have exact information about this, but just a guess from previous experiences. I think that when the pressure is enormous, the program stops even before it can issue a warning. In some critical cases, the entire computer crashes until you stop and restart it. The device may even be damaged, as I saw it happen to a user who was working as part of a team on a huge stadium project that was scheduled to host an important sporting event. Therefore, I think that the matter is not a cause for concern.
Reply to this Discussion! Login or Sign Up