Page 1 of 1

Entity Error

Posted: Tue Jun 06, 2006 7:02 pm
by Deathkindler
When I use Entity's SBSP viewer i get this error, i tried redownloading, that did nothing. It does it with every map, so i think i might be missing a file.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
Error in the application.
-2005530518 (D3DERR_NOTAVAILABLE)
at Microsoft.DirectX.Direct3D.Device..ctor(Int32 adapter, DeviceType deviceType, Control renderWindow, CreateFlags behaviorFlags, PresentParameters[] presentationParameters)
at entity.BSPViewer.InitializeGraphics()
at entity.BSPViewer.Main()
at entity.BSPViewer..ctor(BSPModel tempbsp, Map& mapz)
at entity.MapForm.rawEditorToolStripMenuItem_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
----------------------------------------
entity
Assembly Version: 1.0.2311.435
Win32 Version: 1.0.2311.435
CodeBase: file:///C:/Documents%20and%20Settings/Jake/Desktop/Entity%20Alpha%201/entity.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
----------------------------------------
Microsoft.DirectX
Assembly Version: 1.0.2902.0
Win32 Version: 5.04.00.2904
CodeBase: file:///C:/Documents%20and%20Settings/Jake/Desktop/Entity%20Alpha%201/Microsoft.DirectX.DLL
----------------------------------------
Microsoft.DirectX.Direct3D
Assembly Version: 1.0.2902.0
Win32 Version: 9.05.132.0000
CodeBase: file:///C:/Documents%20and%20Settings/Jake/Desktop/Entity%20Alpha%201/Microsoft.DirectX.Direct3D.DLL
----------------------------------------
Microsoft.DirectX.Direct3DX
Assembly Version: 1.0.2903.0
Win32 Version: 9.04.91.0000
CodeBase: file:///C:/Documents%20and%20Settings/Jake/Desktop/Entity%20Alpha%201/Microsoft.DirectX.Direct3DX.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 Jun 07, 2006 1:46 pm
by l Homestar l
Yeah, I get the same error. Anyone care to help us?

Posted: Thu Jun 08, 2006 8:16 am
by jkjk
several other people do too. i have the latest directx also.

Posted: Thu Jun 08, 2006 7:25 pm
by soccerplay99
same with me it shows tells me that directcd has a prouble dont know what to do

Posted: Thu Jun 08, 2006 10:48 pm
by Net_Slayer
same here but no prob wiv directx

Posted: Sat Jun 10, 2006 1:59 am
by jzimmer09
you need to update ur grafix driver... thast wat i had 2 do.... and i fixed it

Posted: Sat Jun 10, 2006 2:53 am
by Net_Slayer
no help at all my grafix card works perfectly fine...
honest
>_>
..|_
\__/

<_<
..|_
\__/

>_>
..|_
\__/

Posted: Sat Jun 10, 2006 10:53 am
by jlddodger
D3DERR_NOTAVAILABLE

This error stands for (Direct3D Not Available), so either you driver is out-of-date, your directx is out-of-date, or your computer is just generally screwed. I get this error when trying to load BSP Viewer over remote desktop, and I know that that is D3D related.

Don't be so sure about your computers. Check again.

Posted: Sat Jun 10, 2006 11:00 am
by Trigger_six
jlddodger wrote:D3DERR_NOTAVAILABLE

This error stands for (Direct3D Not Available), so either you driver is out-of-date, your directx is out-of-date, or your computer is just generally screwed. I get this error when trying to load BSP Viewer over remote desktop, and I know that that is D3D related.

Don't be so sure about your computers. Check again.
Not Direct 3d. The Direct3D Driver of yours is old. Heres proof. I have No direct x(the program, not the driver) on my laptop. And it still works.

Posted: Thu Jun 15, 2006 8:57 am
by jkjk
hmm, guess i gotta chk my graphics card driver (it's a e-machine)

Posted: Thu Jun 15, 2006 9:22 am
by Monkey Terd
jkjk wrote:hmm, guess i gotta chk my graphics card driver (it's a e-machine)
I have a 3 year old E-machines with 512 ram and everything works just fine :? .

Posted: Fri Jun 16, 2006 8:29 am
by jkjk
Hmm. mine's from 01.