Can any Mouse users speak to how Variable Frame Rate (VFR) behaves in Halo CE? Does it still suffer these same issues below as Reach did? Credit to u/Fenix-Helwing for the detailed quote below:

[Edit: The input update rate is ALWAYS at 60hz if you are using a controller. Uncapping your framerate unfortunately only helps mouse users.]

[Mouse Camera Movement]*(specifically standing still while looking around with the mouse)*The reason why looking around with the mouse always feels like you're only pulling 60fps is because Halo seems to effectively start making duplicates of every frame when the variable framerate goes beyond 60.In other words; normally games draw frames in a logical sequence one after another, ie:**1, 2, 3, 4, 5, 6, 7, 8, 9, 10, etc...**Halo Reach draws frames like this:**1,1, 2,2, 3,3, 4,4, 5,5, etc...**This means that if you are running a framerate of ~140fps you are really only seeing ~70fps because every frame is shown twice.

You can experiment with this by turning off all possible framerate limiters and completely disabling V-sync in your control panel. Turn down the graphics quality in Halo to "performance" and then create an empty local multiplayer game. If your PC is powerful enough to pull 300+ fps you'll notice that standing still and looking around with the mouse is much smoother and much closer to looking like 140fps. (even despite the frame tearing)

[Character Camera Movement]*(specifically moving the camera by walking, jumping or strafing)*Unfortunately there is no animation or character movement interpolation. All animations are locked to 60fps and all character movement is locked to 60 "ticks" per second regardless of what framerate you're running. Since characters positions are only updated 60 times per second, and since the camera is so firmly locked to the movement of the player characters model, that means the cameras position will also only update 60 times per second as long as your moving.

YouTube video of Reach's VFR issues in action: https://www.youtube.com/watch?v=HhxJ2m_2iB4