pi to 37 digits (rounded down on the last digit): 3.1415926535897923284626433832795028841 See original project for explanation: https://scratch.mit.edu/projects/985321285 ------- TurboWarp ------- https://turbowarp.org/986190076?turbo&fps=60
Circle radius increased "slightly" more (from 49500 to 493266927800) After about a day of leaving this project running in the background, on TurboWarp, on turbo mode, with 60 fps turned on, I got the approximation pi ≈ 3.14155, accurate to 4 decimal places. (Putting the exact hits and misses variable values in a calculator and manually calculating the formula got me 3.14154852004, so that's a slightly more accurate idea of the approximation.) It still seems to undershoot pi a little bit, but noticably less than the first project with a radius of only 180 pixels. I think increasing the radius further would yield more accurate results but I'll stop making new projects for it. If you want to expiriment with it yourself, change the value in the set size to (31415926535) % block to a different value. Higher values should be more accurate.
