Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

DarkBASIC Discussion / D3D error, need help!

Author
Message
Bit Rat
19
Years of Service
User Offline
Joined: 3rd Jun 2005
Location: Double Dungeons- dungeon 21
Posted: 25th Mar 2006 01:02
I get an error when trying to place 3d primatives in DB classic

Error:

System Error : Surfaces could not be created. D3D Devices do not support backbuffer bit-depth and HW acceleration.

then DB just exits

Anyone have an idea on how to fix this?

The only thiing I have done recently is update my vid driver and DirectX
OSX Using Happy Dude
21
Years of Service
User Offline
Joined: 21st Aug 2003
Location: At home
Posted: 25th Mar 2006 09:44
Run a DXDiag test - see if that passes.

Bit Rat
19
Years of Service
User Offline
Joined: 3rd Jun 2005
Location: Double Dungeons- dungeon 21
Posted: 25th Mar 2006 11:58
ran dxdiag and all tests passed.
blanky
20
Years of Service
User Offline
Joined: 3rd Aug 2004
Location: ./
Posted: 25th Mar 2006 17:57
What graphics card do you have?

If it's an ATi Rage 3D Pro, you're screwed.

... installing gentoo ...
Bit Rat
19
Years of Service
User Offline
Joined: 3rd Jun 2005
Location: Double Dungeons- dungeon 21
Posted: 25th Mar 2006 23:30
My vid card is an Nvidia Geforce2 GTS chipset (it's a 3 year old card)

one thing i noticed is that when I first get into windows, all of the DXdiag tests run fine, then when I run DBC with some code that creates a primative, DBC will crash to the desktop with no error.
If I try DBC again, That is when I get the error. When I run DXdiag again it says that Directdraw Acceleration and Direct3D Acceleration are not available. Restarting the computer will bring them back however.

So far, all of my other progs that use 3D work fine. I have not tried to reinstall DBC yet, but I have reinstalled DirectX and my vid driver just to be sure they were not the problem. Another thing I have not tried is to go back to my old version of DirectX and vid driver. Does anyone know if DBC 113 is compatable with DirectX 9.0c?
master programmer
19
Years of Service
User Offline
Joined: 30th May 2005
Location: 3D Space
Posted: 25th Mar 2006 23:58
Can you post code on how you put the primitives in? I have basically the same graphics chip and everything works for me

Bit Rat
19
Years of Service
User Offline
Joined: 3rd Jun 2005
Location: Double Dungeons- dungeon 21
Posted: 26th Mar 2006 12:35
I found out what the problem was with my code
I was having it check to see if 800 x 600 x 16 was available and if it was set the display to 800 x 600 x 16

it was at the beginning if the program. I removed it and now my code works again. Now I don't know how to fix that problem
below is the code I used for setting the display mode

c= check display mode(800,600,16)
if c=1 then set display mode (800,600,16)

any suggestions?
master programmer
19
Years of Service
User Offline
Joined: 30th May 2005
Location: 3D Space
Posted: 28th Mar 2006 08:57
I don't usually mess with the display mode, so I'm not 2 sure.

As for graphics cards, I checked again, I have ATI Rage 3D Pro, and it works just fine with DarkBASIC.

Pincho Paxton
22
Years of Service
User Offline
Joined: 8th Dec 2002
Location:
Posted: 28th Mar 2006 09:30
DB Classic crashes if you set the display mode twice. So your code is probably setting it twice.

c= check display mode(800,600,16)
if c=1 then set display mode (800,600,16)

Bit Rat
19
Years of Service
User Offline
Joined: 3rd Jun 2005
Location: Double Dungeons- dungeon 21
Posted: 13th Apr 2006 02:04
The only place I had the code change the display mode was at the very beginning of the code and nowhere else

I even made a test program that would only change the display mode (no other code whatsoever) and it will still crash to the desktop.

I really think that DB just hates the updated vid driver

Login to post a reply

Server time is: 2025-05-23 18:45:45
Your offset time is: 2025-05-23 18:45:45