Search Issue Tracker
Fixed in 5.2.1
Votes
3
Found in
5.2.0f2
Issue ID
722983
Regression
Yes
[DX11] Full screen with low resolutions renders incorrectly
This issue has no description.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph Memory leak when calling the ClearPropertyBinders and AddRemoveVFXProperty
- Entering "Configure Avatar" inside the Inspector locks it
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
- Scene View with Debug Draw Mode enabled is gray when GPU Resident Drawer is enabled
- The UI is not visible when resizing out of focus built Player window with Application.runInBackground set to false
CGDever
May 02, 2017 20:14
What???, not cool! You can still see this bug in 5.6.0. 5.2.1->5.6.0... How can I make games without settings ????
mm.dacampo
Dec 09, 2015 10:46
I don't know if you have the same issue as mine but I just fixed my full screen scaling issue by forcing "Exclusive Mode" for D3D9 & D3D11 in the Player Settings Inspector (accessible from the Build Settings window). I'm using Unity 5.2.0.
sascha_be
Oct 23, 2015 13:39
Also still seeing this issue in 5.2.1. Reloading or loading a different the scene after calling SetResolution seems to go around the issue for now. It is a bothersome and inefficient solution though...
RogDolos
Oct 05, 2015 08:05
SetResolution seems entirely broken with 5.2. Still occurring with 5.2.1.
montyfi
Oct 03, 2015 10:29
5.2.1p1 - Issue is still there
daggada2
Oct 03, 2015 03:18
This is marked fixed, but I don't believe that to be true. I'm seeing all kinds of problems when transitioning betwee resolutions & full screening with 5.2.1f1. This issue definitely should NOT be closed. I'm tempted to open a new issue.
Stardog
Sep 30, 2015 23:11
Still broken in 5.2.1p1, and has nothing to do with DX11.
WaaghMan
Sep 28, 2015 10:30
Still not fixed in 5.2.1p1
Vincent-Virtual-IT
Sep 24, 2015 08:13
5.2.1f1 doesn't correct this bug...
Xentor609
Sep 23, 2015 12:39
Still not fixed in 5.2.1f1....