Hi. Yesterday, I downloaded Willowtree due to the glitch on dlc3 (Armory glitch) Everything was working fine after I fixed it. Shortly after, I downloaded a map mod called "Oasis" because it had a hub for fast travel in dlc3. After playing for a while, I noticed that I was stuck at level 66 with my experience bar saying 3,628,272 - 7,783,184. I could gain xp but my bar wouldn't move. Plus, when I exited the game and came back my experience would go back to saying 3,628,272 - " ". Now, I was using an old version of Willowtree so I was suspecting that maybe the old version was made before dlcs and patches for leveling up came out. (Willowtree wouldnt let me change my xp past 3,628…) I proceeded to download the newest version of Willowtree. My save file loaded up fine but then it wouldn't let me save. I looked around for a bit and tried some stuff that helped others but then I started getting the error of "Couldn't load save" I've even tried downloading an older WT# to see if it would open but it won't. When I try to play Borderlands, I hit single player and then it crashes. Im at my wits with this and I have no idea on how to fix this problem. I would really hate to have to start over again (By the way, I have other save files that load up fine but its just this one that won't)
Sorry for the wall of text. I really have no idea on what to do though.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've not tried to use any player created maps, so I don't know what effect if any they may have on WillowTree# or on the format of your savegame. WT# supports DLC 1-4 since that is what I have savegame examples to develop code for. The 2.2.1 and later versions have much better support for expansion data in the savegame than older versions did There were certainly cases when version 2.0 beta 11 and earlier could corrupt expansion data due to not parsing the data correctly and that is why I joined the WT# project as a developer, to try to help fix those problems.
The experience cap is determined by what expansions you have installed. If you are using versions of Borderlands prior to 1.30 I believe the level cap is 50. If you are using version 1.30 or later of Borderlands and you do not have any expansions I think the level cap is 58. If you are using version 1.30 or later and you have any of the DLCs other than General Knoxx's armory I think the cap is 61 and if you are using 1.30 or later and have General Knoxx's Armory (dlc3) then the level cap is
69, Don't quote these numbers as if they are God, but it works something like this. I may not have the exact numbers correct. If you exceed the level cap I think you still get experience messages but the bar does not actually move. That appears to be what has happened to you.
I don't know for sure how Borderlands determines if General Knoxx's armory is installed to figure out what the experience cap is for you. It is possible that data is stored in the savegame and if that data is corrupted BL may not be able to figure out that you have DLC3 and would cap you at level 61.
If your game crashes when you try to load it then I think it may be likely that you have some invalid item data, but if WillowTree# can load it then it is likely a fixable problem like an invalid item quality or level. WT# will usually refuse to load any data that is a result of actual damage to the Borderlands save file. You'll have to send me a copy of the savegame file for me to figure out exactly what the issue may be. You can email it to me in an attachment or email a link to someplace you've uploaded it that I can download it (like mediafire.com or megaupload.com) at matt911@users.sf.net and I will look into it and try to tell you exactly what the problem may be.
I will tell you that there is a problem with version 2.2.1's handling of item levels in the case where the item level index is negative. WT# cannot normally make items with negative level indexes (since the sliders only have positive numbers) and Borderlands does not create them either, but some players may have bogus items that they created by hand with a hex editor or obtained from another player that did so that can create issues. The latest development version in the "uichange" branch of the SVN archive can support items with negative levels since it has corrected the bug with the integer conversion in 2.2.1 and has a way to edit and view the raw level index in a text box if you want instead of using the slider so you can access negative numbers. However, you'd need a bit of programming saavy to get the source code from the SVN and compile it. There has not been an official release from that code yet.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Note that when you use the save button in WillowTree# it will make .BAK files that are a copy of your original savegame if you saved over your old save in that way you may be able to retrieve an old version of it by renaming one of those BAK files back to sav. If you used the SaveAs button it does not make a copy of a file when you overwrite it since it asks you if you want to overwrite it when you push it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, with the item level stuff. I have never gone into WT# and changed anything except the Location of where I start (Needed for the map mod I downloaded) and the armory quest glitch so I don't think it could be the item level bug unless it can accidently change on its own. Now, I do quite a few .bak files so hopefully thats a good thing. Im in the process of uploading my save right now so I'll have that up in a few. Hopefully you can figure out whats wrong with the darn thing. :(
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oh wow. I just tried to upload my save file to mediafire and it says it can't because its empty. Im guessing a corrupted file then? Anyway I can get another copy of my save file to you using the .bak?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Update: Looking at my save files, I have the messed up save saying that there is 0kb on its size. Now, I have two other .bak files that are my most recent with 0kb as well and only one .bak that is just a bit behind that with kb on it. Maybe take a few copys of that .bak file and convert to .sav?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
WT# allows something like 10 backup copies of a save of one name before it starts throwing the old bak files away. The ones with 0 KB are corrupt. The newest one that is not empty is probably your most recent save. If you have any older ones that are not empty then they are older versions of the save. I would make copies of any of the ones that are not empty for archival purposes in another folder, then make a second copy to work on and rename the extension to .SAV instead of .BAK3 or whatever it is. That file should hopefully still work in Borderlands. Email me a copy of that and I'll look at it to see if I can figure out why WT# may be unable to write it after it reads it.
Probably the 0 byte ones were created when WT# started saving the file then experienced some kind of error that made it unable to continue saving. That may be how WT# currently works (I have to take a look to see) and if so it may be something I need to fix since it really should restore the bak file any time the save fails. If a person tried to save too many times and were unable to save it might have so many bad copies that the original would no longer be present if that is the case and that's something I don't want to happen. As a precautionary measure I would suggest that any time you are editing a save just in general its safest if you make your own backup copy of it first just in case, then you know that no matter what you do to it you can always go back if something is wrong.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Update: So I started messing around with the save files and I converted a slightly recent .bak file to a .sav file. What seems to be the problem is that Willowtree messes with the save files or something. When I open the new .sav in WT#, it loads up fine but then the problem of it saving occurs. After exiting out of WT#, it deletes all of the memory on the save. If that save is in your save data it makes the game crash on startup. So I took out the bad saves and replaced them with a new converted .sav and never opened it with Willowtree. Game started up find and I have my character back. The only problem that still is around is that exp bar. For some reason, its still bugged out. This is the only problem that I'm not sure how to fix and it could possible be linked to the map mod due to the fact that the character with the exp bug is the only character that went on the map mod. Hopefully, this helps for further people with problems and would still love to hear your input. :D Especially this darn exp bug. >:( (Note: I have all the dlc and I'm at 66. Which means I should still be able to go to level 69 but the bug is persisting that.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Seems we were both replying that the same time :D Ya, as stated in the update thats what I did and it seems to fix it. Thanks for the input. Hopefully, this exp bar can be fixed as well. :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Update: As I've know, I'm pretty sure the map mod corrupted my file. I deleted everything that had to do with the map mod last night yet my character in Willowtree says I can still go to such locations. (Other characters are fine when it comes to loading and saving in WT#) Since my file is behind repair at the moment, is there anyway I can "make" a new character on Willowtree and just put everything that my old character has? Such as a "clone" of my corrupted character? I'm totally fine with that as long as it works and such…even if the process of cloning is extensive. Any thoughts on that?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
One last update: After trying the "cloning", I found out that I couldn't save with WT# on any of my save files. After searching online, I downloaded .NET 3.5 framework. It fixed all the problems with Willowtree and enabled me to save. My exp bar was fixed and the game is running perfectly. Sorry for all the updates and such. I just hope this serves as a solution for others that come across the same problems. Also, the map mod had nothing to do with corrupting my files. It was just Willowtree messing up after I asked to save.
Tl,dr?: Download .Net 3.5 framework! (Vista users with Borderlands pc) Ps. Thanks Matt for your help and input :D Again, sorry for all the posts :\
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm happy to have any updates. Too much information is much preferred to too little. I've had people report what appeared to be severe issues at times in the past that did not follow up in any way so I was never able to find any resolution for them. Thank you for letting me know how you resolved this problem. This may be helpful information for others that experience issues saving with WillowTree#. I know another person was telling me just last week that he couldn't seem to save no matter what he did. I will have to recommend this to him and perhaps it will solve his problem as well.
I knew that not having .NET 3.5 would prevent WT# from working, but I assumed it would provide the user with some kind of error message that would make it clear that was the problem. It may be that is true but if you have an old buggy version of NET 3.5 you may not receive the same warning. I will make sure to recommend to people that they make sure they update .NET if they have this problem in the future. In this internet age most users use automatic Windows updates and the automatic update includes .NET 3.5 service pack 1 so this is not a typical problem, but I recognize this isn't the case for everyone and now that I know that it can be an issue for WT# I will be sure to point it out.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i need help i had willowtree working before i restored my computer because it had viruses and now when i download willow tree it wont open ive tried all the websites 2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You haven't been very specific about what won't open.
First off, WillowTree# requires Microsoft.NET Framework 3.5 Service Pack 1 to run and if you reinstalled Windows you might not have that. Make sure you have this installed either through Windows Update or download it directly from:
Were you unable to open the zip archive to extract the WillowTree# files? If so then you need to reinstall the software you use to open zip files like JZip (freeware), 7-Zip (open source freeware), or WinRAR (commercial).
www.winrar.com
www.jzip.com
www.7-zip.org
After installing one of these, be sure you extract all the files including the Data folder and all its contents to a folder that the user will have read and write access to. If you have to give the unzip program administrative access to extract the files, then you probably won't be able to run WillowTree# from that folder unless you also run it as administrator. Sub-folders of the desktop and My Documents folder should have always allow the user read and write access. Sub-folders of C:\Program Files do not allow non-administrator users write access in newer versions of windows (Vista for sure, maybe also Windows 7?) by default unless you change the folder security permissions.
If you are trying to use WillowTree# to open Xbox savegames and it is crashing, get the updated version of x360.dll from the files area in the x360lib folder. There are instructions there and in the zip archive that explain how to install it.
If you are having some problem that doing these things does not solve, then please explain to me exactly what stage of this process you are having the problem, what you are doing, and what is happening instead of what you expect to happen.
I believe Windows has a built-in handling for zip files as well and if it is not working then you must have either a corrupt system or you disabled searching in zip archives.
If you have been able to extract the files and install the program
WillowTree# is in a zip archive. If you can't install it then you need to reinstall the software you use to read zip archives. Windows actually can read zip archives without any software installed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You haven't been very specific about what won't open.
First off, WillowTree# requires Microsoft.NET Framework 3.5 Service Pack 1 to run and if you reinstalled Windows you might not have that. Make sure you have this installed either through Windows Update or download it directly from:
Were you unable to open the zip archive to extract the WillowTree# files? If so then you need to reinstall the software you use to open zip files like JZip (freeware), 7-Zip (open source freeware), or WinRAR (commercial).
www.winrar.com
www.jzip.com
www.7-zip.org
After installing one of these, be sure you extract all the files including the Data folder and all its contents to a folder that the user will have read and write access to. If you have to give the unzip program administrative access to extract the files, then you probably won't be able to run WillowTree# from that folder unless you also run it as administrator. Sub-folders of the desktop and My Documents folder should have always allow the user read and write access. Sub-folders of C:\Program Files do not allow non-administrator users write access in newer versions of windows (Vista for sure, maybe also Windows 7?) by default unless you change the folder security permissions.
If you are trying to use WillowTree# to open Xbox savegames and it is crashing, get the updated version of x360.dll from the files area in the x360lib folder. There are instructions there and in the zip archive that explain how to install it.
If you are having some problem that doing these things does not solve, then please explain to me exactly what stage of this process you are having the problem, what you are doing, and what is happening instead of what you expect to happen.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey so i have tried EVERYTHING on here and every other site i could find and this is still the issue im having…. I would just like to use willowtree to have my lvl 44 get to 69. everytime i do it though, it works perfectly!…. for like 5 minutes… then starts to insanely lag. Until it eventually freezes and corrupts my file making it 0kb and. Ive done everything i could do. please help me :(
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you could tell me which platform you are playing on it would be helpful. If you are edtiing a savegame on the Xbox, I'd also like to know which utility program you are using to extract the savegames from the flash drive (name and version number if you know it).
I'm sorry I haven't been here to help you for the last week, but I don't really have any good suggestions for you. I've not experienced this problem. I would say first off you need to make sure you have the latest update for Borderlands. I wouldn't be surprised if old versions had bugs. Next you need to make sure when you edit your savegame you don't add an excessive number of inventory slots if you are having any sort of problem like this since more inventory slots means more memory usage. Try a small reasonable number like 200 not a huge number like 10000. Finally I would suggest that you try to play without using any extremely modified weaponry as it might cause the fire rate of your weapon to be so high that the game machine can't physically keep up with the sound or graphic requirements, resulting in lag and/or malfunction.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Alright so never mind it wasn't williowtree it was a file in Binaries "nvcpl.ddl" . sorry bout that. But for anyone else with this problem look for that file in binaries and delete it and you should be fine.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi. Yesterday, I downloaded Willowtree due to the glitch on dlc3 (Armory glitch) Everything was working fine after I fixed it. Shortly after, I downloaded a map mod called "Oasis" because it had a hub for fast travel in dlc3. After playing for a while, I noticed that I was stuck at level 66 with my experience bar saying 3,628,272 - 7,783,184. I could gain xp but my bar wouldn't move. Plus, when I exited the game and came back my experience would go back to saying 3,628,272 - " ". Now, I was using an old version of Willowtree so I was suspecting that maybe the old version was made before dlcs and patches for leveling up came out. (Willowtree wouldnt let me change my xp past 3,628…) I proceeded to download the newest version of Willowtree. My save file loaded up fine but then it wouldn't let me save. I looked around for a bit and tried some stuff that helped others but then I started getting the error of "Couldn't load save" I've even tried downloading an older WT# to see if it would open but it won't. When I try to play Borderlands, I hit single player and then it crashes. Im at my wits with this and I have no idea on how to fix this problem. I would really hate to have to start over again (By the way, I have other save files that load up fine but its just this one that won't)
Sorry for the wall of text. I really have no idea on what to do though.
I've not tried to use any player created maps, so I don't know what effect if any they may have on WillowTree# or on the format of your savegame. WT# supports DLC 1-4 since that is what I have savegame examples to develop code for. The 2.2.1 and later versions have much better support for expansion data in the savegame than older versions did There were certainly cases when version 2.0 beta 11 and earlier could corrupt expansion data due to not parsing the data correctly and that is why I joined the WT# project as a developer, to try to help fix those problems.
The experience cap is determined by what expansions you have installed. If you are using versions of Borderlands prior to 1.30 I believe the level cap is 50. If you are using version 1.30 or later of Borderlands and you do not have any expansions I think the level cap is 58. If you are using version 1.30 or later and you have any of the DLCs other than General Knoxx's armory I think the cap is 61 and if you are using 1.30 or later and have General Knoxx's Armory (dlc3) then the level cap is
69, Don't quote these numbers as if they are God, but it works something like this. I may not have the exact numbers correct. If you exceed the level cap I think you still get experience messages but the bar does not actually move. That appears to be what has happened to you.
I don't know for sure how Borderlands determines if General Knoxx's armory is installed to figure out what the experience cap is for you. It is possible that data is stored in the savegame and if that data is corrupted BL may not be able to figure out that you have DLC3 and would cap you at level 61.
If your game crashes when you try to load it then I think it may be likely that you have some invalid item data, but if WillowTree# can load it then it is likely a fixable problem like an invalid item quality or level. WT# will usually refuse to load any data that is a result of actual damage to the Borderlands save file. You'll have to send me a copy of the savegame file for me to figure out exactly what the issue may be. You can email it to me in an attachment or email a link to someplace you've uploaded it that I can download it (like mediafire.com or megaupload.com) at matt911@users.sf.net and I will look into it and try to tell you exactly what the problem may be.
I will tell you that there is a problem with version 2.2.1's handling of item levels in the case where the item level index is negative. WT# cannot normally make items with negative level indexes (since the sliders only have positive numbers) and Borderlands does not create them either, but some players may have bogus items that they created by hand with a hex editor or obtained from another player that did so that can create issues. The latest development version in the "uichange" branch of the SVN archive can support items with negative levels since it has corrected the bug with the integer conversion in 2.2.1 and has a way to edit and view the raw level index in a text box if you want instead of using the slider so you can access negative numbers. However, you'd need a bit of programming saavy to get the source code from the SVN and compile it. There has not been an official release from that code yet.
Note that when you use the save button in WillowTree# it will make .BAK files that are a copy of your original savegame if you saved over your old save in that way you may be able to retrieve an old version of it by renaming one of those BAK files back to sav. If you used the SaveAs button it does not make a copy of a file when you overwrite it since it asks you if you want to overwrite it when you push it.
Thanks for replying so quick. :D
Ok, with the item level stuff. I have never gone into WT# and changed anything except the Location of where I start (Needed for the map mod I downloaded) and the armory quest glitch so I don't think it could be the item level bug unless it can accidently change on its own. Now, I do quite a few .bak files so hopefully thats a good thing. Im in the process of uploading my save right now so I'll have that up in a few. Hopefully you can figure out whats wrong with the darn thing. :(
Oh wow. I just tried to upload my save file to mediafire and it says it can't because its empty. Im guessing a corrupted file then? Anyway I can get another copy of my save file to you using the .bak?
Update: Looking at my save files, I have the messed up save saying that there is 0kb on its size. Now, I have two other .bak files that are my most recent with 0kb as well and only one .bak that is just a bit behind that with kb on it. Maybe take a few copys of that .bak file and convert to .sav?
WT# allows something like 10 backup copies of a save of one name before it starts throwing the old bak files away. The ones with 0 KB are corrupt. The newest one that is not empty is probably your most recent save. If you have any older ones that are not empty then they are older versions of the save. I would make copies of any of the ones that are not empty for archival purposes in another folder, then make a second copy to work on and rename the extension to .SAV instead of .BAK3 or whatever it is. That file should hopefully still work in Borderlands. Email me a copy of that and I'll look at it to see if I can figure out why WT# may be unable to write it after it reads it.
Probably the 0 byte ones were created when WT# started saving the file then experienced some kind of error that made it unable to continue saving. That may be how WT# currently works (I have to take a look to see) and if so it may be something I need to fix since it really should restore the bak file any time the save fails. If a person tried to save too many times and were unable to save it might have so many bad copies that the original would no longer be present if that is the case and that's something I don't want to happen. As a precautionary measure I would suggest that any time you are editing a save just in general its safest if you make your own backup copy of it first just in case, then you know that no matter what you do to it you can always go back if something is wrong.
Update: So I started messing around with the save files and I converted a slightly recent .bak file to a .sav file. What seems to be the problem is that Willowtree messes with the save files or something. When I open the new .sav in WT#, it loads up fine but then the problem of it saving occurs. After exiting out of WT#, it deletes all of the memory on the save. If that save is in your save data it makes the game crash on startup. So I took out the bad saves and replaced them with a new converted .sav and never opened it with Willowtree. Game started up find and I have my character back. The only problem that still is around is that exp bar. For some reason, its still bugged out. This is the only problem that I'm not sure how to fix and it could possible be linked to the map mod due to the fact that the character with the exp bug is the only character that went on the map mod. Hopefully, this helps for further people with problems and would still love to hear your input. :D Especially this darn exp bug. >:( (Note: I have all the dlc and I'm at 66. Which means I should still be able to go to level 69 but the bug is persisting that.)
Seems we were both replying that the same time :D Ya, as stated in the update thats what I did and it seems to fix it. Thanks for the input. Hopefully, this exp bar can be fixed as well. :)
Update: As I've know, I'm pretty sure the map mod corrupted my file. I deleted everything that had to do with the map mod last night yet my character in Willowtree says I can still go to such locations. (Other characters are fine when it comes to loading and saving in WT#) Since my file is behind repair at the moment, is there anyway I can "make" a new character on Willowtree and just put everything that my old character has? Such as a "clone" of my corrupted character? I'm totally fine with that as long as it works and such…even if the process of cloning is extensive. Any thoughts on that?
One last update: After trying the "cloning", I found out that I couldn't save with WT# on any of my save files. After searching online, I downloaded .NET 3.5 framework. It fixed all the problems with Willowtree and enabled me to save. My exp bar was fixed and the game is running perfectly. Sorry for all the updates and such. I just hope this serves as a solution for others that come across the same problems. Also, the map mod had nothing to do with corrupting my files. It was just Willowtree messing up after I asked to save.
Tl,dr?: Download .Net 3.5 framework! (Vista users with Borderlands pc) Ps. Thanks Matt for your help and input :D Again, sorry for all the posts :\
I'm happy to have any updates. Too much information is much preferred to too little. I've had people report what appeared to be severe issues at times in the past that did not follow up in any way so I was never able to find any resolution for them. Thank you for letting me know how you resolved this problem. This may be helpful information for others that experience issues saving with WillowTree#. I know another person was telling me just last week that he couldn't seem to save no matter what he did. I will have to recommend this to him and perhaps it will solve his problem as well.
I knew that not having .NET 3.5 would prevent WT# from working, but I assumed it would provide the user with some kind of error message that would make it clear that was the problem. It may be that is true but if you have an old buggy version of NET 3.5 you may not receive the same warning. I will make sure to recommend to people that they make sure they update .NET if they have this problem in the future. In this internet age most users use automatic Windows updates and the automatic update includes .NET 3.5 service pack 1 so this is not a typical problem, but I recognize this isn't the case for everyone and now that I know that it can be an issue for WT# I will be sure to point it out.
i need help i had willowtree working before i restored my computer because it had viruses and now when i download willow tree it wont open ive tried all the websites 2
You haven't been very specific about what won't open.
First off, WillowTree# requires Microsoft.NET Framework 3.5 Service Pack 1 to run and if you reinstalled Windows you might not have that. Make sure you have this installed either through Windows Update or download it directly from:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=22
Were you unable to open the zip archive to extract the WillowTree# files? If so then you need to reinstall the software you use to open zip files like JZip (freeware), 7-Zip (open source freeware), or WinRAR (commercial).
www.winrar.com
www.jzip.com
www.7-zip.org
After installing one of these, be sure you extract all the files including the Data folder and all its contents to a folder that the user will have read and write access to. If you have to give the unzip program administrative access to extract the files, then you probably won't be able to run WillowTree# from that folder unless you also run it as administrator. Sub-folders of the desktop and My Documents folder should have always allow the user read and write access. Sub-folders of C:\Program Files do not allow non-administrator users write access in newer versions of windows (Vista for sure, maybe also Windows 7?) by default unless you change the folder security permissions.
If you are trying to use WillowTree# to open Xbox savegames and it is crashing, get the updated version of x360.dll from the files area in the x360lib folder. There are instructions there and in the zip archive that explain how to install it.
https://sourceforge.net/projects/willowtree/files/x360lib/
If you are having some problem that doing these things does not solve, then please explain to me exactly what stage of this process you are having the problem, what you are doing, and what is happening instead of what you expect to happen.
I believe Windows has a built-in handling for zip files as well and if it is not working then you must have either a corrupt system or you disabled searching in zip archives.
If you have been able to extract the files and install the program
WillowTree# is in a zip archive. If you can't install it then you need to reinstall the software you use to read zip archives. Windows actually can read zip archives without any software installed
You haven't been very specific about what won't open.
First off, WillowTree# requires Microsoft.NET Framework 3.5 Service Pack 1 to run and if you reinstalled Windows you might not have that. Make sure you have this installed either through Windows Update or download it directly from:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=22
Were you unable to open the zip archive to extract the WillowTree# files? If so then you need to reinstall the software you use to open zip files like JZip (freeware), 7-Zip (open source freeware), or WinRAR (commercial).
www.winrar.com
www.jzip.com
www.7-zip.org
After installing one of these, be sure you extract all the files including the Data folder and all its contents to a folder that the user will have read and write access to. If you have to give the unzip program administrative access to extract the files, then you probably won't be able to run WillowTree# from that folder unless you also run it as administrator. Sub-folders of the desktop and My Documents folder should have always allow the user read and write access. Sub-folders of C:\Program Files do not allow non-administrator users write access in newer versions of windows (Vista for sure, maybe also Windows 7?) by default unless you change the folder security permissions.
If you are trying to use WillowTree# to open Xbox savegames and it is crashing, get the updated version of x360.dll from the files area in the x360lib folder. There are instructions there and in the zip archive that explain how to install it.
https://sourceforge.net/projects/willowtree/files/x360lib/
If you are having some problem that doing these things does not solve, then please explain to me exactly what stage of this process you are having the problem, what you are doing, and what is happening instead of what you expect to happen.
Hey so i have tried EVERYTHING on here and every other site i could find and this is still the issue im having…. I would just like to use willowtree to have my lvl 44 get to 69. everytime i do it though, it works perfectly!…. for like 5 minutes… then starts to insanely lag. Until it eventually freezes and corrupts my file making it 0kb and. Ive done everything i could do. please help me :(
If you could tell me which platform you are playing on it would be helpful. If you are edtiing a savegame on the Xbox, I'd also like to know which utility program you are using to extract the savegames from the flash drive (name and version number if you know it).
I'm sorry I haven't been here to help you for the last week, but I don't really have any good suggestions for you. I've not experienced this problem. I would say first off you need to make sure you have the latest update for Borderlands. I wouldn't be surprised if old versions had bugs. Next you need to make sure when you edit your savegame you don't add an excessive number of inventory slots if you are having any sort of problem like this since more inventory slots means more memory usage. Try a small reasonable number like 200 not a huge number like 10000. Finally I would suggest that you try to play without using any extremely modified weaponry as it might cause the fire rate of your weapon to be so high that the game machine can't physically keep up with the sound or graphic requirements, resulting in lag and/or malfunction.
Alright so never mind it wasn't williowtree it was a file in Binaries "nvcpl.ddl" . sorry bout that. But for anyone else with this problem look for that file in binaries and delete it and you should be fine.