Quote:Original post by nullptr
First-chance exception at 0x1026ed6a in xxx.exe: 0xC0000005: Access violation writing location 0xe2963854.
Unhandled exception at 0x1026ed6a in xxx.exe: 0xC0000005: Access violation writing location 0xe2963854.

What is the value of kLockRect.pBits when you get that access violation (So I can tell how far that address is from the lock)? And what size is the texture, what format, and what RECT are you locking with?

Sorry, forgot to mention that apart form being terribly slow and apprently not supporting cubemaps in a feasable way, the reference rasterizer works fine.
Have no access to full details right now (will do, promise) but the pBits pointer is just a handful of a bytes away, the texture is a 512x256 D3DFMT_A8R8G8B8, the rect can be something like 20,20 to 40,40. Also tried locking the whole surface, same result,
so I blame it on texture trashing (got messages about MRU texture being removed as well).