renderdoc icon indicating copy to clipboard operation
renderdoc copied to clipboard

UI Display Issue

Open SantyWang opened this issue 1 year ago • 7 comments

Description

Hi guys, render doc is very good software, but I seem to be experiencing some display problems in the interface, I tested several versions from 1.32 to 1.9, and the display is abnormal, I think it may be related to my environment, if you have any information about it, thank you very much!

image image

Steps to reproduce

Download installer and install. Run qrenderdoc.exe

Environment

  • RenderDoc version: 1.33, 1.16, 1.12, 1.9
  • Operating System: Windows 10 Pro
  • Graphics API: XXX

SantyWang avatar Jul 12 '24 10:07 SantyWang

This looks like a Qt issue selecting a font which is not displaying numbers as expected.

Please can you share a screenshot of "Tools...Settings" window to see what font Qt is using. Try choosing a different font from that settings window to see if it fixes the issue.

Zorro666 avatar Jul 16 '24 11:07 Zorro666

image Seems like there is no font settings.

SantyWang avatar Jul 22 '24 02:07 SantyWang

That screenshot looks like an old RenderDoc version. Can you post a screenshot from RenderDoc v1.33 of the "Tool...Settings".

i.e. for me it looks like this on v1.33 image

Zorro666 avatar Jul 23 '24 07:07 Zorro666

image

SantyWang avatar Jul 31 '24 08:07 SantyWang

Please can you try changing the "Default Font Family" to a different font i.e. "MS Shell Dlg2" or "Ariel" to see if that fixes the issue.

Zorro666 avatar Jul 31 '24 13:07 Zorro666

Yeah, I've tried, but nothing changed.

SantyWang avatar Aug 12 '24 02:08 SantyWang

Can you post a screenshot of the settings dialog running v1.33 or v1.34 after changing the font to "MS Shell Dlg2" or "Arial" after restarting the program.

baldurk avatar Aug 12 '24 09:08 baldurk

Closing this due to lack of activity from the reporter and no further information to investigate.

If you are the reporter and this bug is still a problem for you, or you are someone finding this issue and you believe this bug is still a problem and you have more information to share, please do not comment here and instead please open a new issue. You can reference this issue if you wish, but opening a new issue prevents confusion of accidentally linking two unrelated bugs and means that each issue can be handled in a clean process.

baldurk avatar Sep 12 '24 10:09 baldurk