Page MenuHomeFeedback Tracker

Bringing up the inventory on dual monitor setup causes mouse cursor to move outside of the game monitor
Acknowledged, WishlistPublic


When you bring up the inventory with Tab on a dual monitor setup the mouse cursor can be moved off the monitor running the game and onto the second monitor instead of being locked to the game monitor.
This can cause you to click off the game and possibly produce an Alt+Tab effect of minimizing the game to taskbar.
Its also annoying to see my cursor rampaging across my second monitor


Legacy ID
Steps To Reproduce

While in game, Press Tab to bring up the inventory on a PC running dual monitors

Additional Information

I would like to see the mouse cursor locked down to the game monitor to avoid any accidental clicks off the game screen

Event Timeline

Guyver1 edited Steps To Reproduce. (Show Details)Dec 17 2013, 11:33 PM
Guyver1 edited Additional Information. (Show Details)
Guyver1 set Category to Inventory.
Guyver1 set Reproducibility to Always.
Guyver1 set Severity to None.
Guyver1 set Resolution to Open.
Guyver1 set Legacy ID to 79403826.May 8 2016, 2:17 PM
Guyver1 edited a custom field.
KilrBe3 added a subscriber: KilrBe3.May 8 2016, 2:17 PM

Yup noticed this too. It happens pretty much 80% of the time. You gotta drag the mouse all the way over from 2nd monitor back to the game, or it minimizes the game due to you clicked 'outside' of the game.

sala added a subscriber: sala.May 8 2016, 2:17 PM
sala added a comment.Jan 10 2014, 6:45 PM


Phugoid added a subscriber: Phugoid.May 8 2016, 2:17 PM

Just to add. I also play with dual monitors but have not noticed this. Having said that, I use a program called Actual Multiple Monitors (which I recommend if you haven't tried it!)

Yup, confirmed and really frustrating.

behaviour also exhibited when pressing the 'P' key to bring up the player list

Bazim added a subscriber: Bazim.May 8 2016, 2:17 PM
Bazim added a comment.Jan 8 2014, 10:56 AM


Hello everyone,

Thanks for sending in all your feedback regarding this issue. The devs are aware of the problem and are working on fixing it.


Was there ever a fix for this? It's been 11 months since the last post.

There has been no fix so far but the bug is reported internally, so it'll be addressed during development.