• Bugs

  • Skeleton Viewer 4.0.64 & 4.1.00 issues

Hello,

I have a company-provided laptop that I use for meetings & other sensitive data. Lately, I have been getting animations reviewed by sharing my screen on this laptop and opening up skeleton viewer. However, because the display of the laptop is 3840x2160 and the (Windows 10) scaling is 250% (the recommended resolution & scale), when I open Skeleton Viewer 4.0.64 it always appears off screen by default. I can only see the top-left corner.

I have tried the usual "fix a window opening off screen" stuff, but none of this is an issue when I reduce the screen scale to 100%; which is way too small to work with on this particular laptop.
So what I'm finding is, it will open in the middle of the screen's total resolution, and it doesn't take into account any scale.

Steps:
1) Open skeleton viewer 4.0.64
2) Opens in the bottom right corner of the screen, only the top-left of the skeleton viewer showing.
3) Close.
4) Change Windows 10 scale (in Scale & Layout in Display settings) to 100% (from 250%)
5) Open skeleton viewer 4.0.64.
6) Opens perfectly in the middle of the screen.

I updated to 4.1.00, which opens perfectly! But now the UI is way too small to be of any use.
Steps:
1) Open skeleton viewer 4.1.00
2) Squint to see the settings.

Any help is appreciated.

Related Discussions
...

I've tried to reproduce this on a Windows 10 laptop with the same screen resolution as yours. I've tried 100% scaling to 250% scaling, and both the 4.0.64 and the 4.1.00 skeletonviewer open in the middle of the screen, with proper UI scaling:

What Java version are you running? I'm using OpenJDK 16 from here: https://adoptium.net/temurin/releases/?version=16

Are your GPU drivers up-to-date?

Are you using any other software that may interfere with how the UI scale of some apps is configured?

shocked Pikachu
It was Java. I used the version in your link and it all runs perfectly. I can't believe I didn't think of that.
Thank you so much for your help, Mario!

Great! Old Java versions are compiled without proper hdpi/ui scaling support, hence the issue you saw.