Hello,
can you guys please confirm the TFDi version of cycle 2504? It is showing 2503 even though the database is updated to 2504.
Cheers
1 Like
Yes, I can confirm that;
Same with me:
Navigraph Hub shows 2504 updated but when I start the sim and load the MD-11 it still shows 2503. Looking at file explorer the small file “cycle.info” is current as of 2/9/2025 ALL other files and data are dated 3/12/2025.
Looks like it is downloading the old data…
1 Like
can confirm.
cycle_info.txt says
AIRAC cycle : 2504
Version : 1
Valid (from/to): 17/APR/2025 - 15/MAY/2025
but it is still 2503.
The same issue here. I reinstalled and nothing change.
Same problem here. I contacted TFDi and the devs say it is indeed a issue with Navigraph not sending the updated files for TFDi MD-11.
Same issue as well, also tried reinstalling without success. FMC still shows 2503 and the old dates of 2503.
same issue as well, showing old data
Same issue, this is like the 3rd time now that they’ve broken the Navdata for the MD-11…it’s getting kinda annoying at this point
Hi,
The navdata files are not broken, nor have you an old cycle. The Hub installs the current cycle correctly and this is also confirmed in this postings here
It’s only the cycle number in the Hub which is not correct. So a “optical” issue …
We will fix it as soon as possible.
Cheers
Richard
We will suspend the TFDi cycle from the next cycle until all issues (internally and externally) are sorted out and fixed to avoid such criticism and troubles.
So cycle 2504 is the last for maintenance at the moment.
Cheers
Richard
I don’t understand this reply. It’s the second time I have personally posted about this. Last time it was admitted that it was a file omission error from NG. This time however, due to an optical issue it has been decided that part of a product we pay for is simply omitted from future updates without any timeframe?
Has anything changed from TFDi’s formatting since it’s release that makes you believe that it’s an external issue?
I think it’d be nice to offer some better explanation and a future solution to this …
Happy Easter,
Xander
EDIT: Just so you are aware. As has been mentioned already, ALL data files except the cycle info file show old (March) Modified Dates. Are you sure it is 2504?
1 Like
Richard, instead of spreading false information, please do actually fix your problem.
Here are two pictures for you. The first is from the previous cycle. The second is from the current cycle.
As you can see, all the navdata files are dated 12.3 12:38. Are you really gonna tell me with straight face that this is the latest navdata? Before you ask, I installed this 5 minutes ago.
Also, Richard, this isn’t the first time this happens to you. Wrong navdata installed
We will fix it in the next couple of hours, and to avoid this in the future, we set this cycle on hold due maintenance.
Happy easter too
Richard
So are you saying that, for addon that you have supported for 1,5 years, you cannot suddenly support it anymore? I fly only the TFDi. Can you return part of my subscription payment? Why would I need to pay the full price for partial product?
1 Like
Yes, as I have written before, we (and also TFDi) must sort out the issues before we run into the same disaster.
The number of small single files kills our package process, so we should not use this any longer. We must check with TFDi if they can optimize it a little bit.
Therefore, we must suspend this addon till all is fixed. We will check your account and will contact you.
Cheers
Richard
What? Why? if its only a “optical” issue there is nothing to suspend.
Why are getting paying pepole punished for an issure where devolper bouncing the ball back and forth?
It was not an optical issue as I have thought, the files were really outdated because our package process was crashed. Therefore we must look for a solution to solve this.
Cheers
Richard
SO because TFDi have broken the package into smaller files to aid optimisation (i.e. smaller individual file downloads with less likelihood of corrupted data), you’re gonna suspend updating these until they go to fewer larger files?
Come on Richard, that’s not a TFDi problem, that’s a Navigraph problem if you can’t package a number of files in a ZIP file which is then extracted on the user’s machine
None said that this is a TFDi issue, but the number of files is an issue in all situations, and you can read a lot of postings here in the past about this.
We must find a solution to improve this and optimize it together with TFDi. You expect correct, stable data, and we must consider how to offer it.
The feeling in this posting is that you are unhappy with the current situation, and that’s ok. So we must look at how we can improve it. So, we need time to analyze this with TFDi and solve this problem.
I understand the criticism, and we will do our best to bring the data back as soon as possible.
Cheers
Richard
1 Like