Jump to content

Object Reference Not Set to an Instance of an Object- PkNX


Recommended Posts

I've been trying to get PkNX to run so I can randomize my LGE/LGP games all night and cannot seem to get it to work. I have the ExeFs and RomFs of both games dumped. LGE ExeFs and RomFs are dumped into a folder titled 'LGE,' which has > RomFs, ExemFs inside, RomFs with 27,818 files and 1,336 folders. The LGP is in similar fashion. I load the folder with PkNX and it gives me an error that states that the 'object reference not set to an instance of an object,' followed by this:

 

Spoiler

 

System.NullReferenceException: Object reference not set to an instance of an object.
   at pkNX.Game.GameFileReference.Get(String basePath)
   at pkNX.Game.GameFileMapping.GetFile(GameFile file, Int32 language)
   at pkNX.Game.GameManagerGG.Initialize()
   at pkNX.Game.GameManager..ctor(GameLocation rom, Int32 language)
   at pkNX.Game.GameManager.GetManager(GameLocation loc, Int32 language)
   at pkNX.WinForms.Controls.EditorBase.GetEditor(String loc, Int32 language)
   at pkNX.WinForms.Main.OpenFolder(String path)
   at pkNX.WinForms.Main.Menu_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.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3056.0 built by: NET472REL1
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
pkNX
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/Harley/Downloads/pkNX_Build_-_VS_0.1.0_167_artifacts/pkNX%200.1.0/pkNX.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.3056.0 built by: NET472REL1
    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
----------------------------------------
pkNX.Structures
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/Harley/Downloads/pkNX_Build_-_VS_0.1.0_167_artifacts/pkNX%200.1.0/pkNX.exe
----------------------------------------
pkNX.Game
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/Harley/Downloads/pkNX_Build_-_VS_0.1.0_167_artifacts/pkNX%200.1.0/pkNX.exe
----------------------------------------
pkNX.Containers
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/Harley/Downloads/pkNX_Build_-_VS_0.1.0_167_artifacts/pkNX%200.1.0/pkNX.exe
----------------------------------------

************** 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:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

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.

 

 

As you can expect, I'm getting extremely frustrated. I don't know what I'm doing wrong or how to fix it, and there's little help available aside from posting this. I am using the latest 1.67 build of PkNX as well. I'm running the correct NET framework and everything as well. This is also on a Windows x64bit. Everything should be working fine?

Link to post
Share on other sites

@hmash15 you've already made this post before, no need to make another one. I'm hiding the old one, and leaving this one up.
If you don't get responses, do not repost this again, alright?

Now patiently wait for people with expertise relating to your problem to reply you.

Also, I saw the previous one and did not reply it, as well as not answering your question on this one, because simply, I don't know.
I never had issues with pkNX, and I don't recognize what issue you have. If everybody came to this thread and said "I don't know" to you, it'll be a very busy thread with no concrete information offered XD

 

Link to post
Share on other sites

I'm sorry! I realized I posted it under the wrong board, and thought it might be better if I posted it under the right one so someone could delete the old one so it didn't clutter. My sincerest apologies!

  • Proud 1
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...