Day of week error in WEATHER TAG

[N6722C]

Day of week changes with UTC time, and not Local time.

Example: Sitting at an airport in Florida

Local Time 6:52 PM (11:52 PM UTC ) Nov 26

about an hour later

Local Time 7:51 PM ( 12:52 AM UTC) NOV 27

But where I am in Florida, it should still be NOV 26 LOCAL

So day of week is the UTC Time Day of week

but time is being displayed as

7:564 PM (12:54 AM UTC)

Implying the time is 7:54 LOCAL ( and for ref that is 12:55 AM UTC)

surely it would be better to display the time as

12:56 AM UTC ( 7:56 PM Local) so that the PRIMARY time, UTC, and NOT the LOCAL in ( ) matches the Day of week.

Most times in Aviation are UTC for consistency

Also, isn’t UTC time more typically in 24 hour Format ?

Then switching to REAL TIME there is STRANGE

( c DOT displayed ??)

what is that meant to denote ???

Its only there with LIVE weather, but there is already a (LIVE) at the end to show you it is LIVE weather, the "C c Dot) is redundant and meaningless.

NOT A BIG DEAL – but seems needlessly confusing

[Hester40MT]

@N6722C

( c DOT displayed ??)

The dot and 2 parentheses (like a satellite) indicate “live”.

[N6722C]

@Hester40MT

The dot and 2 parentheses (like a satellite) indicate “live”.

OK, I can see that “the Dot and 2 parentheses” maybe a satellite symbol, but what does that have to do with “LIVE WEATHER”

It is both confusing and REDUNDANT, as the text (LIVE) is added to the time text, when the weather is Live.

Is it implying that the LIVE weather you are seeing from the cockpit is sent to earth by Satellite – some sort of advanced , science fiction (GAME !! ) "Satellite WEATHER Control System "

Not to be confused with weather information, that can be sent by Satellite to the plane’s satellite radio equipment

[TheSevenflyer]

Topic moved from General Discussion.

[N6722C]

I don’t think “The Community” can themselves change this – It will have to be Asobo, if any changes are going to be made,

[DementedCorn327]

@N6722C

12:56 AM UTC ( 7:56 PM Local) so that the PRIMARY time, UTC, and NOT the LOCAL in ( ) matches the Day of week.

I agree, it makes more sense.

@N6722C

Also, isn’t UTC time more typically in 24 hour Format ?

Agree too, time should always be in 24H format.
I noticed this is based on your PC/Console regional settings. If you switch to a country that uses the 24H format, then time in the MSFS screenshot you shown will also be in 24H format, you can make the test. So that setup in MSFS should be independant of your regional settings.

@N6722C

It will have to be Asobo, if any changes are going to be made

I would recommend you to create a wishlist topic for those changes.

[N6722C]

@DementedCorn327

If you switch to a country that uses the 24H format, then time in the MSFS screenshot you shown will also be in 24H format, you can make the test. So that setup in MSFS should be independent of your regional settings.

Exactly – the whole point of Aviation using UTC is that Aviation is Worldwide, so it greatly reduces the complication of figuring out time differences when stating a “Time”.

Each location can then , if needed, translate that UTC time/date to their current Local time, and any daylight saving times that occur.

So is using the 24 Hour Format.

While not everyone is 100% familiar with the 24 Hour Format, it is used extensively in the Aviation Industry, from controller, to pilots, and even to Passengers.

ie Departure times are always displayed in 24 Hour Format

(local time of course for the general flying public)