Animmaniac: Woah … My mind is blown. That WOULD be good for C3.
Aphrodite: I agree, we need to test at lower framerates. I just meant I’m not sure how to force it low enough to test it.
Here’s the spreadsheet I had up earlier, with newly-corrected numbers comparing the actual physics, the built-in behavior from C2, and my Platform Minus. It shows two important things:
1. IF we could assume a constant framerate, Platform Minus would give less variation in jump height than the built-in behavior as the framerate is set lower and lower. This indicates, but doesn’t absolutely prove, that Platform Minus would improve consistency between machines.
2. In both Platform Minus and the current behavior, velocity seems to lag behind position by one tick. This might mean position should technically calculate before velocity (so it’s using the previous tick’s velocity values), but I'm not 100% certain, and I also couldn’t say whether you would get enough extra accuracy to justify the change.
Thanks for your support, everyone else who’s commented so far. Thanks for your help with the math, Aphrodite and Colludium, and especially, thanks, Ashley, for considering my idea.
Also, would anybody mind if I saved a copy of this forum topic as it stands now? It might come in handy as project experience on a resume. Collaborating to solve a technical problem, providing data to support my claims…