You drop a custom xlive.dll and a xlive.ini into the game’s root folder. The game thinks it’s talking to Microsoft, but it’s actually talking to the wrapper. The .ini file tells the wrapper how to lie. The Core Settings (What Each Line Does) Open xlive.ini in Notepad, and you’ll see a short list of key-value pairs. Here is the standard legend:
; The path where saves go (defaults to game's root or My Documents) SavePath=.\saves\
"My controller has double input." Solution: Set FakeXInput=false or delete the line. The wrapper is emulating a controller and the game sees your real one. xlive.ini
[XLIVE] ; Built-in handle to xlive.dll ; If false, the wrapper will try to load the original GFWL if installed. Logging=false ; Save type: true = use local save only, false = try to use GFWL container ; Set to true to bypass "Failed to initialize Games for Windows Live" UseLocalSave=true
Did it save your 100-hour Fallout 3 save? Or did it corrupt your Resident Evil 5 co-op? Post below. Let’s archive this knowledge before it’s lost to time. End of post. You drop a custom xlive
If you’ve ever tried to play a PC game from the late 2000s to early 2010s—titles like GTA IV , Fallout 3 , Resident Evil 5 , Batman: Arkham Asylum , or Dark Souls: Prepare to Die Edition —you’ve likely encountered a ghost in the machine: . To the average user, it’s just another obscure configuration file. To a modder or a preservationist, it’s a key that can unlock, break, or resurrect a game.
GFWL required you to sign into a Microsoft account, save your game to a "profile," and sync achievements online. When GFWL died (or became unstable), many games became unplayable or couldn't save. The Core Settings (What Each Line Does) Open xlive
; Your local username (case-sensitive in some wrappers) Username=Player1