News for hackers. Stuff that matters.
Re:Babylon.js 3.0 by graedus on Wednesday July 12, 2017 @11:20PM (#14758478)
I'll add my experience with the "PBR Glossy" demo:

Windows 8.1

Chrome: 144fps

Firefox: 144fps

IE11: 72fps

Not sure why IE11 is getting exactly half the framerate of the other two, which are maxing at my monitor's refresh rate. At least none of them hanged or crashed.

Re:Babylon.js 3.0 by moron4hire on Thursday July 13, 2017 @12:19AM (#14758663)
requestAnimationFrame is designed to animate on whole frame boundaries for the monitor on which it is running, to avoid screen tearing. So if IE can't do 144hz, the next option is 72hz. You'll similar see 60hz displays running at 60, 30, or 15 FPS.
Re:Babylon.js 3.0 by DiThi on Thursday July 13, 2017 @06:50PM (#14765983)
The next one after 30 is 20 (one frame every 3 syncs).
Re:Babylon.js 3.0 by moron4hire on Friday July 14, 2017 @11:29AM (#14770550)
If we want to be picky about it, the next one after 30 is "shut the app down, tear it apart, and rewrite from scratch. Anything less than 30 is completely unacceptable."
Re:Babylon.js 3.0 by DiThi on Saturday July 15, 2017 @09:35AM (#14776545)
It depends on the application. In one of my jobs for an educative platform I automatically maintained it over 15 but under or at 30 (if it was over 30, it improved quality).