I am aware of an inversion in the Y-axis... if you look carefully at the snapshot of code above, you will notice a "640 - Mouse.Y" instead of a "Mouse.Y" being used. I have always wanted to implement shaders that follow wherever your mouse goes regardless of whatever layerscale you are currently on. But there are some... issues with Construct 2 code.
Trust me, I have tried explaining before but to no avail. Hopefully, Ashley can see what we mean soon, or at least give us shader effect developer guidelines. I don't want to have to live through another "Adele Dazeem" type of reply. Guess, he's rather busy atm with multiplayer. So let him be. (- I need multiplayer too)
Take a look my existing code. It's seems to be working fine in the version that I released.