Open HalfWayLambda opened 6 years ago
Looks like the NET Framework stuff is a Red herring, the part that get my attention is : at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) at LibModMaker.Steam.InstalledApps() at LibModMaker.SourceMod.GetSDKPath(String RootFolder, String SDKVersion)
ModMaker is sniffing your Steam install to locate where the Source SDK is installed an putting the apps it finds into a dictionary. Looks like it's putting something into the dictionary that the dictionary cannot cope with causing the crash.
Multiple copies of the the same app maybe?
Alright, so here's more of them; Trying to open up the FGD Editor gives an exception error window saying "Object reference not set to an instance of an object", and the rest of the details are as follows:
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
** Exception Text ** System.NullReferenceException: Object reference not set to an instance of an object. at LibModMaker.ForgeGameData.BaseClassRead(String CommandLine, FGDReader Source, EntityTypes EntityType) at LibModMaker.ForgeGameData.Load(String FileName) at ModMaker.FGDForm.frmFGD_Load(Object sender, EventArgs e) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form.OnCreateControl() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.Form.WmShowWindow(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
** JIT Debugging ** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled.
For example:
When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
Furthermore, If I go to the Weapon Editor, then to the HUD Graphics tab and click on any of the 3 dots (...) inside the boxes, they all give the same error, which is this:
"Object reference not set to an instance of an object"
Details: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
** Exception Text ** System.NullReferenceException: Object reference not set to an instance of an object. at ModMaker.frmTextureData.set_Game(SourceMod value) at ModMaker.TextureDataControl.btnEdit_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
** JIT Debugging ** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled.
For example:
When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
And...3rd error is when I try and go to Localization. This time it mentions that "Could not find any resources appropriate for the specified culture or the neutral culture (wat?). Make sure "ModMaker.LocalForm.resources" was correctly embedded or linked into assembly "ModMaker" at compile time, or that all the satellite assemblies required are loadable and fully signed". Ok I think that has something to do with Steam. Here's the details of it:
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
** Exception Text ** System.Resources.MissingManifestResourceException: Could not find any resources appropriate for the specified culture or the neutral culture. Make sure "ModMaker.LocalForm.resources" was correctly embedded or linked into assembly "ModMaker" at compile time, or that all the satellite assemblies required are loadable and fully signed. at System.Resources.ManifestBasedResourceGroveler.HandleResourceStreamMissing(String fileName) at System.Resources.ManifestBasedResourceGroveler.GrovelForResourceSet(CultureInfo culture, Dictionary`2 localResourceSets, Boolean tryParents, Boolean createIfNotExists, StackCrawlMark& stackMark) at System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo requestedCulture, Boolean createIfNotExists, Boolean tryParents, StackCrawlMark& stackMark) at System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents) at System.Resources.ResourceManager.GetObject(String name, CultureInfo culture, Boolean wrapUnmanagedMemStream) at System.Resources.ResourceManager.GetObject(String name) at ModMaker.LocalForm.InitializeComponent() at ModMaker.LocalForm..ctor() at ModMaker.LocalizationTool.Launch(SourceMod Game) at ModMaker.ModView.HelperList_ItemActivate(Object sender, EventArgs e) at System.Windows.Forms.ListView.OnItemActivate(EventArgs e) at System.Windows.Forms.ListView.WmReflectNotify(Message& m) at System.Windows.Forms.ListView.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
** JIT Debugging ** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled.
For example:
When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
These are all the errors I have so far.
Every time i try and launch ModMaker.exe, a "Microsoft .NET Framework" error pops up with quite a lot of information about it. Here's what it says:
"Unhandled exception has occured in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately. An item with the same key has already been added."
If I click continue, Mod Maker opens but...it only shows the top part of it with the sourcemods that i currectly have installed. If I click on one of these the same Microsoft .NET Framework pop up again. Now the interesting part is that this error has a "Details" box which I think shows what causes this problem. It's quite a long one as well, but it can probably be very useful. Let me also mention that i'm using Microsoft's Windows 10, version 1803 (OS Build 17134.165), which is the latest version with all the important updates installed. This error has showed up in the past too however. Here's what the details box says:
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
** Exception Text ** System.ArgumentException: An item with the same key has already been added. at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource) at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) at LibModMaker.Steam.InstalledApps() at LibModMaker.SourceMod.GetSDKPath(String RootFolder, String SDKVersion) at LibModMaker.SourceGame.get_SDKPath() at ModMaker.ModView.set_Options(KeyValues value) at ModMaker.MainForm.ShowMod(SourceMod SMod) at ModMaker.MainForm.ShowMod(String Name) at ModMaker.MainForm.ShowVProject() at ModMaker.MainForm.frmMain_Load(Object sender, EventArgs e) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form.OnCreateControl() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.Form.WmShowWindow(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
** Loaded Assemblies ** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.7.3131.0 built by: NET472REL1LAST CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
ModMaker Assembly Version: 2.0.0.0 Win32 Version: 2.0.0.0 CodeBase: file:///C:/Users/Half%20Way%20Lambda/Downloads/ModMaker_V2/ModMaker.exe
System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.7.3056.0 built by: NET472REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System Assembly Version: 4.0.0.0 Win32 Version: 4.7.3056.0 built by: NET472REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.7.3056.0 built by: NET472REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.7.3056.0 built by: NET472REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.7.3110.0 built by: NET472REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.7.3056.0 built by: NET472REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
LibModMaker Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Users/Half%20Way%20Lambda/Downloads/ModMaker_V2/LibModMaker.DLL
SevenZipSharp Assembly Version: 0.64.3890.29348 Win32 Version: 0.64.3890.29348 CodeBase: file:///C:/Users/Half%20Way%20Lambda/Downloads/ModMaker_V2/SevenZipSharp.DLL
TargaImage Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Users/Half%20Way%20Lambda/Downloads/ModMaker_V2/TargaImage.DLL
** JIT Debugging ** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled.
For example:
When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
My guess is that the .dll files that Windows 10 uses for the Microsoft .NET Framework are unable to properly cooperate with how the program works.