It does have a whole bunch of different types of constraints though, so my first thought was to use those to implement ropes.
The Chipmunk engine doesn't have built-in ropes – easy decision. I didn't use the built-in ropes in the Chipmunk physics engine. The relative sizes of the little guy, the dog, the mouse, and the soccer ball are game design decisions that bent reality for better game play possibilities. This is fairly typical in the craft of game design and development in that you are always making various trade-offs. The performance was better because the code didn't have to calculate all the collision and physics needed for the whole length of the rope cutting down drastically on the calculations needed. This was both a game design and a performance (speed of execution) decision. So their only game play function is to transfer forces between the parts attached to either end. For example, in their final incarnation, the ropes don't collide with anything. Deciding exactly what elements or rope behavior to implement involved trade-offs affecting both performance and also design. The first decision made was exactly how much of a rope's behavior I was going to model.
This is just a quick overview of how I went about implementing them in CM and some of the potholes I hit along the way. It was mostly traveling development paths that others have already blazed and then making whatever adjustments were needed for my specific needs. Getting realistic ropes working required tackling several different problems.
Contraption maker logl full#
After going through Steam's early access program, the full game was released on Steam in the summer of 2014. It was built using a modified version of the Loom Engine, along with a few different libraries/components including cocos2dx and Chipmunk. Contraption Maker (CM) is a sandbox physics game that I developed along with Spotkin.
0 kommentar(er)
