high cpu usage

[hoborg]

From google:

INVALIDCALL usually means that either a parameter you've passed to D3D is invalid or an operation you've requested isn't possible.

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, download and run DebugView from http://www.sysinternals.com or use the command line debug viewer that comes with the DirectX SDK

[Reddwarf]

From google:

INVALIDCALL usually means that either a parameter you've passed to D3D is invalid or an operation you've requested isn't possible.

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, download and run DebugView from http://www.sysinternals.com or use the command line debug viewer that comes with the DirectX SDK

Most people does not install the complete SDK, just the runtime part.

[striben]

I have this error too here, but i have only stupid Intel Atom with intel GPU here. Home i have ATI GPUs and there is no problem.
Can i ask what GPU do you have?

It's a pretty old AOpen i915Ga-HFS motherboard, and I am just using the on-board Intel 82915G/GV/910 Express Chipset Family (that's what device manager calls it). It is just to be used as a recording-machine, so it is not that big problem for me. When I had WinXP installed I could run all "dxdiag"-tests without errors. (dxdiag doesn't seem to have the same test-routines in Win7).

[hoborg]

So it looks like it is connected to intel integrated GPU, mine is "Intel® 82945G Express Chipset Family (i945G0)"

Maybe there is some missing D3D feature?