It can’t be just me - NONE of our 2020 gliders are even close to being transferrable to the 2024 Community folder and being properly flyable. They kinda load, and kinda work, but there’s a mix of graphics, package, xml templates, html/js programming, control binding issues for each plane. Note for our planes I made a significant effort to use 2020 support (e.g. like JS GET_FLIGHTPLAN and the XML templates) rather than simply use 2020 supported ‘FSX’ api’s like the gps simvars and XML PartInfo / Animations.
So obviously the only viable approach will be to create a new 2024 package structure and copy elements across cleaning up problems as we go until we have a viable 2024 package. The idea we’ll be reporting all these migration glitches as ‘bugs’ or ‘regressions’ isn’t going to be a viable strategy, much more likely we’ll leverage the resources in the 3rd-party community to work out what basic support in the new sim (like the new templates) we can use/trust.
My point is it’s become increasingly important some Dev Support info focusses on migrating a 2020 package into 2024 rather than the simple “here’s the new docs” baseline we currently have.