VBGamer

Hmm. Could be. But what about 2D? The primary surface in question doesn't init whether it's a D3D render target or not. I can't even get as far as the code that loads textures (or sprites in 2D) because apperantly I'm out of video memory just because of the primary surface. If the card hogs a bunch of vidmem for textures even while running 2D directdraw stuff, I can unequivically state that's the stupidest fucking thing I've ever heard, and it needs to be fixed - Now!! Who's fault would that be? Microsoft or the lovely people at SiS (Speed is Slow) who wrote my shitty vidcard drivers? Or maybe it's me. I hope it is, 'cuz I can at least correct myself... p.s. - I don't mean to rag on SiS or anything but-.... Hey, wait, yes I do! SiS, you suck!! Go to hell! :-)