Search Issue Tracker
Duplicate
Votes
5
Found in
4.3.0a3
Issue ID
556409
Regression
No
Player Settings - some options under 'Resolution and Presentation' do not work
Specifically 'Default is Full Screen' and 'Default Is Native Resolution'. Neither seems to have any effect on the outputtet build. Instead it seems like it "remembers" the last settings you chose when you exported with the display resolution dialog turned on.
To repro:
- Export a PC build with display resolution dialog enabled. Select 'Windowed' and run the the game
- Now delete all build data. Export again but with 'Default is full screen' checked and display resolution dialog disabled. Observe that the game is still running in Windowed mode.
Similarly the 'Default is native resolution' option has no effect on what can be selected in the display resolution dialog.
Comments (3)
-
265lutab
Oct 03, 2015 19:15
I'm also having this problem. Would love if there was some fix for this.
-
bunCBG
May 23, 2015 16:07
On OS X 10.10.3 with Unity 5.0.1f1, if "Default is Full Screen" and "Default is Native Resolution" are checked, and there is no player preference file, the player launches in full screen but at 1024 x 768 px. I am working with an iMac 27" and it should be 2560 x 1440 px.
-
Timelog
Mar 05, 2015 20:39
Currently running Unity 5.0 And I still have this very annoying issue.
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
- SearchColumn of type "ObjectReference" does not get refreshed for the custom SearchProvider when lighting generation finishes
- LogWarning is not executed in the HDRP package script when running the project in -batchmode
- Freeze on DynamicHeapAllocator::InitializeMemoryRegion when entering Play mode in a specific scene
- Memory usage rises when switching scenes with GRD enabled and a loaded texture in URP
- [Quality Hackweek] Terrain Brush Size value is not serialized after deselecting the terrain when using the first instance of multiple Inspectors
This is a duplicate of issue #569314