60 frames per second isn't possible on a 60Hz monitor: The most serious problem with this port lies in its performance limitations - currently, we've determined that it simply isn't possible to reach frame-rates matching the refresh rate of the monitor in use. The maximum frame-rate seems to be limited to 5/6th of the refresh rate - this means, when using a 60Hz monitor, the game simply cannot go beyond 50 frames per second. We even tried it with a Core i7 system paired with Titan X running at 720p on the lowest settings, but 50fps was still the limit - and the same thing applies to AMD GPUs too. The resulting frame-time graph sees the game bouncing between 16.7 and 33ms throughout the experience - even with the most powerful PC hardware available. With a 50Hz refresh rate then, you'll be limited to just 43fps. When using a 120Hz or 144Hz monitor, the maximum frame-rate obviously increases, but you can't achieve a level of performance that results in consistent, level frame-times. As far as we can tell, a judder-free experience is impossible at the moment without a patch from Remedy. This is something we've never seen before, but we've reproduced the issue on two different PCs running four different graphics cards.

30fps cap doesn't work properly: Users might find that simply capping the frame-rate at 30fps - an option in the menu - could help deliver the near-locked, more consistent update seen on Xbox One. Unfortunately, that just isn't possible either. When the cap is engaged, the game's frame-pacing becomes an issue, resulting in a jerky experience. While it's possible to achieve a measured frame-rate of 30fps, it will never appear as consistent as the Xbox One version, which mostly delivers each frame at a locked 33ms refresh. Normally, we would use the Nvidia half-refresh rate option or Riva Tuner Statistics Server to solve this problem but as a Universal Windows Platform app, the full-screen mode is limited to borderless window, preventing these tools from functioning at all.

Crashing: On two of our Nvidia-equipped systems, Quantum Break crashed. A lot. It's important to stress that it's not the game code itself that died, but rather the Nvidia driver. It's not often that we see the display driver itself crash and recover outside of extreme overclocking tests, but that's exactly what we experienced here. We attempted to rectify the issue by eliminating all traces of the driver from our machines and re-installing, while also using both the latest and older drivers - the results were the same. Quantum Break is unstable on Nvidia hardware, and this may well also explain the inexplicably poor performance we put up with on GTX 970 - remarkably, the AMD R9 390 equivalent is 50 per cent faster. A brief history of Fallout War. War changes quite a lot. A brief history of Fallout

So at this point, we've established that Quantum Break has made a poor first showing, but how does it stack up against the Xbox One version? Truth be told, even with the enhancements, the graphical improvements are limited. It's difficult to appreciate some higher precision features in the face of the other issues. As it stands, we've found that it's impossible to experience the game at a smooth 30 or 60fps on the PC. Frame-pacing issues and the inability to reach your display's refresh rate are a genuine issue for the PC version and prevent the game from ever feeling as smooth as the Xbox One version. For users with a choice between the two, we recommended avoiding the PC version until it is fixed, and recommend playing on Xbox One instead if that option is available.