If you make a standalone build and start it in fullscreen with a lower than native resolution, there is a black bar on the bottom and the rest of the picture is squished upwards.
Doesn’t happen if you set Standalone Player Options - D3D11 Fullscreen Mode to Exclusive Mode, but that of course makes you crash if you alt-tab.
Windowed mode works, but if you alt-enter, the picture will be squished in vertical space and right edge will be cut off.
Yup, same issue here.
i reported something about this issue in more detail to the Unity team.
lets hope this will be fixed fast.
Same issue here, tried on several pc with windows 10, 8.1 and 7.
In some cases I had to change the playerprefs settings I used to set the resolution (default is Screen.NativeResolution) because it rendered at something like 301x213
Unless it’s futile, screenshot? I will have to test this.
We have the same issue here, when selecting a new resolution in-game in our option screen. In Exclusive mode we get an all-white screen when trying to switch resolutions. Hope this gets fixed soon.
dito, for me its blue like my background ^^ I remember a similar problem on Unity 4.3/4.6 and it got fixed with 5.0 if i remember right.
but as i said, i reported this issue with a 5.2 Exampleproject and a 5.0.2 Exampleproject to show that the issue was not existing in 5.0.2 
Lets hope they will fix this issue as fast as possible.
Same here. Is there issuetracker filled already? Please link it so we could bump.
Not funny, I can’t build anything…
Same problem here, can someone add this to issuetracker pls?
Good News for everyone,
this issue is addressed and will be fixed in 5.2.1, just got a reply from the QA Team minutes ago, that this issue was already found in 5.2.0f1
Kind regards
good to know, thanks!
Lets just hope 5.2.1 will be there asap.
Looks like I am going to have to update the 3rd time this week then! (Depends if 5.2.1 comes out fast enough!)
Yikes. Ran into this last night and have been trying today to fix it, then I thought wait a second, is this just a Unity bug? And… yup. Not fun.
has anyone found a solution?
Other than switch to DX9 or use Exclusive mode, no, but apparently the 5.2 patch to fix the issue’s on it’s way… Hopefully for those DX11 folks, it’s coming soon.