News for hackers. Stuff that matters.
Re:MariOCaml: HTML5 Mario, written exclusively in OCaml by mahsu on Sunday December 20, 2015 @06:58PM (#10768851)
What would be the best way to throttle fps and ensure compatibility between different refresh rates?
Re:MariOCaml: HTML5 Mario, written exclusively in OCaml by moron4hire on Sunday December 20, 2015 @07:14PM (#10768884)
You count the time since the last update, wait for the time to accumulate over the update threshold, run the update loop with a fixed time-slice enough times to match whole number of frames. Let the carry over perpetuate to the next frame.

At 144hz with a fixed time-slice set for 60hz, you'd have one update on the 2nd, 4th, 7th, 9th, 12th, 14th, etc. frames.

Re:MariOCaml: HTML5 Mario, written exclusively in OCaml by TronPaul_ on Sunday December 20, 2015 @10:12PM (#10769363)
The best way is usually to not tie game state to frame ticks. See Bethesda's Creation Engine https://www.youtube.com/watch?v=Yuyp-S7FPNI for why that's a bad idea.