davewing

I'm not sure if IRL the A320 has HUD and ROPS?

Glad to hear it's working. At least you can fly to the airport properly now. The markings and signs are wrong; they'd have to be changed in WED. Since I only fly VATSIM and use Navigraph maps, this doesn't make much of a difference for orientation. For those who use TG, it might. I wouldn't hold out hope for an update from TalModels. I can't remember this developer ever releasing an update for their scenery. Have a great day.

The problem with VTBS Taimodels is that although the new runway was added, the renaming of the runways in the apt.dat file was not carried out. Here's a patch that should work. Replace the original apt.dat (make a backup first!) with this one. Please let me know if it worked for you. apt.dat.zip

Thanks, that explains a lot. Especially XP crashes in certain scenery and airports that keep recurring. However: I had two test flights yesterday under XP12.2 (EDDH-EGNX and EGNT-EIDW). I'm using ORBX_GB_TE like @mooney man . I didn't experience any CTDs. While approaching the British coast (FL350), I experienced some CPU spikes, but nothing in the red zone. The FPS was also manageable, although there was a drop compared to XP12.1.4. Overall, I couldn't reproduce the CTDs that @mooney man described. The flights were smooth, no problems with plug-ins, the 12.2 clouds look fantastic, although at the expense of fps. Need to find a reasonable way in the graphics settings, especially at complex airports with a high density of objects. MacPro, 3,2 GHz 16-Core Intel Xeon W, 96GB RAM, AMD Radeon Pro Vega II 32GB, Sonoma 14.6.1

I assume this has nothing to do with @mooney man 's ORBX problem? Because south of EDDM there is no ORBX-TE scenery. But it seems to be the same process. What's interesting is the high altitude at which this happens. Normally, you have a graphics overload problem at low altitudes.

I'm sorry to hear that. I know that line (Art controls are modified) all too well. I often read it as the reason for a CDT in my logs. There are a few articles about it, but there's no clarity. It seems to be a Mac issue. I'm still on an Intel Mac (MacPro 2019, 16 Core Intel Xeon, 96GB, Radeon Pro Vega II 32GB) and will try 12.2 soon. I'll post the results here. I eliminated all JPGs from the ORBX-TE sceneries, which was 235 GB!!!

What's next? Drones? Wingsuits? Flying hot dogs?🤣

Let's see what happens. I have the JPGs in every ORBX scenery. Since they're really useless, I'm going to delete them.

Since I was planning to upgrade to 12.2, I read these posts with great interest. Thanks everyone for the detailed descriptions. What I can confirm: In 12.1.4, there are virtually no problems with ORBX_TE. I did occasionally experience CTD at specific airports, which I was able to partially resolve by, for example, using the less dense grass version of LGSM Samos payware. Or by removing a .png from the orthos in LIEE Calgari, which covered the entire airport in addition to the .dds ortho tiles. Anyway, these reports don't encourage me to update to 12.2. I'll probably stick with 12.1.4 for a while. A note for @mooney man . I've found that CDT on Mac is often associated with overlapping Ortho tiles. In the ORBX Ortho folders (in this case Orbx_C_GB_Central_TrueEarth_Orthos), you'll find two files for the same tile: a .dds file and a .jpg file. It might be worth trying, for example, to remove all .jpg files. In my experience, the scenery displays perfectly if you remove some of the duplicates. At least, that's solved some CTD problems for me. It could be that the Mac graphics cards may have problems loading two images for the same tile.

Here's a patch for the Aerosoft payware LGSA with corrected runway designators (11L/29R, 11R/29L). This allows ToLiss aircraft to fly IFR approaches. Be sure to make a backup from the original before installing. apt.dat.zip

We're used to excellent sound add-ons from Mango Studios. I was therefore surprised by this first scenery. Very well done! Keep it up!

I'm following these in-depth discussions with great interest, and since I'm not an airline pilot, I can't contribute anything. I'll just say this: I think this is a fantastic process. The input from the knowledgeable people here and the efforts of the ToLiss team to continually improve this fantastic Airbus simulation, taking all aspects into consideration, cannot be emphasized enough. Thank you.

Thanks to your help, I was able to solve the problem. I formatted it in non-case APFS, and it worked! You saved my day!!! I have one more question: Is it a good idea to copy the entire CUSTOM SCENERY folder, including the scenery_packs.ini file, to the external hard drive and then add a symlink to just that folder? Or is it better to link individual scenery files?

Thank you again for your kind efforts. I was on vacation for a few days, hence my late reply. I hadn't noticed the capitalization issue in the special line until now. I imagine your investigations are on the right track. My next step will be to reformat the SSD. We'll see what happens...

Thank you for the detailed explanation. The spelling seems to be fine. However, next I'll take your last suggestion and format the SSD as APFS.