westbros Posted February 11, 2020 Share Posted February 11, 2020 Operating system: Windows 10 Simulator: Prepar3D v4.5 Screenshot: Issue: Hi. I recently upgraded to Orbx Central from FTX Central 3. I also migrated most of my Orbx products from my small C drive to my much larger D drive. Since then I have been noticing problems in several addon airport sceneries. For one thing there seems to be elevation issues - I realise that this can often be sorted out through the Vector AEC, although this doesn't always work and I have to physically remove the airport vector bgl file from the directory. All of the adjustments that I had previously made with Vector were lost when the migration took place, and I will now have to check and adjust every airport individually. It's a shame that we weren't warned that this would happen when migrating, as I would have made a note of what adjustments I had made before starting the migration. The main issue that I would like to raise today is that I seem to be getting default scenery popping up in my addons, like default jetways for example, or the aircraft position seems to be wrong (aircraft sitting with its nose inside the terminal building for example), or I'm getting floating airport vehicles (Flytampa Amsterdam). All of this has appeared since the migration. I have also spotted that many of my Orbx products now sit at the top of my scenery library and that you have now implemented the xml method which makes it impossible to move the scenery layers up or down. At the top of my scenery library are Orbx Libraries followed by my Orbx airports. After that comes Orbx England and then Open LC Europe. All of my other non-Orbx addons sit below all of this. Vector and Base all sit towards the bottom of the scenery library, as does FreeMesh. Correct me if I'm wrong, but I thought that many airport addons need to be positioned higher in the library than things like regional sceneries. I'm pretty certain that my Orbx products like Open LC Europe were previously positioned much lower in the library, and we could move them because the xml method wasn't used. Could the new layering be causing my problems? I would appreciate your advice. I was assured by you that the previous issues with the migration that many people had complained about had been fixed with the latest version of Orbx Central. For me it has been anything but a smooth transition (check out my previous posting). Thanks. central.log Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.