I submitted a bug report which was dismissed because it compared results in the smoothest renderer known to current c2 users - nw 10.5. I followed up with an example of frequent frame dropping in modern browser versions but the report was already dismissed and the results ignored.
Ashley, how do you measure high performance in physics behaviour? Being within 1.5 of native speed is useless to a game dev if every 10th frame is dropped and causes janking on non-NASA hardware. My bug report showed some quantitative evidence of what many users have been reporting here, that r196 reduced c2's game making potential (measurable dropped frames), even if the update increased the total number of objects that the engine could run at a janky 30 fps.
I just want a few objects to be rendered at a smooth 60 fps by the physics engine. I don't think the x thousand objects at a janky 30 ish fps is representative of how c2 will normally be used....