Yes, I had the same experience, lol.
I imported a few liveries I and a couple of others had created for the Carenado planes to test things out to see if I could get the planes reorganized so they’re all separate models instead of variants of a single plane. It’s actually really funny how messed up the library is now when I added 13 liveries for 7 Carenado planes in a attempt to pull them out of where they’re sitting as variants of the C170. Unfortunately, no, you can no longer “rename” all planes by renaming one of them. All planes are modular now, and not related to their parent model if you change anything about them. Which, technically, is more logical programmatically. But it was a great way I used to use to organize my library.
I spent about an hour reading the SDK on how liveries are created now, and I’m going to need to spend a couple more days or more on the subject, and do lots of testing, figuring out how to do it properly without messing up the organization of the library if I don’t have all the information necessary to do it. With the added twist now that there’s a new file format for 2024 plane textures.
I think an announcement needs to be made not to try to use 2020 liveries in 2024. We’ve got a lot of work to do to convert them for use. They won’t work as is, at least not without making a mess of the aircraft selection menu, as you saw. All files have to be meticulously edited to a level never known before. The consequences of progress.
It’s going to be super important that we get access to the aircraft.cfg and livery.cfg files for any planes people want to create liveries for so we can keep the library organized. And with the new “Dynamic” concept, livery creation seems like it will be a lot harder for people other than the owner of the plane. I’m sure we’ll learn how. I’m just sad it will be a lot harder to fix the “errors” developers make in UI information since the planes are modularly sorted now. Those detail oriented ones of us, lol.