Users are reporting all CGLs are no longer working im SU12 beta.
Is there a known change to the way CGLs need to be generated in SU12 or is this a bug which will be fixed before release?
Please take a moment to read the platform’s guidelines before you get started!
Users are reporting all CGLs are no longer working im SU12 beta.
Is there a known change to the way CGLs need to be generated in SU12 or is this a bug which will be fixed before release?
I was not able to reproduce this using the sample "KaloAirport" SDK Sample.
Can you send me your project ? See 3) Private Content
Regards,
Boris
Being so close to SU12 release without any confirmation this has been fixed is a little concerning. I've shared the project file almost 2 weeks ago.
This will break almost every 3rd party airport in the marketplace.
We have been able to reproduce the issue with your package but we haven't witnessed it yet on any other package for now so we're not sure if it's project related or a more general issue.
Do you have other airport products on the marketplace that demonstrate this same issue?
Regards,
Sylvain
As mentioned above, facts:
Kind regards,
Marcel
Naming convention in the Community folder does have an influence on what the sim shows. And it's a bit counter-intuitive. 2 packages in Community. One a Smiley face and another just a mustache to place over the Smiley face. Each has a transparent background, and 32bit PNG source.
A package named aaa-rhumbaflappy-c59-aerial (just a mustache) will appear correctly over the rhumbaflappy-c59-aerial (with the Smiley face). If the mustache package is named zzz-rhumbaflappy-c59-aerial, the mustache will not appear.
I believe that alpha-numerically, aaa-rhumbaflappy-c59-aerial is loaded first and has priority, with rhumbaflappy-c59-aerial added under it.
The zip file has the 2 packages. If you rename the aaa-rhumbaflappy-c59-aerial as zzz-rhumbaflappy-c59-aerial, it will not show the mustache, as it is hidden under the Smiley face.
So the package name controls the order of the CGL appearance, but it is inverse in nature.
The problem here is that if you are re-working an airport, your package name should probably be prefixed something like zzz in order to load after any other addon of the same airport. This is because of the excludes, and is the opposite of the CGL project naming. So separating the CGL to a separate project is a good idea, but it should load first in the Community by prefixing it aaa-, and the airport package should be prefixed zzz-.
@rhumbaflappy That's helpful when you have overlapping textures, but MSFS should be handling multiple packages containing the same CGL file, where each one contains textures of a different airfield, without 'losing' some of them to the default textures.
Seems still no progress to fix this issue at your side?
Any update you can give on this general problem and not a scenery addon specific problem?
Marcel
7 People are following this question.