Same issue here!

Same issue for me... :-(

There's also this issue

http://issuetracker.unity3d.com/issues/standalone-inconsistent-direct3d-behavior-with-non-native-resolution-on-fullscreen-builds

which I believe is related.

The 5.1.3 patch 3 from 11 September should include a fix for that:

(722983) - Fixed broken positioning of render when upscaling to native desktop resolution in full screen mode (Direct3D 9 and Direct3D 11).

But for example a 4:3 game is still stretched to fit a 16:10 desktop resolution in D3D11 full screen mode and the mouse position is still incorrect. It seems nothing has changed in that regard.

Same issue here. NOT fixed in 5.2 despite the "Duplicate issue" claiming its fixed.

Same problem on Unity 5.2.
I use NGUI for my project, and you ?

Same problem here, with Unity 5.1.2f1.

I've had this issue for awhile now with the uGUI (months it seems). I'm currently using Unity 5.1.1p1 and the issue is still there. Please fix!

I'm somewhat surprised this is even a problem for a game engine, considering buttons being detected properly on a user interface (in fullscreen mode) is essential to about 99% of games I've seen. Resolution and GUI issues using dx11 in Unity has been a terrible experience up to this point.

Having the same problem here, a quick fix would really be nice. For now I just limited the resolution to only allow 16:9, but that's no option to stick with.

This problem plays and I and friends.
And in the last fifth version, and 4.6.7f1

So I pushed a bit for an answer and got this:

Alex Lian: "Not a 5.2 specific feature and pushing for ETAs/schedules isn't assisting us in any way.

In checking on things for 704405:

1. It's been noted as a input issue internally, and being marked duplicate of another bug

http://issuetracker.unity3d.com/issues/full-screen-input-dot-mouseposition-output-does-not-match-the-displayed-view-on-the-screen

2. This input issue is marked fixed, though not clear in landing in which build/release.
May not make 5.2 final build, but possibly a patch-release."

According to the roadmap, 5.2 final is scheduled for Sept 8th. And then a patch release after that, so that could be over a month from now.

In the meantime you'll have to work around the issue by e.g.:

- offering only exclusive mode
- disabling the resolution dialog and adapting to the user's aspect ratio through code
- or just forcing it to 16:9 and ignoring the problems with the other aspect ratios