We have at this moment problems with e-mails coming to us via Microsoft servers (Outlook, Hotmail, Live, etc). We are in contact with Microsoft to solve this issue.

Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

23 Excellent

About ubersu

  • Rank
    Flight Student - Solo

Recent Profile Visitors

2659 profile views
  1. Hi Denis, It seems that the NDP data is missing a critical file - there is a *.index file that is required that is not installed by NDP. Sorry I missed that one... I suggest sticking with Navigraph for Carenado. DJ
  2. Carenado aircraft were designed with Navigraph in mind. That said it is trivially easy to change the NDP output to the \CarenadoNavigraph folder. That will give you another subfolder named "CarenadoNavigraph"; then drag the content of that folder into the "Navigraph" folder and you are done. DJ
  3. All of the Carenado aircraft use the same data. I just checked the 550, the CJ2 and the Phenoms and all are on the same database in this folder specifically - C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\CarenadoNavigraph\Navigraph
  4. So far as I am aware the data for all the Carenado aircraft goes into a single folder... C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\CarenadoNavigraph DJ
  5. Hi, Yes, the CJ2 uses the Carenado navdata already supplied for the 550 and Phenoms and the CJ2 is already P3D compatible. DJ
  6. Your impression is correct. Take a look at your exe.xml and dll.xml files and see what is being loaded. You may run only one version of SODE at a time... DJ
  7. Actually, I have... DJ Good show - I wish you luck with the new scheme... DJ
  8. Hi, 12Bravo - since the Jetways seem to be the main attraction, you probably need some better structured beta test plans... If users have to move files and folders around you are asking for big trouble. The SODE installer needs to be environmentally aware - it needs to check for incompatible versions, warn the user, not make double entries in the exe.xml and dll.xml files and so on... I don't mean to sound harsh, but I did this sort of thing for 40+ years on systems that are a heck of a lot more complicated than FS ever will be and currently SODE is a pain to get installed and working with more than one airport. DJ
  9. If you did everything exactly as you should, and the sim froze then it could be an error in the exe.xml and/or dll.xml files. The only cure for this nonsense will be for the developer to make the SODE library backwards compatible in each release, and for scenery developers to create a standard discipline for using it. Until then, I consider it to be more trouble than it is worth. DJ
  10. The confusion and technical issues caused by this add-on, and the poor installation procedures and requirements, make it hardly worthwhile. I have had to do so much debugging to install sceneries that insist on using it, that I am seriously tempted not to buy any that do. Just my two cents on the subject. DJ
  • Create New...