[BUG] Disabling Mouse Unhooking does not work in v4

[hmm-norah]

Ashita Version v4.0.0.2

FFXI Version (Type /version in-game to get this.) version 30190305_0

Windows Version (ie. Start > About Your PC) Windows 10 Pro 21H1 build 19043.1237 Experience Pack 120.2212.3530.0

Describe The Bug When mouse.unhook is set to 0, the mouse will jump to a menu when opened like you'd expect, but moving the mouse at all shows that it's actually back where it originally was. Hardware mouse is not enabled, and no plugins or addons are installed. Using /ashita, I can verify that mouse.unhook is off.

Steps To Reproduce

1. set mouse.unhook = 0
2. open configuration on the title screen or something else in game where the mouse jumps to an open window
3. move mouse, it should retain where it was originally when you would expect it to be where the new menu opened up.

Screenshots

https://user-images.githubusercontent.com/696702/136287482-8f3e74a4-00df-4dd1-bddf-f904728b64b2.mp4

Additional Information

• This was tested with the menu resolution matching the game resolution and when set to something larger
• Running on the WingsXI private server
• This did function correctly in Ashita v3

Please let me know if I can add anything else!

[atom0s]

This is due to a side effect of v3's setup. The way v3 handles hooking onto the Direct3D device and windowing the game is old and outdated at this point. The official client has its own windowing mode now which v4 makes use of. So what you're seeing is a side effect of what happened from before with how things were handled.

v3 forces two of the settings in the configuration editor to a set value regardless of what the user wishes to use. That being:

• 0021 - Hardware Mouse - v3 sets this to 1 always. (Meaning hardware mouse is always on.)
• 0034 - Windowed Mode - v3 sets this to 0 always. (Meaning fullscreen mode is always on.)

The same setup can be achieved on v4 doing the same thing though, if you set your configurations to have hardware mouse on and use fullscreen mode.

But now in proper Windowed modes, the snapping will only happen if you have the hardware mouse option disabled. This is how the client is supposed to operate.