Does the developer even test this crap? v1.0d STILL doesn't preserve configuration files! WTF!
After updating LW in the mod manager, now ever time I start the game, it creates a fresh copy of XComInput.ini in in the XComGame\Config in My Documents, which replaces my customized ini and resets all my key bindings! I had to make the file READ-ONLY to prevent this stupid mod manager from resetting it.
And now there is not way to undo this update! It's like a virus.
Need some help. Just set this up on my mac using Wine to start using mods with Long War. Worked perfectly with the Line of Sight mod. Added a couple more mods and tried it again. I had to re-enter the file paths for the XEW folder and the Long War Installation File, which I thought was weird but maybe it's normal. Regardless, I'm quite certain I put in the same file path as the first time, but when I hit "Update Long War!" I get an error that says "The selected XCom Enemy Within file does not exist". The file path I used was Z:\Library\Application Support\Steam\SteamApps\common\XCom-Enemy-Unknown\XCOMData\XEW. Any ideas on what might be wrong? I've checked several times and that file path definitely exists.
65 comments
If you select the Engine.upk from the game's folder you get the following error:
Failed to copy
"C:\Program Files (x86)\Steam\steamapps\common\XCom-Enemy-Unknown\XEW\XComGame\CookedPCConsole\Engine.upk"
to"C:\Program Files (x86)\Steam\steamapps\common\XCom-Enemy-Unknown\XEW\XComGame\CookedPCConsole\Engine.upk"
It tries to copy the file from to the same location and obviously fails miserably.
After updating LW in the mod manager, now ever time I start the game, it creates a fresh copy of XComInput.ini in in the XComGame\Config in My Documents, which replaces my customized ini and resets all my key bindings! I had to make the file READ-ONLY to prevent this stupid mod manager from resetting it.
And now there is not way to undo this update! It's like a virus.