Pointer Tool Error
Posted: Wed Apr 12, 2006 10:03 pm
Hello everyone. Me an a friend are having trouble with Pointer Tool. We are getting the following error after we open a map:
What is the problem?
What is the problem?
HaloMods "Classic" Read-only Archive
Visit remnantmods.com for more information
http://www.halomods.info/
Pointer Tool Error
Page 1 of 1
Posted: Wed Apr 12, 2006 10:40 pm
does this happen before or after you add the new bsp to the map?
Posted: Wed Apr 12, 2006 10:47 pm
After. I have clicked on the Details button if it helps you. Here is the content tihin details:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentOutOfRangeException: Non-negative number required.
Parameter name: value
at System.IO.FileStream.set_Position(Int64 value)
at Raw_Concat.Form1.loadBsp()
at Raw_Concat.Form1.openMapToolStripMenuItem_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.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
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.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.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: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Pointer Tool v3
Assembly Version: 3.0.0.0
Win32 Version: 3.0.0.0
CodeBase: file:///C:/Documents%20and%20Settings/Owner/Desktop/Pointer%20Tool%20v3/Pointer%20Tool%20v3.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.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:
<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.
Posted: Wed Apr 12, 2006 10:50 pm
Delete this post pelease.
Posted: Wed Apr 12, 2006 11:07 pm
Very sorry for the double post. I wonder how that happened...
Posted: Thu Apr 13, 2006 5:42 am
You probably should have just edited the second post, cause now you just did a triple 
. As to the program, I have no idea what's causing that.
. As to the program, I have no idea what's causing that.Posted: Thu Apr 13, 2006 2:40 pm
Anyone?
Posted: Fri Apr 14, 2006 8:19 am
I tried to help him but whenever I tried to open any map not just an edited one or anything i would get that error.
Posted: Fri Apr 14, 2006 9:07 am
Yeah guys im trying to do the shared bsp to coag conversion with shades and silenced deaths tuts. I have a problem after i save my work in HEX workshop. I just pasted the new bsp then saved. I try to open up my new coag in Shades pointer tool, and i get an error that says:
Unhandled exception.....blah blah
Non-negative number required.
Parameter name: value.
Then i wanted to try fixing the magic shades way in DM but the map wont open there either. Can someone tell me whats going on cuz i'd like to get past this step. thanks
t_mann05
also you guys might get answers on this page--->
http://files.halomods.com/viewtopic.php ... sc&start=0
Unhandled exception.....blah blah
Non-negative number required.
Parameter name: value.
Then i wanted to try fixing the magic shades way in DM but the map wont open there either. Can someone tell me whats going on cuz i'd like to get past this step. thanks
t_mann05
also you guys might get answers on this page--->
http://files.halomods.com/viewtopic.php ... sc&start=0
Posted: Fri Apr 14, 2006 4:43 pm
If you already added the bsp to the map, its normal, don't worry. Just hit continue and you're fine.
Posted: Sat Apr 15, 2006 8:20 am
i also get that error and im using the same tut as them. i doubt it would be normal because the pointer tool doesnt show any of the map info such as the BSP Size , BSP Magic, Offset etc.