The biggest reason for us to look at Call of Juarez: Gunslinger was to figure out if Ubisoft had ditched their Uplay DRM or, like their last release with Far Cry: Blood Dragon, had implemented it as a secondary DRM. To our surprise, not only had they released it via. Steam without Uplay, they had ensured Techland's latest game was released with enough sensibilities to have it play (well) on PCs.
Part of our job in evaluating PC games is finding key problems and issues that developers and/or publishers might not have disclosed prior to release. The fewer problems we find, the easier our job becomes. Similarly, if we're provided with a game that is released with similar patterns or trademarks, then we know what to look for and, thus, our jobs becomes much easier.
Such as with the case of Gunslinger where we found that it was (largely) a Steam-released game and, so, we knew it would pose little problems. That isn't to say nor suggest that using Steam is a seamless experience, but rather we know that the game would be linked to a Steam account, or that it would access specific IP addresses that only Valve would use or even how it would install/remove itself.
Gunslinger does play (and scale) rather well on PCs and, for the time being, users can customise settings both in-game and through the obscure config files to their hearts content. While the game is unpatched in its current state we found little errors or problems playing it through end-to-end.
You can read more into our detailed report if you’re interested. We’ve explained what we’ve analysed within Call of Juarez: Gunslinger in greater detail. We also have a discussion thread on Call of Juarez: Gunslinger for those who are interested. Enjoy!