https://www.gamersnexus.net/game-be...ous-misleading-benchmark-tool-gameworks-testsAs we discovered after hours of testing the utility, the FFXV benchmark is disingenuous in its execution, rendering load-intensive objects outside the camera frustum and resulting in a lower reported performance metric. We accessed the hexadecimal graphics settings for manual GameWorks setting tuning, made easier by exposing .INI files via a DLL, then later entered noclip mode to dig into some performance anomalies. On our own, we’d discovered that HairWorks toggling (on/off) had performance impact in areas where no hair existed. The only reason this would happen, aside from anomalous bugs or improper use of HairWorks (also likely, and not mutually exclusive), would be if the single hair-endowed creature in the benchmark were drawn at all times.
The benchmark is rendering creatures that use HairWorks even when they’re miles away from the character and the camera. Again, this was made evident while running benchmarks in a zone with no hairworks whatsoever – zero, none – at which point we realized, by accessing the game’s settings files, that disabling HairWorks would still improve performance even when no hairworks objects were on screen.
We wanted the benchmark tool to approximate the level of visual quality and performance you can expect from your PC environment when running FINAL FANTASY XV WINDOWS EDITION. A Level Of Detail (LOD) issue has been discovered that affects the benchmark scores.
The benchmark also suffers from stuttering; both of the issues will be addressed in the shipping game. While the settings in the benchmark are largely pre-selected for simplicity’s sake, the final game will feature highly customizable settings with On/Off options... (1/2)I would already assume that the available graphic options in game would medigate this issue. I am, still, curious to hear a response about the benchmarking app itself. As that is the main issue that this whole thing stems from, not the game.
No information on an update regarding the actual benchmark.