collider.x = FlxG.mouse.x - cursor.width / 2;collider.y = FlxG.mouse.y - cursor.height / 2;From what I understand, the actual cursor image used to do that before native cursor were supported. Since I don't just want to display an image under the cursor, but also doing collision etc on it, is there anything that I can do to make the collider sprite act the same as the native cursor image? I've tried looking into FlxMouse, but I can't seem to get the exact x/y of the native cursor from there, only the old cursor system (hence the "lag").
(it's working just fine on windows btw)
Thanks :)
- In general, the responsiveness of display object cursors are sluggish. In comparison, native mouse cursors look and perform better when the user interacts with an application.