Extreme small, unreadable Menu-text after Update. 2020 and 2024 SU1

[mseder]

Correct files has arrived, fonts ok, thanks

[virtuali]

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 ?

[virtuali]

Correct files has arrived, fonts ok, thanks

I was quite sure it would have fixed itself shortly.

[virtuali]

3.4.4 update fixed it for me, Fonts came back to the usual size. Thx Umberto

I was quite sure of that.

[virtuali]

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 ?

[Pvazquez]

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

[virtuali]

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 ?

[davidcherrie]

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.

[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 ?

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.

[virtuali]

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.

[virtuali]

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.

[FerrevmVnion]

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.

[davidcherrie]

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.