DXGK_GLITCH_EFFECT - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// d3dkmddi.h
typedef enum _DXGK_GLITCH_EFFECT {
DXGK_GLITCH_EFFECT_SYNC_LOSS,
DXGK_GLITCH_EFFECT_GARBAGE_CONTENT,
DXGK_GLITCH_EFFECT_STALE_CONTENT,
DXGK_GLITCH_EFFECT_BLACK_CONTENT,
DXGK_GLITCH_EFFECT_DEGRADED_CONTENT,
DXGK_GLITCH_EFFECT_SEAMLESS
} DXGK_GLITCH_EFFECT;
View the official Windows Driver Kit DDI referenceNo description available.
Enumeration which describes the user visible effect of a glitch during a SetTimingsFromVidPn call.
DXGK_GLITCH_EFFECT_SYNC_LOSSIndicates that the display connected to the target lost sync due to a glitch. Even a short sync loss will likely lead to the user seeing a black screen while the display device re-syncs.
DXGK_GLITCH_EFFECT_GARBAGE_CONTENTIndicates that garbage content was sent to the display connected to the target due to a glitch. Garbage content will be very noticeable to a user.
DXGK_GLITCH_EFFECT_STALE_CONTENTIndicates that stale content was sent to the display connected to the target due to a glitch. Display of stale content would cause the affected pixel area to appear frozen.
DXGK_GLITCH_EFFECT_BLACK_CONTENTIndicates that black content was sent to the display connected to the target due to a glitch. If the content was black, as would be the case when initializing the display, this will be imperceptible; otherwise it is likely that black content will be noticeable to a user.
DXGK_GLITCH_EFFECT_DEGRADED_CONTENTIndicates that degraded content was sent to the display connected to the target due to a glitch. Degraded content would include pixels which are too bright or too dim or which are displayed using a slightly different color space than intended. Short durations would likely go unnoticed.
DXGK_GLITCH_EFFECT_SEAMLESSIndicates that there was no user visible glitch.