ColinM9991

Try both out now, you'd be doing me a massive favour in helping test. They're both available via the links above I did re-run the downloader script earlier today so I can say with confidence that you should have no issues in downloading the official liveries.

Right, sorry for the spam. v0.0.10 is now released which contains the 3rd party livery support. https://github.com/ColinM9991/Livery-Installer/releases/tag/v0.0.10 I've also created a repository for the PTP download script (which I've documented in the readme of the installer) https://github.com/ColinM9991/Livery-Downloader The latest download scripts will download only the PTP and Icons, since the configs aren't necessary. I've also removed the 737NGX so only the P3D 737NGXu, 747 and 777 liveries will be download. Please test, troubleshoot and report issues here or via DMs. There is a note around troubleshooting in the installer README which I recommend checking out. Now I need to get back to my day job 😅

See page 2 or 3 for my livery downloader utility. This downloads directly from PMDG's storage servers. This will download the liveries for a separate app that I'm developing which will allow you to install them. I'm planning on creating a release later with my app. I still need to improve the error handling but I can develop iteratively with subsequent updates

Very close now to adding support for 3rd party liveries. I've taken a slightly different approach to OC2 in that importing a 3rd party PTP makes it available in the catalog of available liveries (which means copying the PTP to your liveries repository directory) Then you can install it there. You'll be able to delete custom liveries too via the normal UI. Right now it's a single import per livery as you can also set the custom icon. I'd like to eventually add support for bulk importing. Not sure whether I'll support livery exporting as I don't think there's much of a market for that given the aged nature of P3D and market share. This app is mainly to allow people to continue flying the old school stuff

I've opened it up for now to get some test candidates. Please note that, as mentioned previously, you do need to whole liveries directory that's created via the script I shared on page 3 of this thread. Also as mentioned, the PTP decryption passphrase isn't distributed via the app and this is required. Please DM me if you require app support. File logging doesn't really exist in the app yet but I will add it over the week GitHubGitHub - ColinM9991/Livery-InstallerContribute to ColinM9991/Livery-Installer development by creating an account on GitHub. Version 0.0.1 is released here. The application is self-contained so you won't need to install .NET Core if you haven't already got it https://github.com/ColinM9991/Livery-Installer/releases

Bit of a busy day today churning through code for this application. It's been over a decade since I last used WPF in .NET so it has been fun to get hands on again. Unfortunately my development time is limited to weekends as I'm also working Monday to Friday as a developer. Hoping to have this wrapped up over one of the coming weekends. The application can now Extract the PTP Copy the "texture.ZZZ" directory over to P3D Merge the INI files Install the panels configuration into P3D\PMDG\Variant\Aircraft directory Uninstalling a livery performs these steps in reverse. I wrote a little parser for the INI files. It preserves all fltsim.X entries at the top of the file. When uninstalling, it'll determine whether it needs to automatically recalculate the indexes of all fltsim INI entries. For example, if you have 5 liveries installed and uninstall livery #2, the application will decrement the fltsim.3, fltsim.4 sections by -1. Due to the nature of the fltsim sections being index based, you can install many liveries at once but they will be pushed to a queue to prevent race conditions. And now it is time for food and TV P.S; could somebody DM me a livery that contains multiple embedded liveries? I haven't been able to find any yet and would like to make sure my application can handle that.

A work in progress. This will be for P3D V5 as that's the only one I have. Note: this does NOT distribute PMDG's liveries. Their liveries are copyrighted (as per PMDG) and redistribution is prohibited. You WILL need to have your own backup of the liveries. As there are so many potential combinations of folder structures, this will only work with the folder structure produced by my scripts on page 3 https://www.avsim.com/forums/topic/695375-pmdg-oc2/page/3/#findComment-5768330 Maybe in the future, if PMDG are sweetened to the idea, I could enable this app to redistribute the liveries. That's not planned for now though as I do not intend to violate their terms. Also, this application will NOT ship with PMDG's decryption key. I'm afraid you will have to review the alternative options out there to find the key. There is however an input on the Settings page in which you can enter the key so the installation process can function as normal. Screenshots show dark mode, but I am aware there may be users with visual impairments. I care deeply about accessibility so I will work on alternate colour schemes which you'll be able to change in the Settings page.

For one valid avenue, see my response prior to the one that you quoted - that'll allow you to download the liveries by way of the same process that OC2 used 😉

I did offer to host the PTPs for PMDG to distribute throughout the remaining P3D community-base and unfortunately they said the liveries are copyrighted. I'm unsure as to who exactly is the copyright holder, since the liveries will have been contributed by many different livery makers, but that is the response I was given.

Hopefully this is allowed. In a similar fashion to VHOJT, I've prepared a Python script which will download the liveries from PMDG's CDN in the same way that OC2 did. Feel free to review the source of run.bat and src/main.py. PMDG: you did ask that nobody redistribute the liveries and, in the legal sense, I'm not redistributing them. However, if you'd like for me to pull this script down then please let me know here or tag me in your Discord server. I've shared this because, frankly, the PTP extractors are a bigger concern in my view since they expose a private password used by PMDG. To run: Simply install Python (you'll be prompted to do so if the script doesn't detect it) and then launch run.bat https://drive.proton.me/urls/A5T2W02BRM#qZ2nqWKkkczo Frankly, I'm frustrated with PMDG's poor communication around the impact this change would've had and I didn't expect the offline PTP livery installation functionality to be impacted.

I've decided to register after seeing this thread. It's great to see this issue being discussed somewhere. Although I don't own 2024, I have flown the tech alpha and have watched many streams as this behaviour absolutely is noticeable across streams and videos. I do own 2020 which I picked up when it launched. Having flown a real Cessna 172, that's my only baseline to compare against. MSFS 2020 has always been extremely twitchy, wobbly and sensitive on pitch across all aircraft - including the C172. It gets worse with faster speed with heavier aircraft that fly like they're near weightless. It was very disappointing to try out the 2024 tech alpha only to discover the same issue with pitch being far too sensitive even with 25%, 50%, 80% and 100% curves on a Honeycomb Alpha, Boeing TCA Yoke and on a RealSimulator FSSB. That same behaviour is more than obvious in any streamer videos that I've seen from Squirrel, V1, Kip, While I appreciate different hardware will behave differently (hence why I tested 3 that I own), if every other game/sim (X-Plane, DCS, IL-2, Falcon BMS) behaves as expected across a variety of aircraft while MSFS demonstrates a silly twitchy behaviour on all aircraft - that ultimately is a problem of the one sim, MSFS in this case. Incidentally, the A2A Comanche is the only aircraft in 2020 which flies like an actual plane.