Seemingly excessive delay between mouse input switching from camera to menu cursor when menus are opened
- Is the problem OpenMW specific or does it also happen in vanilla Morrowind?
Specific
- What is your operating system?
SteamOS (linux)
- What version of OpenMW are you using? If you used a bleeding edge build, state the exact revision used.
Problem exists in 0.47 and 0.48
- What version of Morrowind are you using (i.e. retail CD or Steam)? What addons (Tribunal, Bloodmoon) do you have installed? What language is your Morrowind install?
Steam, Tribunal and Bloodmoon.
- Do you use any mods? If so, does the problem also occur in a clean vanilla install without any mods?
No mods.
- What are the exact steps to reproduce the problem?
- What did you expect to happen? What happened instead?
Okay, got a really weird one for you. Steam input allows you to bind a series of commands to an input, including delays. It also has 'move mouse to position' as a command. This allows you to do nifty stuff like my idea: a single button that:
- presses Spacebar (opens the container you are looking at)
- wait 500ms
- sends a mouse position command to move the mouse to the location of the "Take All" button
- wait 500ms
- sends a mouse click to click that button
This is where it gets weird. First of all, those waits shouldn't need to be that long, but this problem seems to exist no matter how long you delay which makes absolutely no sense.
When you look at a container and press the button, 1 executes, opening the container. After that? Nothing happens. The mouse cursor doesn't move. So, out of confusion, you close the container, and as you exit the menu, your camera snaps down and to the right.
The camera is somehow receiving the mouse position command instead of the cursor, even 500ms after we open a menu screen! (edit: to be clear, the mouse position command is sent with the menu still open, but the camera doesn't update until you close the menu--even if you keep the menu open for a long time, move stuff around, etc. when you close the menu the camera snaps--so it's definitely the camera receiving the input while the menu is open).
Interestingly, this is not true in reverse. If you press the button when the menu is already open, the menu closes (from the spacebar command), and then 500ms later your camera dutifully snaps down-right (as opposed to the cursor getting the command).
Another confounding detail: Sometimes, it works correctly. Sometimes, very rarely, it the mouse position will correctly be sent to the cursor instead of the camera. However, when it does, the left click is never received, no matter how long after I send it.
Eager to hear your thoughts. I'm guessing there's something tricky going on with camera vs. cursor receiving mouse input, but I can't imagine how the game could be sending the inputs to the wrong one...
EDIT: What's really puzzling about this is, as far as the game is concerned, there's just 3 different buttons being pushed. AFAIK, steam input is a full abstraction layer between the controller and the game--the game should not be aware of the macro button being pressed, only of the 3 buttons getting sent. Yet somehow the game is behaving differently--somehow when the macro button is initially pressed, it is getting stuck on the 'non-menu context' even after we have switched to the 'menu context'. Very bizarre.