• Bugs
  • interface scale bug

  • Изменено
Related Discussions
...

You set the interface scale on the Settings dialog, then closed Spine, ran Spine again, and Spine crashed or never opened?

Can you please cause the crash again, then post your spine.log?

Windows: <user home folder>\Spine\spine.log
Mac: <user home folder>/Library/Application Support/Spine/spine.log
Linux: <user home folder>/.spine/spine.log

  • Изменено

Yes loads but nevers opens. Nothing much in the log.

Spine Launcher 3.0.13
Windows 10 Pro x86 6.2
Java 1.7.0_06 Esoteric Software
32-bit Server VM
Up to date: Spine 3.1.06
Spine 3.1.06 Professional, LWJGL
Licensed to: Ryan
Intel
Intel(R) Iris(TM) Pro Graphics 540
4.4.0 - Build 20.19.15.4364
Started.
WARNING: Flip X timeline is no longer supported, bone: F_Forearm
WARNING: Flip Y timeline is no longer supported, bone: F_Forearm
WARNING: Flip X timeline is no longer supported, bone: F_Forearm
WARNING: Flip Y timeline is no longer supported, bone: F_Forearm
WARNING: Flip X timeline is no longer supported, bone: F_UpperArm
WARNING: Flip Y timeline is no longer supported, bone: F_UpperArm
WARNING: Flip Y timeline is no longer supported, bone: B_Forearm
WARNING: Flip X timeline is no longer supported, bone: F_UpperArm
WARNING: Flip X timeline is no longer supported, bone: F_Forearm
WARNING: Flip Y timeline is no longer supported, bone: F_Forearm
WARNING: Flip X timeline is no longer supported, bone: F_UpperArm
WARNING: Flip Y timeline is no longer supported, bone: F_Forearm
WARNING: Flip X timeline is no longer supported, bone: F_UpperArm
WARNING: Flip Y timeline is no longer supported, bone: F_Forearm
WARNING: Flip X timeline is no longer supported, bone: F_UpperArm
WARNING: Flip Y timeline is no longer supported, bone: F_Forearm
WARNING: Flip Y timeline is no longer supported, bone: F_Forearm
WARNING: Flip X timeline is no longer supported, bone: F_UpperArm
WARNING: Flip X timeline is no longer supported, bone: F_Thigh
WARNING: Flip Y timeline is no longer supported, bone: F_Thigh
WARNING: Flip X timeline is no longer supported, bone: F_UpperArm
WARNING: Flip Y timeline is no longer supported, bone: F_Forearm
WARNING: Flip X timeline is no longer supported, bone: F_UpperArm
WARNING: Flip Y timeline is no longer supported, bone: F_Forearm
WARNING: Flip Y timeline is no longer supported, bone: B_Forearm
WARNING: Flip X timeline is no longer supported, bone: F_UpperArm
WARNING: Flip X timeline is no longer supported, bone: B_Forearm
WARNING: Flip Y timeline is no longer supported, bone: B_Forearm
WARNING: Flip X timeline is no longer supported, bone: F_Forearm
WARNING: Flip Y timeline is no longer supported, bone: F_Forearm

That is completely bizarre. Are you able to reproduce the problem every time? The log you posted was from immediately after it failed to open? Setting the UI scale has almost no chance to cause the Spine window to not appear. Does 3.1.06 work with the scale at 100%? Does 3.1.05 work at 100%? 200%?

Are you able to reproduce the problem every time? yes
The log you posted was from immediately after it failed to open? yes
Does 3.1.06 work with the scale at 100%? yes, when i reinstall.
Does 3.1.05 work at 100%? 200%? i have not tried.

Thanks.

Instead of uninstalling, you can probably just delete your preferences file:
Windows: <user home folder>\Spine\prefs.json

You can try running Spine this way for 200%:
`Spine.exe


scale 2`
This overrides the scale that is set on the Settings dialog.

I'm not sure what else we can do at this point until we can reproduce the problem ourselves.

Thanks.
Spine.exe


scale 1 allowed the software to load again and change the settings back.
scale 2 didn't work.

I see it loading, but once it gets to 100% it closes/terminates.

That's crazy. Scale only affects rendering math. It shouldn't be possible for it to crash the app. Plus, if the app crashes in Spine there should be something in the spine.log file. If there's not, it means the crash was at a lower level. This is equally confusing because the UI scale isn't involved there. 🙁

Could the scale in the prefs json (I assume it is json) being wrote/read incorrectly (char instead of float), this terminating the rest of the the json file?

It's pseudo-JSON. Looks right:

advanced: { uiScale: 1.51 }