Mouse seems to get locked to the wrong window position

[Greywhind]

I've had an MCE for Lord of the Rings Online (copied and modified from the World of Warcraft one) working on one computer. I moved it over to another machine with a dual-screen setup on Windows 7, and when windowed or full-screen, it seems to repeatedly place the boundaries where the mouse can move/can't move in the wrong place. Re-centering the mouse changes where the boundaries are, but seems to lock them to the top-left corner of the screen instead of to the actual position of the window in windowed mode. Switching to freelook (with the right upper trigger) seems to move the boundaries in some manner that I can't figure out.

MCE is attached - please let me know if anyone has an idea why this might be happening.

Thanks!

[Danny]

You either need to remove from the mouse_pointer

<lock_relative_cursor_to_window>true</lock_relative_cursor_to_window> or set it to false

or change
<sync_relative_to_absolute>false</sync_relative_to_absolute> to true

[Greywhind]

Hm... <lock_relative_cursor_to_window> was already set to false in the above .mce file, and I tried removing it entirely, but it didn't change anything.

I also tried setting <sync_relative_to_absolute> to true, and that didn't seem to change anything either.

After each change, I quit and re-started the MotionCreator 2 application, and re-scanned.

[Danny]

Ah right I see it now. If you enable slide_sides on a relative cursor I currently clamp the cursor to the window. I do need to revisit this and see if if that can be optional. Try using an absolute pointer instead of a relative pointer if you don't want the pointer to slide sides.

[Greywhind]

Hm. slide_sides was already set to false, but changing <absolute> to true seems to allow the mouse to move freely. Thanks.

[Greywhind]

I take it back. Setting <absolute> to true fixes it for a while, but then something happens (not sure what yet) and it starts locking the mouse into regions of the screen again. Quitting and restarting MotionCreator seems to temporarily fix it again.

[Danny]

You just uncovered a bug. SetMouseModeAction needs to set the wand back to absolute if coming from the other modes (which we force to be relative). If you remove the last two bindings (Hold To Freelook, Release To Mouselook) it should work fine.

[Greywhind]

I managed to work around this by adding

<mouse_toggle_absolute>
<mode>absolute</mode>
</mouse_toggle_absolute>

into the last <binding> <name>Release To Mouselook</name> section.

Thanks for the help!

[Greywhind]

Hi - sorry to bring back this old thread, but I think there may be a legitimate bug here that hasn't yet been addressed.

Prior to updating my computer to MotionCreator 2 Beta Build 2306 (I think that's the version I first saw this in?), a single-monitor machine using this MCE (without the "sync_relative_to_absolute" positioning or anything) certainly had no problems with the cursor suddenly being locked to a portion of the screen after switching back from freelook mode, but ever since updating (including to the newest version), this seems to happen even on my single-monitor setup. I have to push the "recenter mouse" button to get it to return to allowing the entire screen.

Can you double-check this? I think the behavior has changed in the last two or so versions, and that this is a bug.

[Danny]

What game/mce should I test?

I tested your oringal mce you posted again and made the modifications I talked about. I didn't add your set absolute action becuase that wsa fixed when you reported this earlier. The attached mce seems to work fine in Windows. I don't have the game installed but I can check it out if it still has issues. Can you share the mce you are using please?