Automation Error ,Err.Number=-2005530516,
Members - Reputation: 122
Posted 18 June 2003 - 08:14 PM
Members - Reputation: 1414
Posted 19 June 2003 - 02:18 AM
The easiest way to find out why a D3D call returned an INVALIDCALL error is to let it tell you:
1) Make sure you''re using the DEBUG version of the D3D runtime is installed (you were given the option when you installed the SDK).
2) Make sure that the DEBUG version of the runtime is enabled. Go to the DirectX applet in the Control Panel and look under the Direct3D tab.
3) Whilst in the DirectX control panel applet, increase the debug output level for Direct3D to maximum.
I''ve not used Visual BASIC for over 10 years so I''ve forgotten what debugging support is available and I don''t have it installed on this machine to check... If VB DOES have a debug output window:
4) Run your program and let it fail with the INVALIDCALL error.
5) Now look at all the text in your debug output window. D3D will log information, warnings, and importantly errors to that. It''ll also explain the reason WHY a D3D call has failed.
If VB doesn''t have a simple debug output window:
4) Download and run DebugView from www.sysinternals.com or use the command line debug viewer that comes with the DirectX SDK
5) Run your program and let it fail with the INVALIDCALL error.
6) Now look at all the text in the debug viewer. D3D will log information, warnings, and importantly errors to that. It''ll also explain the reason WHY a D3D call has failed.
Creative Asylum Ltd
Members - Reputation: 127
Posted 19 June 2003 - 07:02 PM
Hope it helps,
Members - Reputation: 130
Posted 20 June 2003 - 10:36 AM
I hope I''ve been useful.
Prog, Sex & Rock''n''Roll :
I don''t like the Prog but the prog likes me.