microsoft / microsoft/psi

\psi Studio's 3D panel not rendering properly when using the integrated GPU (but ok with an external monitor)

Open
#281 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
574
Forks
104
Avg merge
19m
Merged PRs (30d)
1

Description

Hello,

I started using both \psi and \psi Studio and ran into issues with the 3D panel in \psi Studio.

It was not working properly (see below for the symptoms) when Psi Studio was being displayed on my laptop display (with or without an external display being connected). It similarly did not work properly when the program was being displayed on the secondary screen connected through HDMI via a USB-c adapter. It was however working fine when displayed on the same secondary screen but connected through HDMI directly. This led me to investigate graphics settings and forcing the program to use the dedicated GPU (via System->Display->Graphics in Windows 11) indeed solved the problem.

By not working properly, I mean that the panel stays mostly empty and only partially renders its content (grids, skeletons, point clouds, etc) depending on cursor movements. See screenshots for a clearer view on the issue, with the 3D panel placed in the bottom (below the hidden panel that was hidden as it contains a color image).

Without forcing the usage of the dedicated GPU:
Screenshot 2023-05-03 095709

After forcing:
Screenshot 2023-05-03 095748

I am not sure whether there is an easy way to force dedicated GPU usage from the code itself, or whether rendering through the integrated GPU can be fixed, but the need to force dedicated GPU usage should likely be mentioned as a warning somewhere (right now, a laptop user without a secondary screen, or without a "connection setup" that triggers the activation of the dedicated GPU, would likely simply consider that the 3D viewer does not work).

Thank you for the great work! (also please share your code for SIF - the "skeleton merging with 2 kinects" part in particular - as this would likely save me at least a couple of hours 😂)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the 3D panel failure on Windows 11 with an integrated GPU, comparing the laptop display and the different HDMI connection paths described in the issue. Investigate the 3D viewer entry point and rendering setup; done means the panel renders its grids, skeletons, and point clouds reliably, or the application clearly warns users about the dedicated-GPU workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
computer-graphics, desktop-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.