at .BuildFomodFromSource(String p_strPath, NexusAPI p_nxaNexus) at (String p_strPath) at _Click(Object sender, EventArgs e) at .RaiseEvent(Object key, EventArgs e) at .OnClick(EventArgs e) at .HandleClick(EventArgs e) at .FireEventInteractive(EventArgs e, ToolStripItemEventType met) at .FireEvent(EventArgs e, ToolStripItemEventType met) at .PerformClick() at (EventArgs e) at (MouseEventArgs mevent) at .WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at .WndProc(Message& m) at .WndProc(Message& m) at .WndProc(Message& m) at .ControlNativeWindow.OnMessage(Message& m) at .ControlNativeWindow.WndProc(Message& m) at.
System.NullReferenceException: Object reference not set to an instance of an object. "Thursday, Janu11:24:20 PM Fomm 0.13.21 OS version: Microsoft Windows NT Service Pack 1 Whether it's a server capacitance issue or a ploy by NM to get users to buy access to their premium servers matters not.Įdited by MasterObserver, 15 January 2014 - 03:30 PM.It gave me this crash report. I've had maybe 2 successful logins in NMM, all other attempts failed thanks to server issues. NMM even says so upon attempting login, essentially: "Could not reach blah blah server." The application's inability to connect to NM's servers is another issue entirely though At least NMM traps the error appropriately.įrom my experience, the inability to connect to their servers is a natural DoS. Turning the options off is a workaround but it shouldn't be necessary A patch should be released. This is poor error handling on the developer's part, plain and simple.ĪLL object oriented programming languages have the capacity to catch exceptions and deal with them appropriately. I mean, after that crash happens I can just go back into the package manager and activate the mod but it. Is failing, and thus the object that should be returned after successful execution is not. Did you install the FORK Fallout Mod Manager. The method of the object being executed: _LoginKey() The object in question is part of an API used in FOMM to login to NM. It's the combination of a connectivity issue with NM's servers and poor coding.Įxamining the crash dump reveals that the error occuring is a pointer referencing a NULL object.
0 kommentar(er)
