Box2D Forums

You are probably already putting them in since this awesome feature rolled out practically yesterday, but the friction/gear/mouse/pulley/rope/wheel joints don't seem to define a 'Dump()' function, which silently omits the joint from the log file and leaves an empty { } pair to signify where they would've gone. (It might be useful to put an assert into b2Joint::dump(), or perhaps just have it insert a code comment into the log, just until they get done.)

It kind of caught me off guard until I looked into the source. Those particular joints I imagine would be troublesome to generate, especially the gear joint since it depends on joint creation order, yikes. Was just trying out the dump() function out of curiousity so it's not the end of the world, it's pretty neat how it works!

I'm guessing he is just doing the most commonly used joints first.

Yes, the gear joint is a tricky one. I came across that when I implemented an importer/exporter recently. I needed to do them in a second pass once all the other joint types had been given an id to work with. Since Erin is adding to the library itself he will be able to access things a little easier, but it would very handy to have a b2Joint* GetJoint1() and GetJoint2() in the gear joint so that a b2GearJointDef can be fully reproduced using the normal API.

More to the point though, it seems like Diablo's minions may have a little more free time lately... but I'm probably just reading too much into that

Yeah, I will get the other joints done soon. Also, I plan to implement all those APIs to make things like JSON serialization easier.

Thank you!!
I updated my JSON loader for v2.2.0 to support chain shapes and can confirm that all necessary world state can now be obtained from the standard API.

Cool. 2.2.1 should go out soon.