展示显示栈与采集链之间的空隙,思路可迁移到屏幕采集检测设计。
绕过反作弊逆向
Quote:
Originally Posted by
X0V
after ripping my hair out for a solid 24hrs+ the ideal scenario i decided was to just create a pseudo display that mirrors a monitor & have nvidia capture the pseudo
i used iddcx to create the pseudo & set your primary display to the pseudo as well just for an ex.
Code:
UmdfService
=
IddSampleDriver
,
IddSampleDriver_Install
UmdfServiceOrder
=
IddSampleDriver
UmdfKernelModeClientPolicy
=
AllowKernelModeClients
[
IddSampleDriver_Install
]
UmdfLibraryVersion
=
$UMDFVERSION$
ServiceBinary
=%
12
%
\UMDF\IddSampleDriver
.
dll
UmdfExtensions
=
IddCx0102
Code:
hr
=
interop
->
CreateForMonitor
(
virt
.
mon
,
winrt
::
guid_of
<
winrt
::
Windows
::
Graphics
::
Capture
::
IGraphicsCaptureItem
>(),
winrt
::
put_abi
(
item
));
if
(
FAILED
(
hr
)
||
!
item
)
Fatal
(
L
"we failed."
,
hr
);
auto
pool
=
wgc
::
Direct3D11CaptureFramePool
::
CreateFreeThreaded
(
winrtDevice
,
winrt
::
Windows
::
Graphics
::
DirectX
::
DirectXPixelFormat
::
B8G8R8A8UIntNormalized
,
2
,
item
.
Size
());
auto
session
=
pool
.
CreateCaptureSession
(
item
);
session
.
IsCursorCaptureEnabled
(
true
);
the purpose is essentially:
game frames -> pseudo display -> nvidia captures
overlay -> physical display -> completely streamproof(different scope essentially)
and ofc this is assuming that we're talking ab nvidia monitor capture & your overlay is external & not drawn into a swapchain you thats captured lol...
ex: iddcx-objects
https://learn.microsoft.com/en-us/wi.../iddcx-objects
& ge9's iddSampleDriver
Wont this just confuse windows aswell if setting idd as primary display