Jon Clarke

Orbx Central will recognise symbolic Links but not shortcuts. See the attached User Guide for Orbx Central page 21: Quote Moving a library to another location Moving a library is painless with Central and can be achieved in a few steps only: 1. Go to Settings > Libraries. 2. Note the directory of the library you’d like to move. 3. Remove the library that you would like to move (remember: this doesn’t delete the actual files). 4. Close Central by right-clicking on the tray and selecting “quit”. 5. Move the directory to the new location in your operating system. This step may take a while depending on your disk speed. 6. Start Central again 7. Open Settings, and then the Libraries page 8. Press ‘Create New Library’ 9. Select the new library location, give it a name and then press ‘Save’. Central will automatically scan the library for installed products, and then configure your simulators appropriately Central User Guide.pdf

Correct. It is an issue with OpenScenery and not the Orbx addon as far as the error message is stating

There are several Goggle available reports on this topic and y=the conclusion is that it is one addon or the other without some serious .ini manipulations of which I am not familiar with. I do know that disabling the Meigs Mesh file helps and also removing the Laminar Chicago Landmarks helps performance but not necessarily compatibility. https://www.helisimmer.com/reviews/review-drzewiecki-design-chicago-city-xp-and-chicago-airports-xp BUT... I WANT TO USE Orbx’S MERRILL C MEIGS AIRPORT, CAN I USE THIS SCENERY TOO? I’m a big fan of that airport too. So, to answer that question, I bought the Orbx Meigs scenery to see how well the two integrate. The short answer is yes, with some creative scenery .ini file management you can get the two to work together, but there are some compromises. For example, expect to lose the Downtown Police Marine heliport. And some changes to the area immediately around Meigs. Overall, by gaining Meigs with the Orbx scenery, you’ll lose a lot of the other details that make that area great about the Drzewiecki Design. Ultimately it’s really up to the user to determine if this compromise is worth it.

Your scenery packs is all wrongly layered and not how Prbx central would have installed the Orbx addons. Here is a correctly layered rework for you scenery_packs.ini

Thanks for your input. I still have cars running correctly with the txt mod placed in Sumburgh roads file but i am sure your mod works.

The TEGB dev told me long tie ago that those addons include Terra Flora trees. Regarding a definitive answer and whether this should be mentioned in the TE addons although it does state that as exampled by your quote. I will defer that to @Ed Correia for a response

I don't use the Organiser so i cannot comment on it except to say that looking at your log and assuming it is reading your addons sequence correctly, then the True Earth addons are incorrectly layered and you have addons like libraries, including SAM Static aircraft above the True Earth addons. Are you using Traffic global? If so then your number/percentage of aircraft settings are too high. See these 3 pics of what I see with Static planes set to off. 2 planes remain. One of which is the prop under the Ryanair plane in your pic: These pics do NOT use the old Mod file, just the EGFF addon. Static OFF and zero percent Traffic Global. Note 2 statics remain: Traffic Global set to just over 50%. No conflict: Traffic Global set too high:

Welcome. The details you provide are very brief so I ask 2 things. 1. Have you also installed the OrbxLibs library addon required for all Orbx airport addons? If not you need to do so from here: https://orbxdirect.com/product/orbxlibs-xp11 2. When you have done that and tested regarding error messages, if you still get them then attach your scenery_packs.ini, As a norm ALL 3rd party airports should be placed above Global Airports. Also note that most Orbx airport addons are designed to work with the True Earth addon region that the airport is in. They will normally work OK , with some caveats, in default scenery but there may be anomalies which would result in an error message on screen.

No I am not. I am only related to my late parents and siblings Last of the Summer Wine etc?

@Polytoximaniac @Sentry11 I have resolved the issue. In the AFL addon is a folder called ZAFL Mesh +48-123 which I had not noticed before. Either remove (which will probably give a scenery error message on screen) or move to the bottom of the scnery_packs.ini. Here are 3 pics showing the conflict gone. Al pics are with TE Washington SD displaying The Tank Farm near Anacortes: At AFL KAWO showing the town: 2nd pic at KAWO over the airport:

I don't have Allan & Burrows. AFL Arlington is top of the scenery_packs layering in my setup. Washington SD under Global airports. No Enhanced Washington installed

Have you used the Configure option in the EGFF Control panel to disable Static aircraft?

@Sentry11 I am seeing the same as @Polytoximaniac at the oil terminal/tank farm. I tend to get default ground textures around Anacortes with AFL Arlington installed, but TE Washington when uninstalled. How is your scenery_packs layered?

I must admit I had not checked that far out from the actual KAWO airport. Need to seethe AFL response. I will ask if we can contact someone at AFL about this.

I have slightly adjusted your scenery_packs.ini by moving your MisterX and OpenScenery files further down the layering. This may or may not have any influence on what you are seeing. If there was an aircraft taxiing through the wall then that indicates you have a traffic programme running. What is it? As a test you could rename your custom scenery folder to Custom Scenery.BAK, make a new one and drag & drop Global Airports and the TE SoCal files plus OrbxLibs into the new folder. This would leave just the relevant files being used without any chance of a conflict. Choose a flight from KCRQ and see what happens. KCRQ is a default Laminar Gateway airport and not an Orbx addon if I am not mistaken so any thing to do with the airport is a Laminar issue. However I cannot see a mesh issue at KCRQ. I attach 4 pics from all views showing what I see at KCRQ. North Ramp right view: North Ramp left view: North Ramp from above: Part of rest of airport. Note that there are lots of planes. I do not have Parked Aircraft enabled and I have disabled my Traffic Global planes: scenery_packs.ini

I can neither confirm nor deny

I am unsure what you are actually seeking here Carlos but I have been using the AddonLinker since it came out with zero problems at all. To have Orbx central work with the linker you need to create a library for addons. Mine is called MSFS Addons. I have it on the same drive as my MSFS installation so that it doesn't take time to copy/paste etc. You would then need to link that new folder (MSFS Addons) to Orbx Central in the normal way. That way, when you want to install a new addon, you can direct it to either the MSFS Community folder directly or into the MSFS addon library, just like you can with any other Library you have created in Orbx central. When it comes to using Linker for a flight you would only tick the addons you want for that flight. Linker then puts a symbolic link into the MSFS Community folder and off you go. Because the community folder now would only contain symbolic links and not actual hard copy addon files, there is no need to worry about sim updates causing issues with your community folder or any of the addons as they are in storage in a non MSFS directory folder so are not interfered with in any way. In answer to the question about the difference between having the mods in the Community folder vs in another folder: you could always just keep dragging and drop the addons you want for a flight into the Community folder and then drag and drop them back into a Library folder when that flight is finished. But why do that? Having all you mods permanently in the Community folder means long load times, vs short load times when using the Linker to choose relevant addons for a particular flight. I have gone to another level with linker. I have made a folder called MSFS Addons, and the subfolders for the world by regions like US,EU/UK, Asia, South America, Africa and Asia/NZ/AUS. I also have a library for Liveries, Aircraft and Utilities and Mesh. Just ticking the mods you want to use for a flight is so simple that is why I use and endorse the use of Linker. Here are a couple of pics. This set up of subfoldrs took only minutes.:

I suggest you do get it and IF we find something wrong that has not been seen or discovered by me or Sentry11, we can contact AFL.

Check your scenery_packs.ini or attach it for me to look at. Also do you have display parked aircraft enabled in XP? If so try disabling it.

I just got this from the Devs. Quote : " That is the MS/Asobo POI that replaced ours so it will be for them to fix and rotate. "

None seen by me either

I will ask the devs to comment. many Asobo landmarks were kept so i am unsure if this is an Asobo issue or something for Orbx to look at.

Thanks. I believe it is compatible but look forward to your info from AFL

I do not believe that this is now planned due to the difficulties explained by Jarrod in his reply: 2. It was an intentional design decision to remove the default-style road overlays in the immediate confines of the airport, including that section of freeway - by design, this will also remove road traffic. Again, this was primarily done out of "best-case-compromise" - as you no doubt know from your experiences elsewhere, the default roads are beautiful when they work, and cumbersome and ugly when they don't. They also exclude some of our other scenery elements, and of course never 100% line up with the photoreal underneath. Whilst we can add custom road traffic, it does come at a serious performance penalty (more so than default road traffic), so we decided to keep this custom traffic limited to the airside and immediate surrounds of the airports - basically areas you are more likely to see when airside on the ground. So in short - performance + visuals came at the compromise of this missing section of traffic. Whilst we can add the traffic as an update in the service pack, my absolute preference is to always prioritize performance, and it would need to be as an optional feature only.

It is actual photo scenery