23 Apr
2014
23 Apr
'14
8:59 a.m.
Am 23.04.2014 um 09:15 schrieb Christopher Thielen christopher@thielen.co:
Once the cursor data is loaded from bitmap16.flx to a heap, I never see a reference to that memory again, at least in an API trace. After various initializations, there are a lot of CreateTexture calls followed by LockRect ... UnlockRect. From reading around online, my guess is the game uploads textures using memcpy() while the rect is locked. Can anyone who knows a bit more about D3D confirm that's a probable method of uploading textures?
Correct. This is a common way to load textures. There are others, but they all involve LockRect and UnlockRect at some point.