Aerosoft official retail partner for Microsoft Flight Simulator !! 
Click here for more information

Jump to content

bsal

Members
  • Content Count

    223
  • Joined

  • Last visited

Community Reputation

37 Excellent

About bsal

  • Rank
    Flight Student - Crosscountry

Recent Profile Visitors

3082 profile views
  1. Do the people at Lufthansa systems even read the emails you send? Why do they offer such a product if they have zero support for it. Have they communicated with you at all on this issue?
  2. Hi Mathijs just wondering does Lufthansa compile the data into 'flightsim addon' text files and send it to you guys or does someone at Aerosoft compile the data so addons can read/understand the data? To make LIDO airac work fully correct in the FSX airbus only RNAV/RNP procedures need to be changed from 'H' to 'R' type in the PROC text files. Wondering if you could ask whoever compiles the airac for this addon to make the change? Regards Brian
  3. Charts are now upto date thanks guys.
  4. Seems the charts have not updated to the current cycle, departing Palma today via MEROS6B but navdatapro charts still have MEROS5B. Asked a friend to who is a real world FO that uses LIDO and he confirmed latest chart is
  5. The navdata you want to update is called 'Aerosoft Airbus A318/A319/A320/A321' in the navdatapro application. Also make sure you have selected navdatapro in the airbus configurator
  6. Which navdata provider are you using navigraph or navdatapro?
  7. Can confirm navdatapro (LIDO) has coded the descent angle of -3.00 in the navdata while navigraph does not. Maybe that's the issue but the VDEV brick appears to be moving down correctly in the guys screenshots shouldn't the aircraft still follow the VDEV down anyway?
  8. At airports that already have alot of charts this duplicate of old and new is a big pain in the ass, will there ever be a fix for this issue?
  9. Appears the charts haven't updated to current 2005 cycle. Frankfurt has had some procedure changes with the removal of the PSA NDB.
  10. I think there is some confusion here, I thought you are using navdata pro charts app but appears you are not.
  11. Any news from Lufthansa data systems yet on this?
  12. I know it is suppose to be coded as 'H' but the 32bit airbus won't see the VIAS in the FMGC if it's coded with a 'H', I think that's why navigraph still use 'R' for all RNAV/RNP procedures for this aircraft and it works. Hopefully they can change it to 'R' just for this aircraft.
  13. Thanks Mathijs hopefully they will have it changed for the next cycle.
  14. Hi Mathijs I did some more investigating on the issue, for testing I changed the 'H' designator to 'R' in the PROC text file and all the RNAV procedures worked as expected. It seems LIDO uses 'H' for all RNP approaches in the database whle navigraph (Jepessen) uses 'R' for all RNAV and RNP. If you could have Lufthansa data system use an R instead of H that would fix the issue, or this is a long shot a hotfix for the 32bit bus so it understands that 'H' is also an RNAV or RNP approach.
×
×
  • Create New...