mirror of
https://github.com/Echelon9/cxbx-shogun.git
synced 2025-04-02 10:41:47 -04:00
5eacc2892d
git-svn-id: https://cxbx.svn.sourceforge.net/svnroot/cxbx/branches/private/shogun/wip@155 587435c2-1f12-0410-b34b-ee784db558a2
26 lines
1,002 B
Text
26 lines
1,002 B
Text
Direct3D resources are going to be a little bit of a hack.
|
|
There is a tough situation, because precompiled resources
|
|
(XPR) can be loaded into memory manually by an Xbox Game,
|
|
and then "Registered" with pResource->Register(addr);
|
|
|
|
This is a problem because we never have an opportunity to
|
|
intercept the "this" pointer for this datatype. The base
|
|
resource class looks like this:
|
|
|
|
DWORD Common;
|
|
DWORD Data;
|
|
DWORD Lock;
|
|
|
|
The first idea is to tuck away the PC Direct3D resource
|
|
pointer inside of pResource->Data. The trouble with this
|
|
is that some Xbox Games will directly access and modify
|
|
this member.
|
|
|
|
Another technique is to hide the PC Direct3D resource pointer
|
|
inside of the buffer allocated by Data. This could work, as
|
|
long as Xbox Games do not access the resource Data after the
|
|
initial Register function is called.
|
|
|
|
The currently used method is to tuck the pointer away inside
|
|
of the Lock member, and hijack any functions that attempt to
|
|
access the Lock member variable.
|