It looks like you're new here. If you want to get involved, click one of these buttons!
Though setting this value is just an upper limit and box2d might use less iteration if it founds a good solution, but there can be a small performance gain with lesser position iteration. I think it wont be much of a problem to use separate value for each of them. More info on iteration can be found hereThe suggested iteration count for Box2D is 8 for velocity and 3 for position.
Orx uses only one value for the solver iteration number as it's how most of the physics engine work (at least the most common used in gamedev: physx, havok, bullet, ...).
Box2D is thus kind of an exception here and I'd rather stick with the majority when designing a plugin code/config interface, that's why I didn't add two separate values for iterations.
That being said, I can make sure that the position iteration number is half the speed one instead of being the same value, I have no problem with that.
edit: oh, thanks