Alright, so far I've got the "disabled" misterious issue twice. And both times I forgot and simply went to check the settings, the plugin restarted and things when back to normal. But, I finally cought in a savestate a reproducible scenario where it's enabled when it shouldn't.
This is after a clean start of PCSX2:
http://i.imgur.com/yuXqF.jpg
After a pause and resume:
http://i.imgur.com/SMRq3.jpg
And here's some log (I also have a PIX with both screenshots too if necessary)
Code:
GSDX: 0 0 0 0 0 4 0 1 0 0 0 0 0 0 0 0
GSDX: 00 13
GSDX: 0 1 1 0 1 0 1 5 1 0 0 0 1 0 0 0
GSDX: 0 1 1 0 1 0 1 2 1 0 0 0 1 0 0 0
GSDX: 00 1B
GSDX: 00 1B
GSDX: 00 13
GSDX: 00 1B
GSDX: 00 13
GSDX: 00 13
GSDX: 00 13
GSDX: 00 13
GSDX: 00 13
GSDX: 00 13
GSDX: 02 13 *
GSDX: 1 0 0 0 1 0 1 5 1 0 0 0 1 0 0 1
GSDX: 1 0 0 0 1 0 1 2 1 0 0 0 1 0 0 1
GSDX: 1 0 0 0 1 0 1 1 1 0 0 0 1 0 0 1
GSDX: 02 13 *
GSDX: 02 13 *
GSDX: 02 13 *
GSDX: 02 13 *
GSDX: 02 13 *
GSDX: 00 1B
GSDX: 00 13
GSDX: 02 13 *
GSDX: 02 13 *
GSDX: 02 13 *
GSDX: 02 1B *
GSDX: 1 0 0 0 1 0 1 1 0 0 0 0 1 0 0 1
GSDX: 1 0 0 0 1 0 1 1 0 0 0 0 0 0 0 1
GSDX: 00 1B
GSDX: 0 1 1 0 1 0 1 1 0 0 0 0 1 0 0 0
GSDX: 00 1B
GSDX: 00 13
GSDX: 00 1B
GSDX: 00 13
GSDX: 00 13
GSDX: 00 13
GSDX: 00 1B
GSDX: 00 1B
GSDX: 1 0 0 0 1 0 1 1 1 0 0 0 0 0 0 0
GSDX: 00 2C
GSDX: 00 24
GSDX: 00 24
GSDX: 00 24
-------------------------------------
GSDX: 0 0 0 0 0 4 0 1 0 0 0 0 0 0 0 0
GSDX: 00 1B
GSDX: 0 1 1 0 1 0 1 1 0 0 0 0 1 0 0 0
GSDX: 00 1B
GSDX: 00 13
GSDX: 00 1B
GSDX: 00 13
GSDX: 00 13
GSDX: 00 13
GSDX: 00 24
GSDX: 1 0 0 0 1 0 1 1 0 0 0 0 0 0 0 0
GSDX: 00 24
GSDX: 00 24
GSDX: 00 1B
GSDX: 00 1B
GSDX: 1 0 0 0 1 0 1 1 1 0 0 0 0 0 0 0
GSDX: 00 2C
GSDX: 1 0 0 0 1 0 1 1 0 0 0 0 1 0 0 0
The log format is the entire MACRO array that's about to be passed on to the pixel shader (Dx11), with the last bit being the spritehack. The short one, is just TEX0 CPSM and TEX0 PSM from the TextureCache with those having the * being the mix that triggers the hack. The line is the point when I pause and resume.
It shows that effectively, the hack ain't triggered uppon resume and that's because some textures stop being tagged as CPSM 0x2. So, if the same happens but backwards it should be that issue of "hack seems disabled on startup, but enables on pause resume". I hope Gabest takes a look a this. =S
On the bright side, I guess I cought your mysterious bug naoan! =D