DegXI_FS Posted February 10, 2023 Posted February 10, 2023 (edited) Hello, yesterday I tried to fly from LTFM to EYVI but when I loaded the SID from LTFM for some reason only 2 waypoints were loaded into the FMC, DE35L and TO021. Then I decided to check if same happen with other procedures and it does, same when i try to add manually the "waypoint it says waypoint not in database". In the default asobo aircraft it loads all the procedures correctly with all of its waypoints. Is the database from the A310 different from the one on the asobo aircraft? I thought they were the same. TIA Edited February 10, 2023 by DegXI_FS
Deleted Account Posted February 11, 2023 Posted February 11, 2023 Heya! Yes, they do use the same database, but I THINK we access the database differently, don't quote me on this though haha LTFM always seems to be a problem, as the airport doesn't exists in the base sim. Which custom scenery do you have, so I can try to reproduce this?
DegXI_FS Posted February 11, 2023 Author Posted February 11, 2023 1 minute ago, gumbyger said: Heya! Yes, they do use the same database, but I THINK we access the database differently, don't quote me on this though haha LTFM always seems to be a problem, as the airport doesn't exists in the base sim. Which custom scenery do you have, so I can try to reproduce this? Not sure how the developer is called but it's the only one available in the marketplace as far as I know. They recently updated their scenery and the ILS frequencys are now workings correctly, which didn't before but procedures still not working.
Deleted Account Posted February 12, 2023 Posted February 12, 2023 So just to make sure, it´s the SceneryTR ones?
DegXI_FS Posted February 12, 2023 Author Posted February 12, 2023 11 minutes ago, gumbyger said: So just to make sure, it´s the SceneryTR ones? Yes, it is.
Deleted Account Posted February 13, 2023 Posted February 13, 2023 Can confirm this is fixed in the next update coming (hopefully) with SU12 🙂 1
DegXI_FS Posted February 13, 2023 Author Posted February 13, 2023 2 minutes ago, gumbyger said: Can confirm this is fixed in the next update coming (hopefully) with SU12 🙂 Great! Thank you for your help!! 🙏🏻
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now