I am not completely sure what you mean with 'collisions are not deterministic between saves'.
Could you elaborate a bit ?
Measuring & Angles:
Yes, what you have shown in the old video is part of what I had in mind.
I ususally have a reference point and now need to go a certain distance at a certain angle and place the cursor there.
For the other direction, eg. checking that my rendered object in pixels is also correct in MKS terms,
on the Mac I use the tool Pixelstick:
http://plumamazing.com/mac/pixelstick
Pixelstick provides two handles and then shows the distance between them and the angle compared to the horizon (180 to -180 degrees). I can also set an angle and pixelStick will rotate to the requested angle.
PixelStick activates a loupe when grabbing a handle so I can position the handles nicely.
The funny lines sticking out from the handles can be deactivated, But I found it is much better for alignment than just two handles.
PixelStick also supports scaling to Google Maps, Photoshop and stuff.
I use the custom scaling feature which I set with my meter-to-pixel ratio to check my app display with correct scaling.
Sometimes I even set the scaling to the zoom factor in RUBE and check what I have done in RUBE.
(In the screenshot scaling is set to Custom and and Rube zoom of 70 pixels per meter)
All this would be much easier if Rube could help with the measurements
Using three points which would be the span angle, which is also nice ...
![Wink ;-)](./images/smilies/icon_e_wink.gif)
Thanks for taking so much time to listen to my ramblings !!!
Best regards,
Thomas
PS: Was re-reading your collisions tutorial and found a nice typo:
.... you can use IsTouching() to check. Moron that later.
Nice ! ... Did you place it there on purpose ... ?