Version 2.3.0.289 has been released and it should enable WT# to work with Borderlands GOTY Enhanced savegames. There are many new data bytes (about 185) that i don't have any understanding of so probably if you try to convert an Enhanced save from PC to PS3/Xbox 360 or vice versa its extremely likely that some progress or character data (something other than the item data which I believe is fully understood) will end up being scrambled. That may cause problems or may not be immediately noticeable depending upon what the purpose of that data is, so make backups of your characters first if you plan to try. There's currently no viewer or editor for the added Enhanced data bytes, but they are preserved as they are when you edit a character.
If anyone experiences issues with this new build or has any comments or suggestions they'd like to pass on please do so here. Happy hunting!
UPDATE:
Fixed a bug from revision 289 that was causing crashes when classic savegames that had items in Mad Moxxi's bank were loaded. Version 2.3.0.291 is now available.
UPDATE:
Version 2.3.0.292 fixes a bug that could cause corruption of bank and item data upon save if quests or echoes were imported directly from an enhanced savegame to a classic or vice-versa.
UPDATE:
Version 2.3.0.293 replaces the slider control with one that does not require Windows visual styles that should enable WT# to work in the Windows 2000 style classic UI in Windows 7 and earlier. It changes the visual look of the slider control, but it should work the same.
Another update v2.3.0.292 has been posted to fix a save corruption bug if quests or echoes from a classic savegame were merged directly into an enhanced savegame or vice versa due to concurrent use of a shared variable used to keep track of how many bytes there should be in the save for each backpack and bank item or weapon. The links have been updated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't know which weapons you are calling legendaries. I tried to copy a pearlescent (light blue) weapon from one save using the clipboard and pasting it into the weapon inventory of the other and it says it requires level 68. Here's a copy of the weapon code I used:
Import that weapon into one of your savegames and see what level it comes out in Borderlands. If its still 57 then please tell me what platform you are playing on and what DLCs you have installed. If you provide a copy of the weapon you are trying to create that might help me understand why it won't work for you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I appreciate the help, but, unfortunately, I am a massive, massive idiot.
I forgot that weapon proficiencies lower the 'item level' when a weapon is equipped, so level 69 weapons, when equipped, show up as level 57 weapons because I have level 50 proficency with pistols. (at least, pistols do.)
Last edit: Connor Dicken 2019-04-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ahh I see. I didn't even know that. or if I did I must have forgotten it 7 or 8 years ago, so I can easily see how it might perplex someone not aware of it. Glad to hear that the issue is resolved for you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So when BL:GOTY-E first came out WillowTree didn't yet work with the game. So the only way I could think of to import a new character and custom items into the "new" game was to create a level 1 character in-game in the old original Borderlands 1 game and play it just enough to get to fyrestone and get to the first new-u station. Then I went to the old willowtree and added in a bunch of custom stuff. I then went and imported that level 4 character in to the "new" game and I've been playing on it up to level 44. Well I just downloaded the new version of Willowtree, excited to be able to use it with my new playthrough character.. only after opening the character the WillowTree program instantly crashes when I click on the weapons tab. This is reproducable and happens every time I open the character in the new program version. A screenshot is here: https://i.imgur.com/3MMNmzK.png And my save should be attached to this message.
This is in Windows 7 x64. If you need any other information just ask.
Also I wanted to add (And this is just a suggestion for a way to improve the program, not an actual bug or anything): When we go to the skills tab in the new WillowTree, changing around the weapon proficiency settings.. we can set it to like level 50 for pistols, but the experience points don't change. I have no idea what XP points the game would want for a character to actually have level 50 in pistols normally but.. I think WillowTree should automatically adjust the Experience for weapon proficiency based on the level we set some how.. I don't know what would happen if I were to play a character with level 50 proficiency in pistols but only 75 experience points. It might work but possible be unstable / weird. I'll probably wait until I reach level 50 proficiency in a skill naturally then copy-paste it's XP to all the other skills so it's "Right".
Yes, you wouldn't even be able to open a GOTY Enhanced savegame if you weren't using at least 2.3.0.287. It saying 2.2.1 is a result of my forgetting to update the version number internally.. At one time I started to write a script to automate the process of fetching the SVN revision and updating the version number automatically in makedist.bat which builds the distribution files but I never got round to finishing it then I didn't work on WT# for several years and I dont know if I even have that lying around still waiting to finish or not so fornow that is still stuck in the dark ages of manual updates which frequenlty get overlooked..
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the feedback and thanks for including the save file to help diagnose the problem. Sometimes other people have problems that I do not and it helps a lot to have a save file to try to reproduce the issue. In this case, I cannot reproduce your problem. I open your save and go to the weapons tab and it does not crash.
I do have some idea what may possibly be causing the problem for you. On the weapons, items, locker, and bank tab there is a slider control that requires Windows visual styles to be enabled. If visual styles are not enabled then it will not work. As far as I know the only way to disable visual styles is to use the ancient classic Windows 2000 style UI, which most people do not do. It may be that it is crashing because visual styles are not enabled when it tries to display this control. I can see in your screenshot there is no slider drawn in the place where the slider would appear normally on the weapon tab so it either crashed before it ever attempted to draw it or it crashed when it attempted to draw it.
Try to open WillowTree# then click on Options ->Level/Quality Editing Mode->Use Numeric Box Decimal. This will disable the slider and just display a numeric box in the place of the slider. Once you've done that try to switch to the weapon tab and see if it can do it without crashing. Let me know if that resolves the problem for you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Indeed I actually do have windows themes, and aero themes and all of that disabled in windows 7. I don't like any of that and I personally just prefer the basic flat windows look because I've been using computers since the MS-DOS days and I don't really like all that "fancy pretty flashy" stuff. So you're saying just because I have themes and Windows Aero disabled, this program is crashing? Ugh. I guess I'll try putting it back on and see if that fixes it.
EDIT: That's it. If I put themes back on, it doesn't crash anymore. That's mildly annoying that the program relies on that to work.. :( I understand I'm apparently in a niche group of windows users that doesn't have Themes enabled. But It's still.. weird that the program actually requires that and crashes if it doesn't exist.
I'll just have to turn on themes for editing in WillowTree and then turn it off again when done.
Thinking about this I'm guessing you're just assuming everyone uses windows 10 at least today, where themes and windows aero can't be disabled so you just programmed it assuming that everyone will have it. Kind of makes sense.
Last edit: Kithylin 2019-04-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Its not that I want to exclude people that use the classic desktop style its just that the only slider control provided in the C# Windows Forms user interface requires visual styles to be enabled. I'd have to find a third party slider control to replace it with, write one from scratch myself, or call Win32 DLLs written in C from the C# code to use the old sliders that were in Windows 95. All of those options are a pretty big hassle so I just took the path of least resistance at the time and it didn't bother enough people to be worth going back to change it later.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well don't worry about it if it's a big deal and a lot of work. I found a "work around" to make it work for me (turn themes on and off). It seems to be working otherwise just fine.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Someone else was having another unexplained problem with the slider so I decided to go ahead and hunt down a replacement that I know will resolve your problem and I hope will resolve his. It is implemeneted in the new 2.3.0.293 release. I tested it in briefly in Windows XP with visual styles disabled and it seemed to work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, I have downloaded the latest version without having ever downloaded a previous version before. When I attempt to open my PS3 Borderlands save, I receive the following error report:(see below). Please advise, thanks!
WillowTree# failed due to an unhandled exception.
System.FormatException: Bank entry to be written has invalid Type ID. TypeId = 0
at WillowTree.WillowSaveGame.ReadBankEntry(BinaryReader reader, ByteOrder endian)
at WillowTree.WillowSaveGame.ReadWSG(Stream fileStream)
at WillowTree.WillowSaveGame.LoadWSG(String inputFile)
at WillowTree.WillowTreeMain.Open_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at WillowTree.Program.Main()
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, I see the problem here. Thanks for your bug report. It appears that probably any non-Enhanced savegame that has items in Mad Moxxi's bank vault will have this problem until I fix the bug in code to read and write items to the bank vault. I dont usually have items in the bank so when I tested my old savegames I didn't spot this problem. I'll fix it and release a new version in an hour or two. In the meantime if you want to open old savegames that are not from the GOTY Enhanced version I would suggest to download and use the old version 2.2.1.286 which can be found in the files area in the experimental folder if you are trying to use WT# on the old version of Borderlands. If you are operating on a savegame that is created in the Enhanced version then use 2.3.0.289. The bank works for the Enhanced version but I broke it for the old version.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Windows 7 Home Premium 64-bit if that makes any difference.
The slider still works, but that's just a majorly off putting visual thing. Also to be clear, I have the latest version of the program before it was updated for GOTYE, and the bug wasn't there.
Last edit: Nope Derp 2019-04-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Do you have visual styles disabled in Windows? The slider control requires visual styles to display correctly.
You can select Options ->Level/Quality Editing Mode->Use Numeric Box Decimal to change the slider into a numeric box that will likely render correctly for you whether visual styles are enabled or not.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmm I have no idea what the problem is then. You are the second person to have a problem with it this week, but nothing's been changed recently with the slider. Its the same way its been for the last 7 or 8 years.. The other person did not have visual styles enabled. He was using the old windows classic desktop mode in Windows 7, which disables visual styles, but in his case it was crashing WT#.
I will look into replacing the slider control with another one. That would probably resolve both problems. No promises but I'll see if there's something that I can find to do about it later tonight.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, I found a new slider control to use. I tested it on Windows XP with visual styles disabled and it seems to work. Let me know if that fixes the problem you were having with the slider control or not as the slider you see in WT# is a custom user control that combines several controls including the slider. I'm assuming the slider is what is causing the problem but its possible it is not the case. Let me know. Release 2.3.0.293 is available now with the new slider.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems to work 100% with styles off here. I wanted to say thank you for all your effort with this. <3
If I could make one request.. could you allow us to resize the left window pane some how? When we enable all the options some of the titles of weapons go beyond the border and are unreadable. See here: https://i.imgur.com/jCecJ7M.png
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Version 2.3.0.289 has been released and it should enable WT# to work with Borderlands GOTY Enhanced savegames. There are many new data bytes (about 185) that i don't have any understanding of so probably if you try to convert an Enhanced save from PC to PS3/Xbox 360 or vice versa its extremely likely that some progress or character data (something other than the item data which I believe is fully understood) will end up being scrambled. That may cause problems or may not be immediately noticeable depending upon what the purpose of that data is, so make backups of your characters first if you plan to try. There's currently no viewer or editor for the added Enhanced data bytes, but they are preserved as they are when you edit a character.
If anyone experiences issues with this new build or has any comments or suggestions they'd like to pass on please do so here. Happy hunting!
UPDATE:
Fixed a bug from revision 289 that was causing crashes when classic savegames that had items in Mad Moxxi's bank were loaded. Version 2.3.0.291 is now available.
UPDATE:
Version 2.3.0.292 fixes a bug that could cause corruption of bank and item data upon save if quests or echoes were imported directly from an enhanced savegame to a classic or vice-versa.
UPDATE:
Version 2.3.0.293 replaces the slider control with one that does not require Windows visual styles that should enable WT# to work in the Windows 2000 style classic UI in Windows 7 and earlier. It changes the visual look of the slider control, but it should work the same.
Binary download link: https://sourceforge.net/projects/willowtree/files/2.3/WillowTree%23-2.3.0.293.zip/download
Source code download link: https://sourceforge.net/projects/willowtree/files/2.3/WillowTree%23-2.3.0.293-source.zip/download
Last edit: matt911 2019-04-10
Another update v2.3.0.292 has been posted to fix a save corruption bug if quests or echoes from a classic savegame were merged directly into an enhanced savegame or vice versa due to concurrent use of a shared variable used to keep track of how many bytes there should be in the save for each backpack and bank item or weapon. The links have been updated.
Having the same issue with the new version, I only seem to be able to make guns up to level 57 in-game.
Weirdly, this doesn't apply to purples or lower, they can be made up to level 69 no problem, but anything legendary never goes about level 57.
I don't know which weapons you are calling legendaries. I tried to copy a pearlescent (light blue) weapon from one save using the clipboard and pasting it into the weapon inventory of the other and it says it requires level 68. Here's a copy of the weapon code I used:
dlc3_gd_customweapons.Pearlescent_Weapons.CustomWeap_CombatShotgun_DahlJackal
gd_manufacturers.Manufacturers.Dahl
gd_weap_combat_shotgun.A_Weapon.WeaponType_combat_shotgun
gd_weap_combat_shotgun.Body.body5
gd_weap_combat_shotgun.Grip.grip2
gd_weap_combat_shotgun.mag.mag1
dlc3_gd_weap_UniqueParts.CombatShotgun.barrel3_DahlJackal
gd_weap_combat_shotgun.Sight.sight5
gd_weap_combat_shotgun.Stock.stock3
None
gd_weap_combat_shotgun.acc.accnone
dlc3_gd_weap_UniqueParts.CombatShotgun.DahlJackal_Material
gd_weap_combat_shotgun.Prefix.Prefix_Spread1_Hunters
dlc3_gd_weap_UniqueParts.Title.TitleP_Dahl_Jackal
0
5
3
70
Import that weapon into one of your savegames and see what level it comes out in Borderlands. If its still 57 then please tell me what platform you are playing on and what DLCs you have installed. If you provide a copy of the weapon you are trying to create that might help me understand why it won't work for you.
I appreciate the help, but, unfortunately, I am a massive, massive idiot.
I forgot that weapon proficiencies lower the 'item level' when a weapon is equipped, so level 69 weapons, when equipped, show up as level 57 weapons because I have level 50 proficency with pistols. (at least, pistols do.)
Last edit: Connor Dicken 2019-04-07
Ahh I see. I didn't even know that. or if I did I must have forgotten it 7 or 8 years ago, so I can easily see how it might perplex someone not aware of it. Glad to hear that the issue is resolved for you.
So when BL:GOTY-E first came out WillowTree didn't yet work with the game. So the only way I could think of to import a new character and custom items into the "new" game was to create a level 1 character in-game in the old original Borderlands 1 game and play it just enough to get to fyrestone and get to the first new-u station. Then I went to the old willowtree and added in a bunch of custom stuff. I then went and imported that level 4 character in to the "new" game and I've been playing on it up to level 44. Well I just downloaded the new version of Willowtree, excited to be able to use it with my new playthrough character.. only after opening the character the WillowTree program instantly crashes when I click on the weapons tab. This is reproducable and happens every time I open the character in the new program version. A screenshot is here: https://i.imgur.com/3MMNmzK.png And my save should be attached to this message.
This is in Windows 7 x64. If you need any other information just ask.
Also I wanted to add (And this is just a suggestion for a way to improve the program, not an actual bug or anything): When we go to the skills tab in the new WillowTree, changing around the weapon proficiency settings.. we can set it to like level 50 for pistols, but the experience points don't change. I have no idea what XP points the game would want for a character to actually have level 50 in pistols normally but.. I think WillowTree should automatically adjust the Experience for weapon proficiency based on the level we set some how.. I don't know what would happen if I were to play a character with level 50 proficiency in pistols but only 75 experience points. It might work but possible be unstable / weird. I'll probably wait until I reach level 50 proficiency in a skill naturally then copy-paste it's XP to all the other skills so it's "Right".
Last edit: Kithylin 2019-04-07
Well, it been a while since since i put some time on this app. I'v check your screenshot https://imgur.com/3MMNmzK and the app crashing clearly wrote 2.2.1. Then I download your save file and the last editor https://sourceforge.net/projects/willowtree/files/latest/download that is WillowTree#-2.3.0.289.zip
So.... maybe you have download it. But it seem you didn't run it to open your file and used older version.
I made the test click on weapon tab and didn get any error.
Despite what the error says, I assure you that I am using the latest version 2.3.0.289 when I submitted this a few minutes ago.
Yes, you wouldn't even be able to open a GOTY Enhanced savegame if you weren't using at least 2.3.0.287. It saying 2.2.1 is a result of my forgetting to update the version number internally.. At one time I started to write a script to automate the process of fetching the SVN revision and updating the version number automatically in makedist.bat which builds the distribution files but I never got round to finishing it then I didn't work on WT# for several years and I dont know if I even have that lying around still waiting to finish or not so fornow that is still stuck in the dark ages of manual updates which frequenlty get overlooked..
Thanks for the feedback and thanks for including the save file to help diagnose the problem. Sometimes other people have problems that I do not and it helps a lot to have a save file to try to reproduce the issue. In this case, I cannot reproduce your problem. I open your save and go to the weapons tab and it does not crash.
I do have some idea what may possibly be causing the problem for you. On the weapons, items, locker, and bank tab there is a slider control that requires Windows visual styles to be enabled. If visual styles are not enabled then it will not work. As far as I know the only way to disable visual styles is to use the ancient classic Windows 2000 style UI, which most people do not do. It may be that it is crashing because visual styles are not enabled when it tries to display this control. I can see in your screenshot there is no slider drawn in the place where the slider would appear normally on the weapon tab so it either crashed before it ever attempted to draw it or it crashed when it attempted to draw it.
Try to open WillowTree# then click on Options ->Level/Quality Editing Mode->Use Numeric Box Decimal. This will disable the slider and just display a numeric box in the place of the slider. Once you've done that try to switch to the weapon tab and see if it can do it without crashing. Let me know if that resolves the problem for you.
Indeed I actually do have windows themes, and aero themes and all of that disabled in windows 7. I don't like any of that and I personally just prefer the basic flat windows look because I've been using computers since the MS-DOS days and I don't really like all that "fancy pretty flashy" stuff. So you're saying just because I have themes and Windows Aero disabled, this program is crashing? Ugh. I guess I'll try putting it back on and see if that fixes it.
EDIT: That's it. If I put themes back on, it doesn't crash anymore. That's mildly annoying that the program relies on that to work.. :( I understand I'm apparently in a niche group of windows users that doesn't have Themes enabled. But It's still.. weird that the program actually requires that and crashes if it doesn't exist.
I'll just have to turn on themes for editing in WillowTree and then turn it off again when done.
Thinking about this I'm guessing you're just assuming everyone uses windows 10 at least today, where themes and windows aero can't be disabled so you just programmed it assuming that everyone will have it. Kind of makes sense.
Last edit: Kithylin 2019-04-07
Its not that I want to exclude people that use the classic desktop style its just that the only slider control provided in the C# Windows Forms user interface requires visual styles to be enabled. I'd have to find a third party slider control to replace it with, write one from scratch myself, or call Win32 DLLs written in C from the C# code to use the old sliders that were in Windows 95. All of those options are a pretty big hassle so I just took the path of least resistance at the time and it didn't bother enough people to be worth going back to change it later.
Well don't worry about it if it's a big deal and a lot of work. I found a "work around" to make it work for me (turn themes on and off). It seems to be working otherwise just fine.
Someone else was having another unexplained problem with the slider so I decided to go ahead and hunt down a replacement that I know will resolve your problem and I hope will resolve his. It is implemeneted in the new 2.3.0.293 release. I tested it in briefly in Windows XP with visual styles disabled and it seemed to work.
Hello, I have downloaded the latest version without having ever downloaded a previous version before. When I attempt to open my PS3 Borderlands save, I receive the following error report:(see below). Please advise, thanks!
WillowTree# failed due to an unhandled exception.
System.FormatException: Bank entry to be written has invalid Type ID. TypeId = 0
at WillowTree.WillowSaveGame.ReadBankEntry(BinaryReader reader, ByteOrder endian)
at WillowTree.WillowSaveGame.ReadWSG(Stream fileStream)
at WillowTree.WillowSaveGame.LoadWSG(String inputFile)
at WillowTree.WillowTreeMain.Open_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at WillowTree.Program.Main()
Ok, I see the problem here. Thanks for your bug report. It appears that probably any non-Enhanced savegame that has items in Mad Moxxi's bank vault will have this problem until I fix the bug in code to read and write items to the bank vault. I dont usually have items in the bank so when I tested my old savegames I didn't spot this problem. I'll fix it and release a new version in an hour or two. In the meantime if you want to open old savegames that are not from the GOTY Enhanced version I would suggest to download and use the old version 2.2.1.286 which can be found in the files area in the experimental folder if you are trying to use WT# on the old version of Borderlands. If you are operating on a savegame that is created in the Enhanced version then use 2.3.0.289. The bank works for the Enhanced version but I broke it for the old version.
Last edit: CKY 2019-04-09
The new version is now available for download as the default download. I updated the download links at the top of this post.
So I'm getting a visual bug whenever I use WillowTree. Namely that the sliders for quality and level are giant white boxes with a X through them, like so: https://www.dropbox.com/s/os6zwrsyjfj4u1o/Untitled2.png?dl=0
Windows 7 Home Premium 64-bit if that makes any difference.
The slider still works, but that's just a majorly off putting visual thing. Also to be clear, I have the latest version of the program before it was updated for GOTYE, and the bug wasn't there.
Last edit: Nope Derp 2019-04-09
Do you have visual styles disabled in Windows? The slider control requires visual styles to display correctly.
You can select Options ->Level/Quality Editing Mode->Use Numeric Box Decimal to change the slider into a numeric box that will likely render correctly for you whether visual styles are enabled or not.
Actually yes visual styles is enabled.
Hmm I have no idea what the problem is then. You are the second person to have a problem with it this week, but nothing's been changed recently with the slider. Its the same way its been for the last 7 or 8 years.. The other person did not have visual styles enabled. He was using the old windows classic desktop mode in Windows 7, which disables visual styles, but in his case it was crashing WT#.
It might be a Windows bug. I found an article about a recent bug that sounds similar to what you are seeing at https://blog.jtbworld.com/2018/12/red-x-symbol-error-after-updating-to.html .
I will look into replacing the slider control with another one. That would probably resolve both problems. No promises but I'll see if there's something that I can find to do about it later tonight.
Ok, I found a new slider control to use. I tested it on Windows XP with visual styles disabled and it seems to work. Let me know if that fixes the problem you were having with the slider control or not as the slider you see in WT# is a custom user control that combines several controls including the slider. I'm assuming the slider is what is causing the problem but its possible it is not the case. Let me know. Release 2.3.0.293 is available now with the new slider.
It seems to work 100% with styles off here. I wanted to say thank you for all your effort with this. <3
If I could make one request.. could you allow us to resize the left window pane some how? When we enable all the options some of the titles of weapons go beyond the border and are unreadable. See here: https://i.imgur.com/jCecJ7M.png