This is the fastest version I (and scratching_claws) could come up with. This version reportedly gets instant times on most computers (correct me if I'm wrong). My slow ahhh chromebook gets a .5 second refresh rate, but this is the furthest we could possibly optimize it. Leave this running for a little while, come back, and press Space to see the average time the frames took! I really like what you (@scratching_claws) did!! Just a few fatal flaws here and there... One big mistake that you made is putting the "pen down" inside of the inner loop (which is SO expensive, like 12 more RTC per pixel than needed). This version gets .5 SECONDS (on my slow Chromebook)!!!!!!!!!
Other minor optimizations: - Using -i2 + 180 instead of i2 - 180 * -1 (idk if this made a difference really) - Did change x by 1 instead of whatever complicated math you had. Barely made a difference, but still... - I actually simplified (and made faster) a lot of complex math you had. PLEASE!!!!!!!!!: Keep in mind (if you are to remix this again) that the RTC of xpos/ypos is .3, and the RTC of ANY (variable) reporter is .6, so use xpos/ypos wherever you can (that makes sense at least)!! - Moved the blocks around for a bit more correct timing What DIDN'T work: - Instead of a separate i variable, I calculated the index based on i2 and i3. Didn't work at all. It was, in fact, slower. This might be Scratch's limit to optimization...
