Node Editor hotspots misaligend when displaying same nodes in two monitors with different WIndows Scaling Settings #86466

Closed
opened 2021-03-10 23:41:17 +01:00 by Duarte Farrajota Ramos · 6 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: Dual GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72
Two monitors with different windows Scalingsettings each connected to a different GPU

Blender Version
Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-03-10 04:47, hash: 70e73974b5
Worked: Unknown, I don't think this ever worked correctly
Tested under 2.92 and 2.83 LTS, both affected by the issue.

Short description of error
When displaying two windows with the same node editor (Shaders, Compositing or Geometry Nodes) in two windows each on different monitors with different Windows Scaling settings, the node "hotspots" (for dragging, resizing or connecting sockets) on the original window in the main monitor become misaligned with their visual representation, rendering them hard to use.

Exact steps for others to reproduce the error

  • Open a new Node Editor (for Materials, World Shaders, Compositing or Geometry Nodes, doesn't matter)
  • Add some example nodes, doesn't matter which
  • Shift-Drag from a corner of the current node editor to create a new window
  • Drag new window to a different monitor with different scale setting, while maintaining the same node tree as the original window

Now the "hotspots" (areas to trigger mouse actions like dragging to move, socket triggers for dragging, selection etc.) of the original node editor in the main monitor become offset from the visual representation of the nodes, rendering them hard to use.

  • This only seems to happen if both monitors use different Scale and Layout settings under windows Display Settings (right-click on the desktop, under Display settings > Scale and layout > Change the size of text, apps, and other items), one of the monitors uses 100% the other was at 125%
  • The bug only manifests if the two node trees are displaying the same type of tree (Shaders, Compositing or Geometry Nodes)
  • The bug only manifests if the two node editors are on different monitors
  • Closing the secondary window or moving it back into the main windows monitor cancels the effect.
  • Only the main window ever seems affected, the secondary window remains working as intended in any of the monitors
  • Setting both monitors to have scaling at 100% seems to avoid the issue

See the following screen capture, it is not obvious in the video, but the recording was captured midway between the two system monitors, the blue background is Window desktop wallpaper on the second monitor and represents the boundary between two screens, while Blender's main window was full screen on the main monitor.
NodeBug.mp4

This is probably related to #85628, I have the same issue if I try to open a window in the secondary monitor, throwing an "Unsupported graphics card, need OpenGL 3.3 error".

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: Dual GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72 Two monitors with different windows *Scaling*settings each connected to a different GPU **Blender Version** Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-03-10 04:47, hash: `70e73974b5` Worked: Unknown, I don't think this ever worked correctly Tested under 2.92 and 2.83 LTS, both affected by the issue. **Short description of error** When displaying two windows with the same node editor (Shaders, Compositing or Geometry Nodes) in two windows each on different monitors with different Windows Scaling settings, the node "hotspots" (for dragging, resizing or connecting sockets) on the original window in the main monitor become misaligned with their visual representation, rendering them hard to use. **Exact steps for others to reproduce the error** - Open a new Node Editor (for Materials, World Shaders, Compositing or Geometry Nodes, doesn't matter) - Add some example nodes, doesn't matter which - Shift-Drag from a corner of the current node editor to create a new window - Drag new window to a different monitor with different scale setting, while maintaining the same node tree as the original window # Now the "hotspots" (areas to trigger mouse actions like dragging to move, socket triggers for dragging, selection etc.) of the original node editor in the main monitor become offset from the visual representation of the nodes, rendering them hard to use. - This only seems to happen if both monitors use different Scale and Layout settings under windows *Display Settings* (right-click on the desktop, under *Display settings > Scale and layout > Change the size of text, apps, and other items*), one of the monitors uses `100%` the other was at `125%` - The bug only manifests if the two node trees are displaying the same type of tree (Shaders, Compositing or Geometry Nodes) - The bug only manifests if the two node editors are on different monitors - Closing the secondary window or moving it back into the main windows monitor cancels the effect. - Only the main window ever seems affected, the secondary window remains working as intended in any of the monitors - Setting both monitors to have scaling at `100%` seems to avoid the issue See the following screen capture, it is not obvious in the video, but the recording was captured midway between the two system monitors, the blue background is Window desktop wallpaper on the second monitor and represents the boundary between two screens, while Blender's main window was full screen on the main monitor. [NodeBug.mp4](https://archive.blender.org/developer/F9883747/NodeBug.mp4) This is probably related to #85628, I have the same issue if I try to open a window in the secondary monitor, throwing an "Unsupported graphics card, need OpenGL 3.3 error".

Added subscriber: @DuarteRamos

Added subscriber: @DuarteRamos
Duarte Farrajota Ramos changed title from Node Editor hotspots misaligend when displaying two windows with the same node editors in different monitors to Node Editor hotspots misaligend when displaying same nodes in two monitors with different WIndows Scaling Settings 2021-03-10 23:53:56 +01:00

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'

I don't have the hardware to check. But the report is valid, so I'm confirming the bug.

I don't have the hardware to check. But the report is valid, so I'm confirming the bug.

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Duarte Farrajota Ramos self-assigned this 2021-05-07 00:37:48 +02:00
This seems to be similar or the same underlying issue as - https://developer.blender.org/T74355 - https://developer.blender.org/T76637 - https://developer.blender.org/T81160 - https://developer.blender.org/T86466
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
2 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#86466
No description provided.