Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Bumped - Is there still a limit to number of addon scenery XML files in P3Dv4.2 ?

Featured Replies

Has this been fixed yet in v4.2?

(I did a search in both the AVSIM forum here and the LM forum, but did not find a definitive answer in the posts I found. So not sure if it is still an issue or not.)

Rick Ryan

Hello Rick

The Prepar3D v4.2 Client update Includes the following below,  I think this is what you are referring to ? 

Fixed issue that could cause incorrect or corrupt textures to load when having several scenery add-ons installed through the Add-on Package setup

 

 

 

From past and present tests, there are still problems with the number of add-ons in P3Dv4.2. Could not determine however how the problem originates? From the products added-on or LM. The critical point seems to be above 30 add-ons.

Cheers,

Pierre

Pierre

I9 14900K 5.5 64gb ram 6800 RTX5090 Asus Strix Gaming E

  • Commercial Member

Hello @ll,

there are two things to keep in mind:

1. The issue was not related to the number of addons, but to the number of add-on.xml files. That is not the same thing. You can have any number of addon components in the same add-on.xml. I have a customer who literally has hundreds of sceneries referenced externally without problems - but he only has about 20 XML files.

2. The texture corruption often happened when scenery addons where referenced by always splitting "scenery" and "texture" subfolders into two separate addon components. It is not necessary to do that, scenery components can be added just like it always was - by targeting their top folder, the "scenery area", as a component of type "Scenery" - this implicitly includes the texture subfolder.

Best regards

 

Edited by Lorby_SI

LORBY-SI

@Lorby_SI

Oliver, 

How does this corruption manifest itself? I have about 60 aircraft addon.xml and 25 scenery addon.xml running v4.1.

Besides slow loading of the sim, what else has been affected?

Thanks for your advice.

Henry

My MSFS 2020 repaints: Flightsim.to - Profile of HStreet

Working on MSFS 2024 versions.

  • Commercial Member
21 minutes ago, Henry Street said:

@Lorby_SI

Oliver, 

How does this corruption manifest itself? I have about 60 aircraft addon.xml and 25 scenery addon.xml running v4.1.

Besides slow loading of the sim, what else has been affected?

Thanks for your advice.

Henry

Hello Henry,

I have yet to experience this myself. But from what I know, you will have wrong, missing or corrupted textures on all kinds of objects.

The issue was supposedly fixed with 4.2, but I still suspect that you can run into texture loading issues when splitting up (all your) scenery area definitions. Because if you do, then the simulator has to parse through all of their texture folders all the time - it doesn't know that the texture component that you added is only valid in a limited area! This could possibly lead to textures with the same file names overwriting each other (so you get the wrong texture on an object), or, it could just generally take too long to parse and then load textures in time so they get corrupted.

Mind you, that is just my personal theory.

Best regards

Edited by Lorby_SI

LORBY-SI

I've had problems with effect textures not loading as soon as I went over 35 or so effect folders defined via xml. I consolidated those into one, which solved the problem.

Best regards, Dimitrios

9950X3D - 64 GB - RX 7900 XTX - TrackIR - Power-LC M39 WQHD - Honeycomb Alpha yoke, Saitek pedals & throttles in a crummy home-cockpit - MSFS for props, P3D for jets

All the problems I had with textures as a result of too many xml files went away with 4.2.  Before, I had to disable the ones I wasn't using with Oliver's Addon Manager.

In my case, I knew right away when I had too many because the default F-35 would appear jet black in the initial create-a-flight menu.

Now if only LM would release a hotfix for the blasted menu problems in 4.2...

Regards

 

Bob Scott | President and CEO, AVSIM Inc
ATP Gulfstream II-III-IV-V

Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE
Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro
Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case

Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090
Samsung 55" JS8500 4K TV@60Hz,
3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU
Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro
PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box

Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090
Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus,
TM TCA Officer Pack
, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.