Blender UI not taking full screen on launch #60650
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#60650
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Mac Mojave
Graphics card: see attached system info.txt
Blender Version
Broken:
version: 2.80 (sub 35), branch: blender2.8, commit date: 2018-12-03 23:39, hash:
1b6a394d86
, type: Releasebuild date: 2018-12-04, 01:09:28 - Just checked & this bug is still active on latest nightly build of Jan 19 too.
platform: Darwin
Short description of error
Starting blender on Mac laptop and the UI does not fill the app window. Please see the attached screenshot.
Also, try to click around in that black empty area to use the UI and highlight things on the small area. It's really wierd. It makes 2.8 unusable on the laptop. When I switch to a big screen, the UI snaps to the bigger window and is "fixed." Thus, it is only possible to work in 2.8 when I'm tethered to the bigger monitor.
Exact steps for others to reproduce the error
Could not find this in the list of open or closed bugs. Hope it is helpful.
system-info.txt
Added subscriber: @snakeblade
Added subscriber: @WilliamReynish
Cannot reproduce that here.
Can you please try with an up to date build? Always test with the latest build, otherwise we will keep getting bug reports for things that were already fixed.
Thanks.
Hi William - yes, just tested on latest nightly build - Jan 19th available today and it's still happening.
Does not happen when I use app on big monitor. Happens whether I have attached monitor or not.
Yes, laptop is retina
External monitor is detached
Monitor is beyond retina
Running with defaults yes
Thanks for replying so quickly too. You all are awesome. Please see attached. I am also checking forums on Discord too. Thanks again. I am a UX person so am happy to help test 2.8.
system-info2.txt
Well, I can't reproduce it here - I have a 13.3" 2017 Macbook Pro without touch bar. For reference, which exact model are you on? The system-info doesn't tell us that.
Does resizing the window, or going to full screen mode fix the issue?
Thanks, again, sometimes it will randomly snap into the right size, but it hasn't done so in the last 20 restarts of Blender. I've restarted the machine too.
I am going to try another way to reproduce when I get to my studio in 20 minutes or so. I have a late 2015 13.3", obviously no touch bar, but everything works great. I have max memory - largest specs for this work too.
Checking Discord forums for others with the same issue too. I'm a UX person so also happy to help.
Thanks for the info, but might be hard to solve if we can't reproduce. May to specific to a specific GPU.
You you keep resizing the window, see if it will then snap to the correct size.
Ok, you are correct. This is a scaling and resolution issue between the monitors. The confusing part is that it happens on the laptop when I am not attached to the bigger monitor. To review:
Both displays are running at default. However, this big monitor is older than I thought: its max resolution is 1920 x 1200.
Here is what happens when I am in the studio attached to the big monitor.
So, this may be an issue for a small number of users and I realize you can't fix it if you cannot reproduce it. I build software too. Thanks for helping me troubleshoot the problem. Now I know what to do if I want to work on the laptop after I leave the studio. ;-)
Yes, I suspected it could be an issue with two monitors with different retina-ness. Blender may become confused in this case.
It could also be an issue that happens because Blender is trying to relaunch to a state where it thinks it will go to your external display, but because it's disconnected, it scales wrongly on your built-in display. Something like that.
It still does look like a bug, but as you say, one that seems to appear if you are using a specific hardware setup. I'll leave this report open for now - perhaps other developers can test with this kind of setup to try and reproduce it.
Closed as duplicate of #57069