Render Topbar is missing after several renders in New Window mode #57654

Closed
opened 2018-11-06 18:00:01 +01:00 by Antonio Vazquez · 10 comments

Windows 10

  1. Open default scene
  2. Be sure render is in New Window mode
  3. Press F12
  4. New window is created with topbar
  5. Press F12 several times, the topbar is offset outside of the view (reset when move the window)

I have seen that the problem is only if the window is greater than monitor size. If the output window fit in monitor, the topbar is fine always.

Example:
image.png

Windows 10 1) Open default scene 2) Be sure render is in New Window mode 3) Press F12 4) New window is created with topbar 5) Press F12 several times, the topbar is offset outside of the view (reset when move the window) I have seen that the problem is only if the window is greater than monitor size. If the output window fit in monitor, the topbar is fine always. Example: ![image.png](https://archive.blender.org/developer/F5410536/image.png)
Author
Member

Added subscriber: @antoniov

Added subscriber: @antoniov
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Cant seem to be able to reproduce... (topbar is always there and in place)

  • How do you enforce the window to be greater than the monitor size? (I've set render dimension to 4k but still only get a maximized window matching my monitor size)
  • anything else I could be missing?
Cant seem to be able to reproduce... (topbar is always there and in place) - How do you enforce the window to be greater than the monitor size? (I've set render dimension to 4k but still only get a maximized window matching my monitor size) - anything else I could be missing?
Author
Member

I have two monitors of 1680 x 1050.

I set the render output to new window with a resolution of 1080p,

Render the image and put the new window in the second monitor. Only then if you render again get the errror (having the new window in secondary monitor)

If you render in the main monitor, just when you try to see the window and use the mouse, the mouse event fire the refresh and gets the topbar.

@lichtwerk I'm not sure what do you think, but this is a so small problem that we could close the bug and if get worst reopen it again (we have too many things to do now to spend time in things like this). What do you think?

I have two monitors of 1680 x 1050. I set the render output to new window with a resolution of 1080p, Render the image and put the new window in the second monitor. Only then if you render again get the errror (having the new window in secondary monitor) If you render in the main monitor, just when you try to see the window and use the mouse, the mouse event fire the refresh and gets the topbar. @lichtwerk I'm not sure what do you think, but this is a so small problem that we could close the bug and if get worst reopen it again (we have too many things to do now to spend time in things like this). What do you think?
Member

I'd keep it open (one more on the giant pile wont hurt), I'll set it to Normal an add User Interface, maybe someone picks it up, otherwise can be revisited later...

I'd keep it open (one more on the giant pile wont hurt), I'll set it to `Normal` an add `User Interface`, maybe someone picks it up, otherwise can be revisited later...

Added subscriber: @iss

Added subscriber: @iss

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'
Richard Antalik self-assigned this 2020-02-11 00:54:20 +01:00

This has been reported, but I can not find report to merge this

This has been reported, but I can not find report to merge this
Author
Member

Closed as duplicate of #71334

Closed as duplicate of #71334
Author
Member

Fixed in #71334

Fixed in #71334
Sign in to join this conversation.
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
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#57654
No description provided.