Should the update loop and render loop be merged?

[nightm4re94]

^{This post has been migrated automatically from the old LITIENGINE forum (2018 - 2022).
Posted: 2019-05-05 22:28:57
User: TheRamenChef [] (age: 1441 days 🔥; posts: 5)}
When I move the camera around to follow the player, in the update loop, it causes various graphical glitches, such as entities lagging behind the camera and screen flickering when loading a different map. These glitches could all be fixed if the game didn't update and render at the same time, but enforcing that could lead to performance issues. What alternative options are there? Are the performance losses acceptable?

[nightm4re94]

^{This post has been migrated automatically from the old LITIENGINE forum (2018 - 2022).
Posted: 2019-05-06 12:01:02
User: CalvinMT [] (age: 1451 days 🔥; posts: 114)}
I've encountered this problem aswell and did not give it any importance for the moment although it is a serious subject.
I'm definitely not an expert at this, but I don't think that merging the update loop and the render loop is a solution - that is because I think the game sometimes needs to do updates that doesn't need any rendering - although I don't think they should be independent.

[nightm4re94]

^{This post has been migrated automatically from the old LITIENGINE forum (2018 - 2022).
Posted: 2019-05-08 19:01:58
User: steffen [Admin 👑, Mod 🔧] (age: 1568 days 🔥; posts: 100)}
TheRamenChef You can attach your logic to update the camera to the render loop. That would be the recommended way and that's, in fact, the reason why the focus of the current camera is evaluated just before rendering (see ~~~~RenderLoop.process()).

[nightm4re94]

^{This post has been migrated automatically from the old LITIENGINE forum (2018 - 2022).
Posted: 2019-05-12 00:36:00
User: TheRamenChef [] (age: 1441 days 🔥; posts: 5)}
I had no idea that the focus was buffered like that. With that in mind, I've created fixes for some of the graphical glitches.