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
Using StartAllBack with "Use new fonts globally" option enabled (Changes the font used globally to Segoe UI Variable Display instaid of Segoe UI) causes the font inside of Fjord Launcher to fall back to some kind of default font (Suspecting Qt's default font if it even has one) instaid of Segoe UI Variable Display.
Can you reproduce this issue on Prism Launcher (either latest stable 9.x release or latest development build)? I doubt this is specific to Fjord Launcher, so try with Prism Launcher and if you can reproduce it, file an issue on Prism Launcher. And/or StartAllBack, perhaps.
Can you reproduce this issue on Prism Launcher (either latest stable 9.x release or latest development build)? I doubt this is specific to Fjord Launcher, so try with Prism Launcher and if you can reproduce it, file an issue on Prism Launcher. And/or StartAllBack, perhaps.
Did try on Prism 9.2 and on Shattered Prism
Prism 9.2 uses Segoe UI Variable Display as it should be, Shattered Prism shares the same behavior as described
Shattered Prism is based upon Fjord (as of late last year) and so any issues you have would be shared between the two for the most part, I can't think of any specific change made to Fjord that would cause this though, Startis/Startallback seem to work fine without that setting enabled?
Operating System
Windows
Version of Fjord Launcher
Fjord Launcher 9.2.2
Version of Qt
Qt 6.8.2
Description of bug
Using StartAllBack with "Use new fonts globally" option enabled (Changes the font used globally to Segoe UI Variable Display instaid of Segoe UI) causes the font inside of Fjord Launcher to fall back to some kind of default font (Suspecting Qt's default font if it even has one) instaid of Segoe UI Variable Display.
Screenshots showing the issue:

Steps to reproduce
Suspected cause
No response
This issue is unique
The text was updated successfully, but these errors were encountered: