Advice fixing #13683 (DirectX mouse overlay?)

[Christopher Thielen]

Do you know of a method to watch texture load like this? I am able to 
find the spot in the executable where the cursor resource is loaded into 
a heap (and the address of that heap in the running process), but I am 
unable to link it to any particular texture create call. Perhaps there's 
a debugger which watches for memory access at certain locations?

On 4/23/2014 1:59 AM, Stefan Dösinger wrote:
>
> Am 23.04.2014 um 09:15 schrieb Christopher Thielen <christopher at 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.
>