engine error: internal driver direct3d device?

[sir_frags]

My engine error when game crashes after a few minutes of gameplay:

http://i5.tinypic.com/4pb5wfl.jpg


Any help here guys?

Thank!!!!

[~kev~]

Same problem I am having - exact same error message. Sometimes the game will start and run, after a few minutes it crashes. Sometimes it crashes on start up before the game even loads. Some times I can play without any problems.

My system stats:
Operating System: Windows 2000 Professional (5.0, Build 2195) Service Pack 4
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
Motherboard - ASUS A8N-E
BIOS: Default System BIOS
Processor: AMD Athlon(tm) 64 Processor 3200+, ~2.2GHz
Memory: 1024MB RAM
Page File: 534MB used, 1938MB available
Windows Dir: C:\WINNTPRO
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.0001.0904 32bit Unicode

Results from dxdiag:
------------
DxDiag Notes
------------
DirectX Files Tab: No problems found.
Display Tab 1: No problems found.
Sound Tab 1: The file P17.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
Music Tab: No problems found.
Input Tab: No problems found.
Network Tab: No problems found.

---------------
Display Devices
---------------
Card name: RADEON X800 Series
Manufacturer: ATI Technologies Inc.
Chip type: RADEON X800 GTO (0x5549)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_5549&SUBSYS_03121002&REV_00
Display Memory: 256.0 MB
Current Mode: 1280 x 1024 (32 bit) (60Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: ati2dvag.dll
Driver Version: 6.14.0010.6599 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 1/24/2006 21:52:48, 255488 bytes
WHQL Logo'd: Yes

[Deadly Furby]

Play the game in 800x600. Later, try switching resolutions in game

[sir_frags]

Oh Oh...i'm using the radeon x800 as well. Not a good sign....

I'm in 800X600 though.

[~kev~]

I tried the game at 800X600 and 1280X1024.

I was running the game at 1024X768 when the problem first came up.

At 1280X1024 - I got the same error "engine error: internal driver direct3d device?"

At 800X600 - I got a C++ run time error, R6025 - "Pure Virtual Function Call" and the game crashed.

Oh Oh...i'm using the radeon x800 as well. Not a good sign....

I'm in 800X600 though.

The X800 was and still is a popular card. Even though its an older card, I still see it posted on sharkyforums, and steam forums. Hopefully its not an issue with the card / driver, if it is we can expect a lot more of these post.

[sir_frags]

Ok, here is what I added to my "set launch options" when you right click on the game in Steams Game List.

-dxlevel 80 -heapsize "524288" -mp_decals "100" +mat_forcehardwaresync "0" +snd_async_prefetch_priority "1" +mat_forcemanagedtextureintohardware "0" +mat_specular "0" +r_shadows "0" +mat_bloom "0"

Also, I went into Video Options and turnded Shader and Shadow settings to Low, which is what I have to do to get Half Life 2dm to run on my comp.


I doubt all of you need all that. All I know is my problem has gone away. Also, heapsize is important because the Source engine defaults to 256mb. I have 1gig ram so I set heapzie for 524288 to let the game know I have 1gig instead of 256mb. That is very important too. If you have more than one gig of ram, you need to go google the right heapsize because heapsize is measured in kb and not mb.

Anyway, my problem has not happened at all since I added the above line to my FF game's launch options.


*Frags*

[~kev~]

I doubt all of you need all that. All I know is my problem has gone away. Also, heapsize is important because the Source engine defaults to 256mb. I have 1gig ram so I set heapzie for 524288 to let the game know I have 1gig instead of 256mb. That is very important too. If you have more than one gig of ram, you need to go google the right heapsize because heapsize is measured in kb and not mb.

*Frags*

A valve employee (DougV I think it was) posted in the steam forums - the half life 2 engine ignores the heapsize command. The engine will use the amount of ram it sees fit. Only when you run a 64 bit processor and and a 64 bit operating system with over 4 gigs of ram will the source engine run its best.

And that is from the steam support forums.

http://forums.steampowered.com/forums/showthread.php?t=460359

http://forums.steampowered.com/forums/showthread.php?t=541987

http://forums.steampowered.com/forums/showthread.php?t=577439

http://forums.steampowered.com/forums/showthread.php?t=570696

[sir_frags]

No, that is not correct. Heapsize is not ignored. I can see the change take place in the HL2dm console when I restart the game. It goes from 256 to 512mb in the console when I use this launch option. If I remove it, the console goes back to 256mb. I might have my mb's mixed up now because it's been months since I've tested this, but I am at work now and can't test it.

But no matter what, I know if I do not use the launch options above that my half life2dm game will only run for a few seconds before shutting down. I've tested this time and time again.


*Frags*

[4est]

No, that is not correct. Heapsize is not ignored. I can see the change take place in the HL2dm console when I restart the game. It goes from 256 to 512mb in the console when I use this launch option. If I remove it, the console goes back to 256mb. I might have my mb's mixed up now because it's been months since I've tested this, but I am at work now and can't test it.

But no matter what, I know if I do not use the launch options above that my half life2dm game will only run for a few seconds before shutting down. I've tested this time and time again.


*Frags*


Frags, you may have already done this, but it's worth a try.
http://fortress-forever.com/forum/showthread.php?t=10752