Please download the latest experimental revision from the experimental files area, extract it to a different folder, and try to run it. It has a more detailed error log that will be much more helpful in determining what your problem is. There isn't enough information provided in this Windows event log for me to diagnose the problem.
I just noticed that the error log you posted says you are using version 2.1.0.0 The latest release version should report 2.2.1.0 I think. Please make sure you try using the latest release revision if you are having problems.
Additionally, if you are opening Xbox 360 savegames please check for a replacement for the x360.dll library in the "x360lib" folder as you may need it if WT# crashes at the moment you try to open any Xbox 360 savegame.
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: willowtree#.exe
Problem Signature 02: 2.2.1.0
Problem Signature 03: 502b34c1
Problem Signature 04: WillowTree#
Problem Signature 05: 2.2.1.0
Problem Signature 06: 502b34c1
Problem Signature 07: 5a4
Problem Signature 08: 91
Problem Signature 09: System.TypeInitialization
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I still can't tell what the problem is with 2.2.1.102, so the suggestion to try the latest experimental revision to get a more detailed exception report stands, though I can see you aren't getting exactly the same error as you were in version 2.1. Something is failing during static initialization of a class, but I can't tell what class or what operation is failing from the log, which is why I created the new exception handling code in the experimental revision.
The most likely problem is improper installation or lack of user access so WillowTree# can't find or operate on one of the files in its Data folder during startup. Typically to install you must extract all the contents of the ZIP file into a folder that the user has both read and write access to, such as a subfolder of My Documents for instance, then run WillowTree#.exe in that folder to use it. If you don't have proper access to one of the files or the folder then the experimental revision will terminate with a file not found exception or unauthorized access exception and list the name of the file that it couldn't access. I'll be able to tell you more when I see the error dump from the new experimental revision. If you can get that to work then WT# 2.2.1.102 should work properly also in general.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
FYI
I tried this for Windows 7, and found that it doesn't work with.Net 4.5. I then installed .Net 3.5, and had to "turn it on" from the control panel. Once I did this, all was well.
Hope this will help someone with similar problems.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i try to open willowtree and it comes up with a message saying willow tree has stopped working.
check online for asolutionandclose the program
close the program
i use windows 7
this is the error i get
Description:
Stopped working
Problem signature:
Problem Event Name: APPCRASH
Application Name: WillowTree#.exe
Application Version: 2.1.0.0
Application Timestamp: 4d4dde6f
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.17651
Fault Module Timestamp: 4e21213c
Exception Code: e0434f4d
Exception Offset: 000000000000cacd
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Please download the latest experimental revision from the experimental files area, extract it to a different folder, and try to run it. It has a more detailed error log that will be much more helpful in determining what your problem is. There isn't enough information provided in this Windows event log for me to diagnose the problem.
http://sourceforge.net/projects/willowtree/files/experimental/
I think the latest version available is 2.2.1.222.
I just noticed that the error log you posted says you are using version 2.1.0.0 The latest release version should report 2.2.1.0 I think. Please make sure you try using the latest release revision if you are having problems.
http://sourceforge.net/projects/willowtree/files/2.2/WillowTree%23-2.2.1.102.zip
Additionally, if you are opening Xbox 360 savegames please check for a replacement for the x360.dll library in the "x360lib" folder as you may need it if WT# crashes at the moment you try to open any Xbox 360 savegame.
http://sourceforge.net/projects/willowtree/files/x360lib/
Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: willowtree#.exe
Problem Signature 02: 2.2.1.0
Problem Signature 03: 502b34c1
Problem Signature 04: WillowTree#
Problem Signature 05: 2.2.1.0
Problem Signature 06: 502b34c1
Problem Signature 07: 5a4
Problem Signature 08: 91
Problem Signature 09: System.TypeInitialization
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
I still can't tell what the problem is with 2.2.1.102, so the suggestion to try the latest experimental revision to get a more detailed exception report stands, though I can see you aren't getting exactly the same error as you were in version 2.1. Something is failing during static initialization of a class, but I can't tell what class or what operation is failing from the log, which is why I created the new exception handling code in the experimental revision.
The most likely problem is improper installation or lack of user access so WillowTree# can't find or operate on one of the files in its Data folder during startup. Typically to install you must extract all the contents of the ZIP file into a folder that the user has both read and write access to, such as a subfolder of My Documents for instance, then run WillowTree#.exe in that folder to use it. If you don't have proper access to one of the files or the folder then the experimental revision will terminate with a file not found exception or unauthorized access exception and list the name of the file that it couldn't access. I'll be able to tell you more when I see the error dump from the new experimental revision. If you can get that to work then WT# 2.2.1.102 should work properly also in general.
FYI
I tried this for Windows 7, and found that it doesn't work with.Net 4.5. I then installed .Net 3.5, and had to "turn it on" from the control panel. Once I did this, all was well.
Hope this will help someone with similar problems.