🔒 Locked

D3D9 Runtime Error

Started by KitsuneStrife May 5, 2004 at 4:46 PM 15 replies 1.4k views

Original Post

May 5, 2004 at 4:46 PM

Microsoft.DirectX.Direct3D.InvalidCallException /*********************************************************/ ... private Device device = null; ///

/// We will initialize our graphics device here ///

public void InitializeGraphics() { // Set our presentation parameters PresentParameters presentParams = new PresentParameters(); presentParams.Windowed = true; presentParams.SwapEffect = SwapEffect.Discard; // Create our device /* Error Here */ device = new Device(0, DeviceType.Hardware, this, CreateFlags.SoftwareVertexProcessing, presentParams); } ... /*********************************************************/

circlesoft

101

circlesoft

May 5, 2004 at 5:55 PM

What about all the other presentation parameters that you need to set?

KitsuneStrife

Author

KitsuneStrife

May 5, 2004 at 6:51 PM

I did what I was told to do in a book, and it doessnt work, so please explain, I''m new to DX.

KitsuneStrife

Author

KitsuneStrife

May 5, 2004 at 10:49 PM

Here is a screenshot:
http://strife.fox.50megs.com/cgi-bin/i/error.JPG

Muhammad Haggag

156

Muhammad Haggag

May 6, 2004 at 6:21 AM

Do you have the debug dx runtime? If not, install it so that you get debug output, which will tell you exactly what's wrong (edit: You might want to check the forum FAQ).

The problem you encountered is that there's a wrong parameter in your Presentation parameters - something that your card doesn't support, it seems. Unfortunately, I don't know what presentation parameters is initialized to by default.

Muhammad Haggag,
Optimize
Bitwise account: MHaggag -

[edited by - Coder on May 6, 2004 7:23:49 AM]

DrunkenHyena

May 6, 2004 at 3:25 PM

Most samples for MDX try to show off how much less code you need by depending on defaults, but they rarely do a good job of stating what needs to be set and when.

My advice is the same as in Unmanaged DX, set all of the members of your PresentParameters. Then you always know what you''re setting. Even better, make sure you understand WHY you''re setting them and WHAT you''re setting them to.

Stay Casual,

Ken
Drunken Hyena

KitsuneStrife

Author

KitsuneStrife

May 10, 2004 at 1:37 PM

ARGH!!! I tried to set the setting according to what some of the examples included with the SDK, but I''m still getting the error.
Would it help if I got a new graphics card? DOH! I''m on a notebook, I cant upgrade the graphics. Oh well, it was a good dream while it lasted.

Muhammad Haggag

156

Muhammad Haggag

May 10, 2004 at 3:31 PM

quote:
Original post by KitsuneStrife
ARGH!!! I tried to set the setting according to what some of the examples included with the SDK, but I'm still getting the error.
Would it help if I got a new graphics card? DOH! I'm on a notebook, I cant upgrade the graphics. Oh well, it was a good dream while it lasted.

Never despair. What's your card type? Fire up DirectX Caps Viewer (Under DXSDk\Utilities), save the D3D caps into a file, and either post it here enclosed with [ source ][/ source ] tags (without the spaces between the square brackets and "source"), or mail it to me.

Have you installed the debug runtime? If you don't understand what I'm talking about, read the forum FAQ, and if not there yet, send me an email.

Muhammad Haggag,
Optimize
Bitwise account: MHaggag -

[edit]Clarification

[edited by - Coder on May 10, 2004 4:34:59 PM]

DrunkenHyena

May 10, 2004 at 3:33 PM

If you set up the debug runtime it would tell you why it''s failing.

Do any of the SDK samples run? If not then your card may not support DX9.

Stay Casual,

Ken
Drunken Hyena

KitsuneStrife

Author

KitsuneStrife

May 11, 2004 at 11:23 AM

My graphics specs for my notebook:
AGP-enabled Intel® ® 815EM graphics chip with up to 11 MB video SDRAM (shared) and 3Dgraphics support and Intel''s Dynamic Video Memory Technology

I will post the CAPS later today.

And yes, the samples work in full-screen, but when I Alt+ENTER, they crash.

KitsuneStrife

Author

KitsuneStrife

May 11, 2004 at 5:41 PM

http://dew.mg2.org/coligna/dxview.log

[edited by - KitsuneStrife on May 11, 2004 6:42:13 PM]

Alvarny

May 11, 2004 at 7:17 PM

If the samples crash when in windowed mode theres a problem. Have you tried reinstalling Direct X?

KitsuneStrife

Author

KitsuneStrife

May 11, 2004 at 9:27 PM

Yes, on several occasions.

Muhammad Haggag

156

Muhammad Haggag

May 12, 2004 at 11:15 AM

Sample-crashing means you have a driver bug, most probably. Do all the samples crash on mode-switching, or just the managed ones?

Try changing your app to run in full-screen (i.e Windowed = false)

Muhammad Haggag,
Optimize
Bitwise account: MHaggag -

KitsuneStrife

Author

KitsuneStrife

May 13, 2004 at 11:38 AM

I tried making my app to go full screen, but it didnt change my resolution of the screen, and it still gave the error. Is there another thing I need to do other than changing it to "presentParams.Windowed = false;"?

Supernat02

May 13, 2004 at 12:07 PM

I think you also have to set the width and height parameters to valid values when running full screen (i.e. 800x600, 1280x1024, etc).

Chris

Muhammad Haggag

156

Muhammad Haggag

May 13, 2004 at 3:34 PM

quote:
Original post by KitsuneStrife
I tried making my app to go full screen, but it didnt change my resolution of the screen, and it still gave the error. Is there another thing I need to do other than changing it to "presentParams.Windowed = false;"?

Do the managed samples work? If they do, modify the code of anyone to write the presentParams to a file, and check that one for some working parameters.

Muhammad Haggag,
Optimize
Bitwise account: MHaggag -

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.