Well, this issue is probably the most difficult one. "Internal Driver Error" - that's the worst feedback Direct3D can give me!! Still checking manuals and stuff...
Well, this issue is probably the most difficult one. "Internal Driver Error" - that's the worst feedback Direct3D can give me!! Still checking manuals and stuff...
Yeah, that's really bad. I hope you will find something.
Remember that the Pixels-property worked well in PowerDraw3pre with same hardware and also DirectX 9.0c installed. If you access the Pixels the same way it could be a bug in your coding. If you do it another way maybe it's within drivers or DirectX.
<a href="http://www.greatgamesexperiment.com/game/Valgard/?utm_source=gge&utm_medium=badge_game"><img border="0" alt="GGE" title="GGE" src="http://static.greatgamesexperiment.com/badge/game/valgard/gge400x56.png"></a>
I've updated the sources - it should fix some issues related to antialiasing (now it's updated whetever you change the video device, use Alt+TAB or switch between full-screen and windowed mode).
Check it on http://turbo.gamedev.net/asphyre.asp
Bookmarks