You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
After forcing:
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 😂)
The text was updated successfully, but these errors were encountered:
qdrien
changed the title
Psi Studio's 3D panel not rendering properly when using the integrated GPU (but ok with an external monitor)
\psi Studio's 3D panel not rendering properly when using the integrated GPU (but ok with an external monitor)
May 3, 2023
Thanks for posting this issue! I haven't observed this behavior myself, but it's good information in case others run into a similar issue on laptops with integrated graphics.
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:
After forcing:
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 😂)
The text was updated successfully, but these errors were encountered: