• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Timezone Editor Problems

Hi Don,

I tried the Time Zone Editor.

I go to Airports, Change Local Time Offset and enter DTMB. I receive the data for DTMB. As Tunisia is using DST I change the Summer Time from blank to 2. I click on Apply Update.
When I click then on the Exit button I receive the following warning : "Changes made to the file will not be saved. Exit anyway ? ". I have the option Yes and No.

This means that Apply Update is not changing the timezone.dat file which it should be doing

Or am I doing something wrong here?

Rgds
Luc
 

gadgets

Resource contributor
Or am I doing something wrong here?
No, Luc, you're not doing anything wrong. It would appear that I started to modify the time zone editor some time ago but never finished the job. The finished time zone editor is available in Version 1.31, uploaded a short while ago.

Thanks for pointing out the problem.

Don
 
Time Zone Editor

Hi Don,

I have a problem with the timezone editor. I start from the default timezone.dat
When I change the timezone for an airport (GCFV) and save the changes I receive an error message for certain flightplans (see example in attachment). I have checked my airport.dat,the airport is there, and I have checked my timezone.dat, the changed airport is there as I have entered and the airport in the error message is also there. I have this with MDPP and GGOV.

Any ideas ?

Rgds
Luc
 

Attachments

  • 1.jpg
    1.jpg
    20.5 KB · Views: 497
Last edited:

gadgets

Resource contributor
The country/region/city data is used to link the two data bases. This problem should occur only if the spelling of the country entry in the two databases don't match or if no standard time offset is specified in Timezone.dat. I note that two of the three airports with which you're having difficulty have a 0 offset from UTC. Please check that the standard time offset in the timezone database for the applicable city is "0" and not blank.

In order for me to help diagnose the problem further, I need a copy of your "AirportList.dat" and your "Timezone.dat". Please send them via e-mail attachment to the e-mail address noted at the end of the user manual.

Don
 
Hi Don,

Thks for the new version.

I tried it out, did the same thing as described in my mail to you, and works now. I change the timezone for GCFV and no longer have the error message.

I do however have a problem now with the conversion from LT to UTC. eg the first flight in flighplan (13) from the file I send you yesterday :

EBBR 10:25 MDPC 18:20 all LT

when I look in the text editor(=UTC) I see 0/08:25,@0/18:20,360,F,0103,MDPC.
So dep EBBR correct as (UTC+2), arr MDPC wrong (1820 and -4UTC= 22:20)

other flights have the same problem

Could you check this plse

Thks a lot
Luc
 

gadgets

Resource contributor
Sorry, Luc. It was another instance of a problem I fixed yesterday. (If summer time was selected and summertime was not observed at the airport, I used UTC time rather than the standard time offset.)

Easy fix. I'll have a new version out later today.

Sure wish you'd been on my beta team!
Don
 
Top