Cursor lock to screen center

[Lymex]

Hi guys, so I've recently changed to a new laptop, from Windows 8 to Window 10.

As the title suggests, my cursor isn't locking to the center of the screen during gameplay. This is for windowed and borderless window, since it gives me better performance.

The cursor is locked within the window itself, but if I move my mouse fast enough (which I do, since this is an FPS) then I can end up clicking outside the game window. I also end up clicking on the border itself, so instead of shooting, nothing happens when I click after making quick turns.

This didn't happen with my old laptop, so I'm wondering if this was an issue with Windows 10 or just a new Depth update. As I said, cursor is locked within the window, but can I lock it to the screen centre instead?

[BabyCat]

Hey RunningAway,

I believe there is a bug with the game engine we use (Unreal 3) which causes this problem and we unfortunately can't really fix. For me personally, I only have the problem occur when I have two or more applications running that use DirectX. For example, two games; Depth and Photoshop; etc. When you only have Depth open on your PC (No Web-browser, etc. just Depth) do you still have the problem?

Having a quick look online, it looks like there may be some mouse locking application you could run to help with this problem. I haven't used any before, so unfortunately I can't recommend anything...

Hopefully we can figure a solution out!

[Lymex]

1. Tried closing all other applications and running Depth, no success.
2. Tried mouse locking applications: Cursor Lock, AutoHotKey. Both no success.

Most of the solutions online seem to deal with locking the mouse within the program itself (which Depth already achieves), or issues with multiple monitors (but I'm using a single monitor so no problems there).

Anyway one problem I foresee with external applications locking the cursor to the center, is that I wouldn't be able to move the cursor in the main menu or weapon loadout screens, so it won't be much of a solution either.

I had assumed this issue was a programming or scripting "feature" of the game that could be solved by the devs, although I don't know any coding so I can't say. If this is a bug in the engine itself, then it seems I'm out of luck.