Algodoo

Forgot to add, this is PHUNLET-SAFE. This means that you should be able to save it as a Phunlet and throw it anywhere to use it

The RPM meter reads 100 RPM higher than the RPM of the input shaft. I did a test by attaching a motor/axle to the input shaft (circle) and it confirms the result that I am getting.

It might look like it, but the number indicates the RPMs of the RED lines, not the gray ones. I know it is a bad design though.
I'm thinking on deleting the whole meter altogether, or maybe making the scale smaller, but it is not essential, you can simply delete the laser and the lines and the thing won't work worse

Whatever you did corrected that issue but it apparently created a new one! Now the indicator needle bounces (or oscillates) at a rate of about 2 per second between zero and the indicated RPM. It does that regardless of the RPM.

I wonder if a digital readout for this application might be better and less troublesome than the analog meter readout. Just a suggestion.

I see, are you testing it with a motor axle? That's just the good old exploding legacyMode 1 bug. If you attached the previous version of the dyno to an engine with very high torque at low RPMs, the force that a legacyMode 0 axle is not enough and the wheel will speen faster, giving inaccurate results (it would measure the torque of the engine at 300 RPM and display it as if it was the 100 RPM measurement). As a workaround I made it so that the axle switched to legacyMode 0 after 800 RPM, where most engines don't have that much torque.

If you used the dyno with an engine it will most probably not do that bouncy needle thing, this is just an Algodoo problem with a stretched axle with two axle motors on the ends

I connected THIS ENGINE to your dyno, and it does the same weird oscillation.

No offense intended, but I think your dyno has a design flaw.

You have to attach it directly to the crankshaft, no other axles in between, or Algodoo freaks out. It's just the damn "direct solver solution was non-finite" error.
I have connected it directly to the crankshaft and could carry out a reading just fine:
https://puu.sh/wLqek/181be2283d.png

The irregular part at the start of the curve is because this is a 4-stroke engine running at 10 times less speed than it would in real life, so the balls will get killed way before BDC. I've observed that the measurement of the dyno is much more irregular on any 4 stroke engine, for example my V6 engine has such huge peaks at low RPMs that the scale of the graph gets compressed to like 1/10th of the actual window size (even though smoothing 50 eliminates those peaks). But it does a nice curve on 3+ cylinder, 2 strokes

gotta add, I was looking at the RPM meter all the time and it never jumped

Yeah, that makes sense. I've had many problems with Algodoo axles in many different applications, and I often ended up having to switch them to legacy mode (don't recall if it's zero or one) in order to keep them from freaking out. That's one of the things that I wish Emil would have fixed before bailing out of Algoryx. The other thing on my Algodoo "complaint list" is the fact that you cannot write directly to an indexed array element (scene.my.array(35) = 3.14, for example). Oh well, thank God there's a work-around for that!

Overall, good job on the dyno!

I hate the array thing too... Had to rewrite the whole array every time I needed to change a value on my priority shooter thingy.
There are a bunch of things that could get fixed easily, for example on my platform every time I open the integrated browser and the Featured page is just about to load Algodoo freezes completely for 10 seconds at best (worst time was 2 minutes)

This is far from done, I just figured out I'll need to add a logarithmic scale for much higher RPMs... Hope I don't break anything else

Can you help me with widgets?

what widgets