Hallo,
The Super 80 pro was crashing FSX in total during loading of the aircraft.
After reinstalling everything the Super 80 pro was working normal again but after update the navdata to gen 2307 version it crashed the FSX total during loading of the aircraft.
I still had a version gen 2211 and i installed this version and it working normal again but as soon i manually use the 2307 version the super 80 pro crashes FSX again.
info the 2307 version works oke in the Fokker 70/100 aircraft.
Hope you help.
Hi Willem,
it looks like, the this addon has any internal data limitations and therefore the CTD. You wrote the database works in the Fokker, that means it should also work in the Super 80 because the data which they are using are equal.
Therefore my assumption, that this is an addon issue (ie. to small array for the amount of data because the data are growing from cycle to cycle, …).
Sorry, but in this case we must forward you to the addon devs. We can’t do anything for it.
I can do this Willem but I’ll test this first too … to confirm it 100% and to be sure, this is really no data issue from our side. I will inform you, when I have report it - hope thats ok for you.
Hallo,
I still have a problem with the latest Nav data for the Flight 1 Super 80 pro i already made a topic about this, but this one is closed but they promised to check it first by them self but still no answer if they have the same problem.
So i hope there is something they found about this.
pls check the topic from 7 augustus.
Hi Willem,
sorry that I have overseen this in the past and thanks for the re-post to remind us …
I have tested the F1 Super80 pro with our latest data and I can confirm the issue. I have also checked the data and as you wrote before, the same data works in other addons. So my personal assumption is (I can´t check it deeper), that an size of an internal array is too small defined and with every cycle the amount of waypoints increase, also terminal procedure legs and so on …
So, that´s not what we can fix sorry - I would recommend to contact F1 but I´m not sure, if they will fix this for such “old” addon. Please don´t understand me wrong, but the effort to fix this in their addon could be higher.
Sorry Willem and sorry again for the delay of this not good answer …
Cheers,
Richard
A second reply,
I received a reply from Flight 1 forum, and they told me to go back to you because it is a problem from Navigraph data itself.
Sorry for this but they told me it happened after the new updates so it is Navigraph problem.
Sorry to say, but this will not help anybody. I told them the same.
Hi Willem,
can you post the reference link to this forum? The Flight1 Super 80 pro uses exactly the same format as in example the F1 Fokker 70/100 and here the data are good so far. At least, I don´t have the same issue as in the S80pro.
So, when this is really a data issue, it shouldn´t work in the Fokker too - right? The issue is, that the datasets are growing and growing, right but we can´t remove data only that a addon works with the data sorry.
Again, I´m willing to help you here but I can´t see what issue we have. Possible that your reference F1 forum posting brings more light on this topic.
Thanks Willem, I have also posted my concerns in the F1 forum but according the previous answer from Mr. Patterson - I guess there will nothing be happen from the F1 side, sorry. I´m pretty sure, that this has something todo with hard-code limits which was very popular in the past, in the FSX time because no one has think about the amount of data in the future.
But anyway, I can´t see any data issue here - we will see, what they say but honestly, as I have written before, I don´t think, that this will be fixed. As a result, we must remove the S80 from our list because it´s not compatible any longer.
Ok they ended the support, but the product is still available for the same price if you look at the site and that what I don’t like about it.
So if people buy it now it will not work correctly, and you lost your money.
And the result is the same for your site, you are stopping the updates for this product and the people don’t know what the problem is.
Right, but without any help from the devs of the S80pro, we had no chance to find out what the problem is. So, when they ended the support - what should we do, we have no other possibility to remove it due any incompatible issues. It makes no sense, to offer a dataset which is not working, which is outdated and where we know that we can´t find out the reason.
In the meantime, I have also tested the data with the Piper Cheyenne now - also here, no issue - for me it´s nearly 100% sure, that this is a S80pro issue somewhere, sorry to say.