It will work, however, if you rollback to an older version of the software and use an offline profile. The procedure is so asinine that it led me to test this out for myself, and sure enough if you crash GFWL (which is easy enough by simply disconnecting while it updates) the entire thing crashes from then on and won't update properly even if you do a clean uninstall and then a reinstall. Rinse and repeat that logic whenever this issue arises. What's more is that support for games using GFWL can't troubleshoot the service because GFWL is operated by Microsoft, as indicated in the following forum thread. Well, the real kicker is that so long as you can sign-in to GFWL the problem is no longer something Microsoft deals with considering that they don't troubleshoot third-party games. In one case the service and game wouldn't acknowledge that players were logging in, and in result it became impossible to actually save the game since saved games are attached to GFWL profiles and the profile log-in wasn't being acknowledged. What's more is that the GFWL service wouldn't be so bad if perhaps there were viable workarounds. Of course, this led many gamers to group up and form a petition for Namco's upcoming PC release of Dark Souls, hoping to prevent it from utilizing the DRM-based Games for Windows Live platform, mostly because of a few of the problems mentioned above. If you can't log into the account, if there are problems with GFWL, or the update fails, etc., etc., you simply cannot access the multiplayer. The problem, however, is that online play via GFWL works like an online pass, restricting online play to that singular account and that account alone. Even if you register your game with a serial key you'll have to re-input the key to play online as a safeguard against hackers and pirates. The other issue is that GFWL is a DRM-style authenticator for anyone who wants to play online.
0 kommentar(er)
