1

In general, it depends on the game. You say: The first option seems suited for a LocalPlayerController because that's the naive way you normally read the mouse coordinates in the screen and adjust the deltaYaw and deltaPitch based on the deltaX and deltaY of the mouse. But not on every game you don't. Let us keep in mind that both sound like high level ...


1

The second approach is better in general (with the exception of code that generates a new mesh each frame). The reason is that queueing request allows you to execute them in batch. And that opens plenty of optimizations. For example, use a single render call for many identical meshes. And if you are switching shaders, you can make of the render calls for ...


Only top voted, non community-wiki answers of a minimum length are eligible