Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
There are a few problems people may run into trying to use WillowTree#. Most often when people find that they cannot load or save their savegame, it is a result of one of these things.
1) If you try to use WillowTree with Xbox 360 savegames and you do not have an internet connection, WillowTree# will crash. This is related to a bug in the third-party X360.DLL library file that WT# uses. The solution to this is to download a newer version of the X360 dll library from the author here:
Download the zip file and replace x360.dll in your willowtree folder with the one in the zip file. This problem effects users that attempt to open Xbox saves when they don't have internet access available (or they blocked it with their firewall) because the older version of X360.DLL deployed with WT 2.2.1 has a bug in its version check.
2) WillowTree# has a bug saving to paths that contain a folder named Data. If you try to save to one, the save will always fail. For instance you cannot save your savegame to a path like C:\WillowTree\Data or C:\Games\Data\Borderlands. The workaround for this is to make sure you don't put your savegames in a path that contains a folder called Data.
3) WillowTree# uses Microsoft .NET Framework 3.5 service pack 1. You must have it installed for WT# to work properly. If it is missing or damaged WT# will not work properly. Version 3.5 is required specifically. The later 4.0 version is not a replacement for it. They are designed to coexist peacefully on your computer and will be used as required by software written for one or the other. If you use Windows automatic updates then it should already be installed. If you do not then you may need to download it from microsoft here:
Bumping this one to the top since it is still relevant for people who cannot get WillowTree# to work, especially Xbox 360 users.
I have since created a new version of the X360 library that is located in the files area that people may want to use instead of downloading the one listed in #1. I would say that #1 is probably the most frequent cause of problems for Xbox users and #3 for users of Windows versions before Windows 7.