RC2 is now available: http://www.textadventures.co.uk/blog/20 ... ndidate-2/

I have had a problem with this. I got this error on opening a game:

Error launching game: Object reference not set to an instance of an object

Now the error may well be in my game (I know there is a problem somewhere), however, after that trying to edit something else, or trying to click on the cross in the topright corner I got this:

System.NullReferenceException: Object reference not set to an instance of an object.
   at AxeSoftware.Quest.EditorController.Uninitialise()
   at AxeSoftware.Quest.Editor.CloseEditor(Boolean raiseCloseEvent)
   at AxeSoftware.Quest.Main.Main_FormClosing(Object sender, FormClosingEventArgs e)
   at System.Windows.Forms.Form.OnFormClosing(FormClosingEventArgs e)
   at System.Windows.Forms.Form.WmClose(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)

The only way to terminate was through task manager.

ETA: Having gone back to RC1, I have found that the error in my code was a missing }

I'll update the RC tomorrow to fix that "Object reference not set to an instance of an object" error when closing.

Do you always get that error when you have a missing "}" character?

It happened repeatedly for that one error. I did not try other files and other errors efore uninstalling.

The build has now been updated - if you're running the older one you should be notified that a newer version is available. Redownload RC2 to fix the error above.

Just updated the build again as my earlier fix may not have quite fixed the exception in all cases (silly copy and paste error). Latest version is now uploaded, 5.0.4239.31339.

I think you may still have a memory leak. My adventure in 94 KB as the XML files; Quest is currently using 951 MB of RAM, and has hung. Still seems to be when going from code to GUI.