[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    Re: Advice fixing #13683 (DirectX mouse overlay?)
From:       Christopher Thielen <christopher () thielen ! co>
Date:       2014-04-27 0:24:03
Message-ID: 535C4E23.9010405 () thielen ! co
[Download RAW message or body]

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=F6singer wrote:
>
> Am 23.04.2014 um 09:15 schrieb Christopher Thielen <christopher@thielen.c=
o>:
>> 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 i=
nitializations, there are a lot of CreateTexture calls followed by LockRect=
 ... UnlockRect. From reading around online, my guess is the game uploads t=
extures 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 the=
y all involve LockRect and UnlockRect at some point.
>


[prev in list] [next in list] [prev in thread] [next in thread]