'torque' divided by 'inertia' twice? about matter-js HOT 8 CLOSED

This may depend on your particular setup.

Can you provide a jsfiddle please?

from matter-js.

http://jsfiddle.net/wafo2qga/1/
It's used to be C/S structs. Matter.js running on my server and send frame data to a browser. The task of the browser is to draw frames. So the code is strange.
http://203.195.196.109:8899/game.html

from matter-js.

It looks like you're only applying a (small) force for a single frame?
I think you need to apply a bigger force over a number of frames to get the acceleration you're looking for.

But actually, what you probably need to use is Body.setAngularVelocity which is instantaneous, where as forces are much slower acting.

from matter-js.

No.. You didn't get my point.
http://jsfiddle.net/wafo2qga/2/

Body.applyForce(boxA, Vector.add(boxA.position,{x:80,y:0}), {x:0,y:-0.5});

A 'small' force let the box jump so high without any rotation. Isn't it abnormal?

from matter-js.

I do get your point, it does seem a little strange that there's no rotation given the change in linear velocity.

So there may be an issue with angular force application. I'll investigate further, thanks.

from matter-js.

I ran into this issue today too. Fix seems to be to remove * body.inverseInertia from Body.js:570.

Based on my rather limited understanding, this makes sense based on the physics because the torque isn't proportional to inertia, however the angular momentum that results from it is.

from matter-js.

Wow, I was having so much trouble getting things working, I thought it was because I didn't understand what was going on, but turned out by removing * body.inverseInertia everything makes sense now !

Is the bug still here? Or is it just me?

from matter-js.

Fixed in the latest master build, thanks guys.

from matter-js.