X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=README.markdown;h=685f221c13a0c4c9c74eb7af672ac4db6b636620;hb=54300ebabd931085b2ef12edfef2e8ddd8c709dc;hp=c82149545f474e90b5e3135214470da0ab7a0ebd;hpb=db82d4062fd73362be2ceb66068720cab2814a74;p=apitrace

diff --git a/README.markdown b/README.markdown
index c821495..685f221 100644
--- a/README.markdown
+++ b/README.markdown
@@ -18,7 +18,7 @@ Obtaining **apitrace**
 ======================
 
 To obtain apitrace either [download the latest
-binaries](https://github.com/apitrace/apitrace/downloads) for your platform if
+binaries](http://apitrace.github.com/#download) for your platform if
 available, or follow the instructions in INSTALL.markdown to build it yourself.
 On 64bits Linux and Windows platforms you'll need apitrace binaries that match
 the architecture (32bits or 64bits) of the application being traced.
@@ -241,6 +241,13 @@ Then run the application as usual.
 You can specify the written trace filename by setting the `TRACE_FILE`
 environment variable before running.
 
+For D3D10 and higher you really must use `apitrace trace -a DXGI ...`. This is
+because D3D10-11 API span many DLLs which depend on each other, and once a DLL
+with a given name is loaded Windows will reuse it for LoadLibrary calls of the
+same name, causing internal calls to be traced erroneously. `apitrace trace`
+solves this issue by injecting a DLL `dxgitrace.dll` and patching all modules
+to hook only the APIs of interest.
+
 
 Emitting annotations to the trace
 ---------------------------------