FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: Tur1can21 on March 31, 2025, 10:20:52 am
-
Hi
I install msfs2020 yesterday and after install of GSX-Pro (include yesterday update) i have extreme small Menu-text, unreable for me on 3840x2160 Screenresolution. This also affects my msfs2024 SU1 installation. Try to fix as mentioned here in the Forum but i cant fix it (klick on gsx Menu-Border. Resize and move around Menu Window, open GSX Menu with hotkey instead of toolbar). The Text seems to be rendered correctly (not blurry) but just way to small. Change UI Text Size in msfs Menu does not change anything.
Is there any GSX config file where i can change the Text size ?
I did not found anything in the GUI and Manual.
thx
best regards
Andi
-
Just updated to v3.4.3 and the text size is now wrong in MSFS 2020 (was ok previously). The larger text size required in VR is now used in 2D and the smaller text size is now used in VR. Note this was MSFS 2020. I see recent changelog addresses an MSFS 2024 issue, so this may have had unintended consequences in 2020?
-
Noticed the same thing in VR yesterday using 3.4.1. Haven't tried 3.4.3 yet
-
Same problem but only in VR
See https://www.fsdreamteam.com/forum/index.php/topic,33024.0.html
-
Same problem
-
Same here in MSFS2020 - GSX update 3.3.4 - GSX Menu text way too small- please fix to previous size. Thanks.
-
Mine has extremely big menu, 1080p, adjusting the ui scale in settings has no effect.
-
Same problem here, fonts in 2D are a bit smaller than usual, in VR absolutey unreadable, 3.4.2 and 3.4.3 makes no difference.
Any ideas for a solution?
-
Same here!
Please fix this issue, in VR GSX is now unusable!
-
What have you done?
-
I confirm, text in VR is extremely small (I can't read it anymore, I need to get closer to the GSX windows to read) and in 2D it seems now bigger instead.
-
So , then let's hope for a quick update as fsdt did in the last few days for other issues
-
In my case with 2560x1440 2D Version 3.4.3. font size is okay. :)
Was far too big before/overlapping lines.
-
For you at least the menu is opening, here it doesn't open at all, since last Friday, version 3.4.3. Do you use FS2024 or 2020? Here I use 2020.
-
Any chance to rollback ? Are the older Versions available to download manually somewhere ?
It is unusable for me now (sit about 4 Meters away from 55" 2160p TV)
-
No chance I guess if you look at older threads with other issues .
Should not be too hard to fix for FSDT, I hope the responsible guys read this
-
It's ridiculously large now on my 3440x screen and font size does not auto-resize when you shrink the Main Menu window down. I tried the Scaler mod and that didn't touch it whereas before this change it did. Fix it quickly please thanks in advance.
-
looks like its a msfs2024 bug from the last update
-
Of course it's an MSFS SU2 Beta bug, and we had to act quickly on it, because without our FIX, it would cause a completely unreadable menu with microscopic tiny fonts, which was way worse than a "slightly" different font size that, as you can see, depending on the resolution used, might be perfect, better than before or worse, because the only FIX for that bug was to set a fixed font size, so at least you would see something.
Since this problem doesn't affect only GSX but several other apps with a Toolbar menu, on a recent post on their devs forum, Asobo promised the problem with UI scaling, which happened with MSFS 2024 SU2 Beta and we had to act quickly on to prevent a way worse issue of tiny unreadable fonts, should be fixed in the final version or in a newer beta, so assuming it will be fixed, we can go back to the previous version of the menu which supported UI scaling.
-
For you at least the menu is opening, here it doesn't open at all, since last Friday, version 3.4.3. Do you use FS2024 or 2020? Here I use 2020.
I Use 2020.
-
I have this problem in 2020 and 2024 SU1 (not beta). Can you please provide a previous Version to downlad as it is unusable for me now. I have tiny microscopic fonts now. thx
-
which happened with MSFS 2024 SU2 Beta and we had to act quickly on to prevent a way worse issue of tiny unreadable fonts, should be fixed in the final version or in a newer beta, so assuming it will be fixed, we can go back to the previous version of the menu which supported UI scaling.
So the change you made quickly impacts both 2020 and 2024 and also affects people not on the SUbeta like myself okay thanks looks like it will be restored at some point.
I've also noticed a big increase in jerky animation in GSX over the past few weeks. It's never been great though it's been okay but now much worse, regardless of whether or not the sim is locked at 30 FPS or not.
-
These updates should first go through beta testing for anyone who wants to use and test them, just like many developers do. Now, since last Friday, I have not been able to simulate them in MSFS2020 because GSX no longer works after a quick update.
-
... because without our FIX, it would cause a completely unreadable menu with microscopic tiny fonts, ...
Your fix caused microscopic tiny fonts for me, never had this problem before. Can you please provide me a previous version ?
best regards
Andi
-
I also have this problem in MSFS 2020 in the VR Menu, the fonts are microscopicly small and impossible to read.
In no way it is just "slightly different"
A possibility to download previous versions would help quickly and nobody would have to wait for another SU or could at least use the product we paid for again.
-
Who cares about SU2 beta users, they use beta they know the risks. let them have screwed up fonts and have Asobo fix it !!! now everyone else has screwed up fonts 2020 in VR is a joke, fix it back to the way it was and stop blaming everything you do on someone else.
-
Exactly AndyCYXU!
This arrogant attitude from FSDT is absolutley not understandble.
First releasing an update without sufficiant testing and then blaming everybody else but themselves when problems occur, that make the product unusable from one second to the other!
Users would expect a quick fix /roll back option or at least an excuse but not justification for your very own inability!
This would be ok for freeware but not for a 35 Euro product from a company, that makes advertisements with "high quality addons for flight simulation on their homepage.
-
Then, I understand that for solve a problem with FS2024 Beta, GSX Pro on my FS2020 is wrong with a very little fonts. Incredible!
Any solution for FS2020?
-
This getting a farce .... the in the release notes you only mentioned SU 2 scaling bugs... but you introduced a scaling bug by yourself... as SU 1 looks still like this
(screenshot is resized from 4k to 1080p)
The task is:
- Fix the scaling in all versions of MSFS <= 1.38.2.0 (SU 1 and lower)
Umberto, you dont have to react quick on beta versions, you have to maintain the product working for official versions first, second may provide a hotfix for beta versions
@Sharpsolver
Unfortunately the attitude is included when buying gsx :/
Never saw a "it was my fault / i apologize" or s.th similar before or even not just an "Ups!", never in almost a decade using GSX
-
Problem remains with update 3.4.4
-
I confirm, no change also in VR with 3.4.4
Still unreadable >:( >:( >:(
-
MSFS 2020
Problem remains for ver 3.4.4
-
The problem has been fixed in 3.4.0, since with the 3rd SU2 Beta, Asobo has fixed the bug in the sim which caused tiny fonts.
-
ehm.. no ?!
Orginal resoultion is 3840x2160, image is down sized to 1080p
-
ehm.. no ?! Orginal resoultion is 3840x2160, image is down sized to 1080p
The problem discussed here is the TINY unreadable font in SU2 Beta. You don't have that, your screenshot shows fonts *slightly* smaller than what I see here but, I don't have a 4K monitor, so I don't know if your size is how it always look like in 4K, but it surely NOT the tiny unreadable fonts that has been fixed for sure.
Version 3.4.4 doesn't change anything, it simply restored the menu file as it was before the SU2 bug, so you should see the same result as you always had and if you are not, it means you don't have 3.4.4 installed, possibly due to your cloudflare node not updated yet, so just try again now, it might be fixed.
-
The problem discussed here is the TINY unreadable font in SU2 Beta. You don't have that, your screenshot shows fonts *slightly* smaller than what I see here but, I don't have a 4K monitor, so I don't know if your size is how it always look like in 4K, but it surely NOT the tiny unreadable fonts that has been fixed for sure.
Version 3.4.4 doesn't change anything, it simply restored the menu file as it was before the SU2 bug, so you should see the same result as you always had and if you are not, it means you don't have 3.4.4 installed, possibly due to your cloudflare node not updated yet, so just try again now, it might be fixed.
So the problem of half size font is not a bug but a feature? Why has this become an issue for all of us that use a 4K monitor all of sudden then?
-
"so you should see the same result as you always had and if you are not, it means you don't have 3.4.4 installed,"
Images from 1 VR Menu 2 Installer and the manuifest.json file from fsdreamteam-gsx-pro
MSFS2020
Please, just fix this
-
As I've said, the TINY UNREADABLE fonts problem HAS BEEN FIXED. You with 4K monitor are all reporting a whole completely different issue, which is NOT tiny unreadable fonts, but just fonts as smaller as they used to be even, again, I have no frame of reference since I have a 1440p monitor, so I don't know *exactly* how they looked like before.
I'll try to explain it again: the bug that has been fixed is the one that, when you open the menu the first time, the fonts where microscopic, NOT as in your screenshot, but way, way smaller. And as soon as you clicked on the menu border, they fixed themselves to their normal size. THIS and only THIS is the bug that HAS BEEN FIXED in 3.4.4.
You are seeing something different, and I suspect one or more updated files might have not reached your local cloudflare node, even if the manifest.json has (so quoting the manifest.json is not very useful, it only show you at least *tried* to update).
Can you check the size of these two files ?
\Addon Manager\fsdreamteam-gsx-pro\html_ui\InGamePanels\FSDT_GSX_Panel\FSDT_GSX_Panel.css (should be 2860 bytes)
\Addon Manager\fsdreamteam-gsx-pro\html_ui\InGamePanels\FSDT_GSX_Panel\FSDT_GSX_Panel.html (should be 3994 bytes)
If the copy you have has a different size, you don't have the latest version we have online now so, just try again an update CHECK, I'm sure the update files must reach your cloudflare node, I also forced a cache retrigger, in case cloudflare didn't take it.
-
I'll check those files, but just to avoid misunderstandings.
My problem with the small fonts is only in VR. The image is the VR view and the fonts are really microscopic maybe not that obvious on the image.
This problem sytarted right after I guess (80% sure) the 3.4.3 release, with no updates of the flightsim for a long time.
In the non-VR view the fonts maybe are a bit smaller, but really no problem, hard to see a difference, if there is one.
-
C:\Program Files (x86)\Addon Manager\MSFS\fsdreamteam-gsx-pro\html_ui\InGamePanels\FSDT_GSX_Panel\FSDT_GSX_Panel.css
2657 bytes, on disk 4067 modified 04-03
C:\Program Files (x86)\Addon Manager\MSFS\fsdreamteam-gsx-pro\html_ui\InGamePanels\FSDT_GSX_Panel\FSDT_GSX_Panel.html
3815 bytes, on disk 4096 modified 03-31
css attached as txt
-
css attached as txt
That's confirms my suspicion which is a cloudflare replication delay: BOTH files are not the version we have online. As I've said, the correct size are these:
\Addon Manager\fsdreamteam-gsx-pro\html_ui\InGamePanels\FSDT_GSX_Panel\FSDT_GSX_Panel.css (should be 2860 bytes)
\Addon Manager\fsdreamteam-gsx-pro\html_ui\InGamePanels\FSDT_GSX_Panel\FSDT_GSX_Panel.html (should be 3994 bytes)
So, just try again until you get the correct ones, sometimes it might take two tries, if you are the first in your area calling for a new file.
-
Just try updating again now and check the file sizes of the two files I listed, which were surely outdated in your case.
Nothing affects how cloudflare nodes are updated, it's completely outside anybody's control, we can only tell cloudflare which files are new (and there's an automated procedure for that), the rest is done automatically. What you do is not really relevant but, it's *possible* that, if you were the first one calling for that file in your area (same local node), it might require trying an update Check twice.
-
Its so small that i need to wear my glasses which i never had to do to read the menu. So to me its: Tiny and unreadable.
So it would be great if you change the font size back to the size before whatever you have done
-
Totally unreadable, also with the newest version, also in MSFS2020, also in VR.
-
3.4.4 update fixed it for me, Fonts came back to the usual size. Thx Umberto
-
Correct files has arrived, fonts ok, thanks
-
Its so small that i need to wear my glasses which i never had to do to read the menu. So to me its: Tiny and unreadable.
You haven't read what I wrote in all my previous posts, haven't you ? This was the key parts:
I'll try to explain it again: the bug that has been fixed is the one that, when you open the menu the first time, the fonts where microscopic, NOT as in your screenshot, but way, way smaller. And as soon as you clicked on the menu border, they fixed themselves to their normal size. THIS and only THIS is the bug that HAS BEEN FIXED in 3.4.4.
It seems you are "just" reporting a smaller size than before that you are deeming "unreadable", NOT the font starting microscopic and THEN fixing themselves after a click, which (again) was the ONE and ONLY issue changed (which also required an updated from Asobo)
So it would be great if you change the font size back to the size before whatever you have done
That's precisely what we did!! Have you missed all my other posts about not getting the right files ? Have you checked the files I asked to check, which would prove the problem was in fact a network replication delay ?
-
Correct files has arrived, fonts ok, thanks
I was quite sure it would have fixed itself shortly.
-
3.4.4 update fixed it for me, Fonts came back to the usual size. Thx Umberto
I was quite sure of that.
-
Totally unreadable, also with the newest version, also in MSFS2020, also in VR.
Have you read what I wrote in all previous post, especially the one which will explain how to check if you are getting the correct files ?
-
Hello,
I am also having the same problem. It started about two weeks ago… I think, maybe longer. I have not added any new aircraft, scenery, liveries… nothing since January when I bought the EDDF scenery for MSFS 2020… I really don’t know what happened. I just updated via FSDT Live Update and still not fixed.
Not sure what to do. I am including a before and after screenshots so you can see the difference.
Pvazquez
-
Not sure what to do. I am including a before and after screenshots so you can see the difference.
Have you read what I wrote in all previous post, especially the one which will explain how to check if you are getting the correct files ?
-
Have you read what I wrote in all previous post, especially the one which will explain how to check if you are getting the correct files ?
If users are updating to the latest version and not getting correct files, surely that is not their fault and an issue on your side? Maybe fix your constant issues with Cloudflare or look for another CDN?
Just one software developer to another, maybe ensure that all files have reached the CDN before allowing the end-user to be able to see the update. Just a suggestion.
-
Not sure what to do. I am including a before and after screenshots so you can see the difference.
Have you read what I wrote in all previous post, especially the one which will explain how to check if you are getting the correct files ?
Hello,
I did update my GSX and I did as you posted before... Here is the screenshots so you can see them. The files have the correct bytes... It is still showing in small letters. I really don't think the problem is with my installed copy of GSX Pro. It's just my opinion.
Regards,
Pvazquez
UPDATE:.... I just updated it twice again just now and it looks like it's fixed. I will check again in the morning.
-
If users are updating to the latest version and not getting correct files, surely that is not their fault and an issue on your side?
And where, exactly, I ever said it's the "user's fault" ?
Maybe fix your constant issues with Cloudflare or look for another CDN?
Yes, because nobody uses Cloudflare...
Just one software developer to another, maybe ensure that all files have reached the CDN before allowing the end-user to be able to see the update. Just a suggestion.
And you think we don't do that ? Of course tests are being made before a new release, using a VPN, but it's not as if I can test each and every node individually. An example, a user in Melbourne didn't get the latest file. I checked with a VPN and tried all nodes in Australia (there are about 6-7 of them), and ALL of them had the latest file EXCEPT the Melbourne one!
The issue is, when I open a ticket to Cloudflare, by the time they reply (usually a couple of days), the node has already refreshed, so I have no evidence to supply to them to understand why some nodes refresh faster than others.
-
UPDATE:.... I just updated it twice again just now and it looks like it's fixed. I will check again in the morning.
Of course it fixed itself, that what I keep trying to explain, for example here:
It's *possible* that, if you were the first one calling for that file in your area (same local node), it might require trying an update Check twice.
-
That's precisely what we did!! Have you missed all my other posts about not getting the right files ? Have you checked the files I asked to check, which would prove the problem was in fact a network replication delay ?
i wont start the discussion about "your" cdn again ... gsx is the only program i know which has this weird distributing.... others programs are updating completely or they dont, but they dont update some files and some files later ... whatever discussed it years ago and its still the same mysterious gsx cdn ... sorry :)
i can resize the window, the font size remains tiny (and tiny is what i call tiny)...everthing is tiny when i cant read it without glasses, and before i never had to wear glasses to read the gsx menu ...
i will run the update another 10 times and hopefully the cdn is so kind and offers all files on any of the runs.
-
And where, exactly, I ever said it's the "user's fault" ?
Yes, because nobody uses Cloudflare...
And you think we don't do that ? Of course tests are being made before a new release, using a VPN, but it's not as if I can test each and every node individually. An example, a user in Melbourne didn't get the latest file. I checked with a VPN and tried all nodes in Australia (there are about 6-7 of them), and ALL of them had the latest file EXCEPT the Melbourne one!
The issue is, when I open a ticket to Cloudflare, by the time they reply (usually a couple of days), the node has already refreshed, so I have no evidence to supply to them to understand why some nodes refresh faster than others.
Do you use TCP or UDP?
Also if files are missing when they reach the node, why do you not have any validation to check all changed files have been received before allowing a user to use that node?
Sure there are the odd occurrences in deployment but with FSDT there are so many updates that have issues it is the norm and not the exception. So if Cloudflare aren't able to acknowledge and solve your problems then maybe move to Azure or Amazon or Google? You'd definitely have a lot less posts on the forums complaining that updates don't fix what they say they fix or break something else.
-
After updating twice everything now OK in VR, thank you!
-
Do you use TCP or UDP?
We just do the standard Cloudflare API call to purge an outdated file, so it's TCP.
Also if files are missing when they reach the node, why do you not have any validation to check all changed files have been received before allowing a user to use that node?
We cannot check the node, we just make a very simple API call to tell Cloudflare "these files are outdated, please resync", and it's then all done automatically by Cloudflare. OF COURSE we have an hash validation check to verify all files has reached the server, but the only thing we see is our origin server, not what's on the nodes.
In fact, I oversimplified, but the structure is not so simple as "our server->local node", there are servers IN BETWEEN that also need to be replicated as well, this is how really works:
https://developers.cloudflare.com/_astro/tiered_cache_topology.sy3gfwwc_ZdD2IV.webp (https://developers.cloudflare.com/_astro/tiered_cache_topology.sy3gfwwc_ZdD2IV.webp)
So, nobody downloads from our server directly except the main Upper Tier Cloudflare servers, which are the first getting the updated files. However, they won't download them *immediately*, they will just know (because of the API call we did with a list of outdated file) that, in case somebody needs a file, that file is outdated, so it must be downloaded again from our origin server.
So, when an user in a random place from his local Cloudflare node request a file, the local node should know it's outdated, so it will check the Upper Tier server on Cloudflare to see if the new version is there. If it's there, the local node will download it from the Upper Tier server and will serve to users of that local node. If it's not, the Upper Tier server which should also know that file is outdated, will finally download it from our server, the local node will download it from the now updated Upper Tier server, and so on.
This is a black box for us, the only thing we do, is provide a list of outdated files, the rest is done automatically by Cloudflare. It should be clear that, with that system in place, updates cannot be "immediate", there always be some kind of replication delay, because Upper Tier servers and Local nodes both host thousands if not millions of websites.
It has already happened that, when Cloudflare went down, millions of website were affected:
2019:
https://www.bbc.com/news/technology-48841815
2022:
https://www.techmonitor.ai/hardware/cloud/cloudflare-outage-disrupts-sites-google-aws-twitter
This outage affected Google, AWS and Twitter, so much for "Switch to Google or AWS"...
2024:
https://www.bleepingcomputer.com/news/technology/cloudflare-outage-cuts-off-access-to-websites-in-some-regions/
Note that, we have a Pro account, so we don't have the "regional Tier" layer of servers, so there's just one in between "origin server (FSDT)->Upper Tier server->Lower Tier (your local node)", the Regional Tier is reserved to Cloudflare Enterprise account which *start* at $5000/months, so there's no way we could possibly afford this.
As I've said, the only way to really TEST what would happen on user's systems, is to use a VPN, select a different country and just use the FSDT Installer and see if newer files are up.
Which I obviously do, but it's not I could possibly test each and every country in the world, if I test a couple of countries in different continents (Europe, America and Asia), and I see the newer files are up, I would be sure that at least Cloudflare got the CORRECT list of outdated files, so it surely synced at least the Upper Tier servers and the local node I tested but again, it's not really feasible to test all of them, see my previous example of the user having a problem in Melbourne: I tried ALL nodes in Australia, and Melbourne was the ONLY one not updated yet, but of course it got updated a few hours later.
Sure there are the odd occurrences in deployment but with FSDT there are so many updates that have issues it is the norm and not the exception. So if Cloudflare aren't able to acknowledge and solve your problems then maybe move to Azure or Amazon or Google?
We already use S3, but without Cloudflare in between as a CDN, the bandwidth bill would be outrageous. I happened a few years ago: because I didn't knew that Cloudflare never caches files larger than 500MB, we had a very old version of the full GSX Installer as a single .EXE, which was about 3GB. In a month, we spent $5000 of AWS bandwidth fees, so out of the ordinary, that I even had an Amazon representative calling me by phone to talk what they must have imagined a "new large enterprise customer", when in fact it was just my fault not having read the fine lines in the Cloudflare docs that files larger than 500MB are never cached. That's why the GSX full installer downloads in several parts of 490MB each...
That's a side effect of GSX installer always being freely available to anybody, without any account or registration, with no limit on downloads, no limits on bandwidth, and we NEVER, EVER experienced a loss of access to our server collapsing after a big release, not even on GSX for MSFS release day (something happened to many other devs), because we spread the load over the big Cloudflare networks.
Also, what Cloudflare also does, is prevent DDoS attacks and other threats on our servers. I just entered the Cloudflare stats page now and, in the last 24 hours, they have blocked more than 8000 Threats (7,137 from China, 767 from Singapore, 158 from Vietnam, if you like statistics), just 4.970 threats in the past 6 hours.
Now, while we DO NOT store any of our customers data on our servers (we don't process payments, and we don't handle the activation servers ourselves), there's at least this forum where we have at least emails for all forum users so, Cloudflare is helping protecting this data as well and it's another reason why we manually approve new forum registration: we have a plugin in the forum software which has a database of known spammers, so each new registration is checked manually, and *still* somebody managed to get through, by manually creating new email accounts to post Spam here.
That is to say, we take great care about users security and privacy, and Cloudflare is helping doing that, without having to hire dedicated people just to defend our servers from all kind of attacks, so even if it has annoyances, it works.
-
Just try updating again now and check the file sizes of the two files I listed, which were surely outdated in your case.
Nothing affects how cloudflare nodes are updated, it's completely outside anybody's control, we can only tell cloudflare which files are new (and there's an automated procedure for that), the rest is done automatically. What you do is not really relevant but, it's *possible* that, if you were the first one calling for that file in your area (same local node), it might require trying an update Check twice.
Worked for me after deleting those 2 files (FSDT_GSX_Panel.html and FSDT_GSX_Panel.css) and updating the GSX. Fonts size is back to what it was (resolution 3840 x 2160). Just updating GSX, didn't work for me!
Thank you !