vrecan said:
ANTI-DETECT-MODE fights against shader and texture specific optimisations <--- is the part that is the most interesting to me. Cant wait to see what will come of this.
Anti-Detect-Mode works on both vertex and pixel shaders. How it works:
first version:
-insert NOP instruction
PRO's: worked on r3xx vpu's
CON's: errors on NV3x vpu's
second version:
- insert/double instructions which don't do any harm to the shader result
PRO's: worked on all vpu's
CON's: more instructions, slower shaders and/or going beyond shader instruction limit
third version(used in ShaderMark v2.0):
- shuffle some instructions on a random base, which have no needed order for execution
- shuffle R register's, like r1 to r3 on a random base
PRO's: worked on all vpu's
CON's: may be easy to detect by driver coders
So the ADM will be modified in future versions/updates of ShaderMark v2.0 in order to have some impact. It's a race....
Regards,
Thomas