Closed emign closed 4 years ago
Hm, could we save both versions? The old one like more straightforward/thorough and the new one like more optimal and recommended?
It should use fixed updater if not using the parameter with the time. You can compute a multiplier with:
val ratio = it / 16.milliseconds x += 2 * ratio
Or use fixedUpdater
For example I have a 144hz screen. If not doing so, I would see it something like 2.1x times faster than when using a 60hz screen
addUpdater is every frame and fixedUpdater 60 times per second?
addFixedUpdater
allows you to configure times per second. For example:
view.addFixedUpdater(16.666666.milliseconds) {
}
or
view.addFixedUpdater((1.0 / 60.0).seconds) {
}
after the new version you will also be able to do too:
view.addFixedUpdater(60.timesPerSecond) {
}
Nice. We need a video for that
Indeed
very minor