- User Since
- Jan 31 2004, 8:54 PM (728 w, 4 d)
Fri, Jan 5
@Philipp Oeser (lichtwerk) Here's the file, all pared down from the original, but has the motion tracking data, and the working constraints.
Thu, Jan 4
Wed, Jan 3
Nov 28 2017
This was my conclusion as we’ll. There would not seem to be an apparent reason that the collision modifier would not be like other physics modifiers and have the same UI design, with the enable/disable icon. There have been some times I’ve wanted to disable it, but instead had to remove and reapply it in the physics panel (luckily it retains its settings.) I’m sure that there is a reason, there always is.
Nov 27 2017
Sep 22 2016
A few months ago, I was seemingly having the same problem, and stumbled across this bug report, and chalked it up to a bug that had not yet been addressed. It turned out, however, that there was another reason for my results, and I was able to solve my problem, and just want to make sure others don't make my same mistake if stumbling across this report. I also do not know if this is the problem being experienced by Tobias Regengrecht when he posted this. I downloaded his blend and it was mapped correctly for me.