Render window menu disappears/offset when launching a second rendering #75419

Closed
opened 2020-04-05 20:57:09 +02:00 by Sebastien Larocque · 5 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28

Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: 375c7dc4ca

Short description of error
Render window menu disappears/offset when launching a second rendering.

Exact steps for others to reproduce the error

  • Launch the attached file in Blender. It can also be any file that you create in Blender. As far as I know, this problem has been present for years.
  • Press F12 to launch the first rendering and open the render window at the same time.
  • Press F12 again to launch a second rendering. Sometimes, the problem occurs on the third rendering.
  • At this point, you should see the menu disappearing behind the window’s top bar.

I attached three screenshots demonstrating different characteristics of the problem.

RenderWindow-WindowMode.jpg

  • It is still possible to move the cursor over the menu bar to activate the menu of other buttons, but the visible area is very thin.
  • The menu bar appears to have an offset towards the top.

RenderWindow-Maximized1.jpg

  • The maximized version does not have any menu visible or that appears to have any offset.

RenderWindow-Maximized2.jpg

  • The maximized version on this one shows a “hand” button at the top-right corner. It shows a certain offset. When trying to click on the top of the window in the rendering area, it is still possible to activate certain elements. For example, in this screenshot, the button “Browse Image to be linked” has been clicked. This is why the drop-down menu is shown on this screenshot.

I also noted that the raw screenshots “RenderWindow-Maximized1.jpg” and “RenderWindow-Maximized2.jpg” do not have the same height, although both windows have been maximized. I ignore the reason at the moment.

Notes

When taking the screenshots, I used the Alt + Print Screen button on the keyboard to capture only the window (without the Windows task bar and other parts of the screen). Surprisingly, on the image “RenderWindow-WindowMode.jpg”, we can see the task bar. Normally, we would not see the task bar when capturing only the window with Alt + Print Screen. This information indicates that the rending window area was probably covering the task bar at the bottom, but with transparency. Capturing only the window’s content also captured what was behind the transparent area: the task bar in this case.

Another behavior that might explain the bug is about the fact that when pressing F12 to launch the second rendering, the window is automatically resized. Blender tries to maximize the covered area to nearly the maximum space that the window can occupy on the screen. A suggestion is to avoid resizing the window every time a rendering is launched. It might have something to do with the bug, but I also found this very annoying because this prevents ourselves from setting up our window layout as we would normally do with other windows.

After resizing the render window, if launching another rendering, the menu bar does not disappear. However, the window is resized. Launching another rendering just after (without resizing the window) makes the menu bar disappear.

I use a dual-monitor configuration in case that might influence.

Workaround

  • One way to recover this problem is to use the “Maximize” and “Restore Down” button on the window’s top bar.
  • Double-click the window’s top bar is one simple way to make the menu reappear just after launching the rendering.
  • Clicking on the window’s top bar to move it makes the menu reappear.

Render Window Layout.blend

RenderWindow-Maximized1.jpg

RenderWindow-Maximized2.jpg

RenderWindow-WindowMode.jpg

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28 **Blender Version** Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: `375c7dc4ca` **Short description of error** Render window menu disappears/offset when launching a second rendering. **Exact steps for others to reproduce the error** * Launch the attached file in Blender. It can also be any file that you create in Blender. As far as I know, this problem has been present for years. * Press F12 to launch the first rendering and open the render window at the same time. * Press F12 again to launch a second rendering. Sometimes, the problem occurs on the third rendering. * At this point, you should see the menu disappearing behind the window’s top bar. I attached three screenshots demonstrating different characteristics of the problem. RenderWindow-WindowMode.jpg * It is still possible to move the cursor over the menu bar to activate the menu of other buttons, but the visible area is very thin. * The menu bar appears to have an offset towards the top. RenderWindow-Maximized1.jpg * The maximized version does not have any menu visible or that appears to have any offset. RenderWindow-Maximized2.jpg * The maximized version on this one shows a “hand” button at the top-right corner. It shows a certain offset. When trying to click on the top of the window in the rendering area, it is still possible to activate certain elements. For example, in this screenshot, the button “Browse Image to be linked” has been clicked. This is why the drop-down menu is shown on this screenshot. I also noted that the raw screenshots “RenderWindow-Maximized1.jpg” and “RenderWindow-Maximized2.jpg” do not have the same height, although both windows have been maximized. I ignore the reason at the moment. **Notes** When taking the screenshots, I used the Alt + Print Screen button on the keyboard to capture only the window (without the Windows task bar and other parts of the screen). Surprisingly, on the image “RenderWindow-WindowMode.jpg”, we can see the task bar. Normally, we would not see the task bar when capturing only the window with Alt + Print Screen. This information indicates that the rending window area was probably covering the task bar at the bottom, but with transparency. Capturing only the window’s content also captured what was behind the transparent area: the task bar in this case. Another behavior that might explain the bug is about the fact that when pressing F12 to launch the second rendering, the window is automatically resized. Blender tries to maximize the covered area to nearly the maximum space that the window can occupy on the screen. A suggestion is to avoid resizing the window every time a rendering is launched. It might have something to do with the bug, but I also found this very annoying because this prevents ourselves from setting up our window layout as we would normally do with other windows. After resizing the render window, if launching another rendering, the menu bar does not disappear. However, the window is resized. Launching another rendering just after (without resizing the window) makes the menu bar disappear. I use a dual-monitor configuration in case that might influence. **Workaround** * One way to recover this problem is to use the “Maximize” and “Restore Down” button on the window’s top bar. * Double-click the window’s top bar is one simple way to make the menu reappear just after launching the rendering. * Clicking on the window’s top bar to move it makes the menu reappear. [Render Window Layout.blend](https://archive.blender.org/developer/F8451186/Render_Window_Layout.blend) ![RenderWindow-Maximized1.jpg](https://archive.blender.org/developer/F8451187/RenderWindow-Maximized1.jpg) ![RenderWindow-Maximized2.jpg](https://archive.blender.org/developer/F8451188/RenderWindow-Maximized2.jpg) ![RenderWindow-WindowMode.jpg](https://archive.blender.org/developer/F8451189/RenderWindow-WindowMode.jpg)

Added subscriber: @SebBlender

Added subscriber: @SebBlender

Added subscriber: @Dariusz

Added subscriber: @Dariusz

Added subscriber: @mano-wii

Added subscriber: @mano-wii

This is the same problem identified in #71334 although the steps to reproduce are different.
I will merge the reports. This one can still be used for consultation.

This is the same problem identified in #71334 although the steps to reproduce are different. I will merge the reports. This one can still be used for consultation.

Closed as duplicate of #71334

Closed as duplicate of #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#75419
No description provided.