Completely unrelated but what problem are you having uninstalling Python?
From control panel you should be able to uninstall it.
If you tell us your windows version and which Python you installed we can try to give you some suggestions to remove it.
I installed python 3.9 as it was one of the plug ins we needed to fix the issue of the liveries per the developer of the liveries(Clint123) something like that.
This was before he came out with the now working liveries manager for the new patch.
Now i am unable to uninstall it because it says it was never installed but I can clearly see it on my C: drive. I am running on windows 10
Please clarify what do you mean by âI can clearly see it on my C: driveâ
I havenât seen the video which Python distribution did you install, Iâm guessing the video provided a link, which one?
When I go into settings /storage/ C: drive, I see everything I have installed in my PC alphabetical.
Unfortunately Iâm not near my pc or I would take a screenshot. Python shows up in there(104mb)
I try uninstalling it but it doesnât let me.
It was on his discord with a link for a workaround to get the liveries working for the new patch.
You say it doesnât let you uninstall, can you tell me which error message it gives you?
If possible capture a couple of screenshots.
As I said it is totally unrelated but if you want to go back to a cleaner config we can help you.
I know this is unrelated to the thread but I need help getting rid of this python 3.9
The error message says âUnable to uninstall because python 3.9 was never installedâ
But when I go into my storage I see that itâs installed in my computer.
I wonât be home until tomorrow so I canât send you screenshots right now.
Thereâs no such message AFAIK. When you get home try to capture the screenshots of what you see and the error message and if possible please find the link you followed to install Python from the developer discord.
Iâll be glad to help you if possible.
Okay thank you, Iâll send you everything tomorrow.
Because nobody actually knows what the real problem is, so there are a bunch of hacks that people think are the solution because for whatever reason things work now, but nobody actually understands the real structure thatâs required. I donât even know if the planes from Asobo actually all follow the same structure, since one thing works for one plane, and something else works for another (and Iâm not talking deluxe or premium planes). Itâs kind of â â â â â â â me off the lack of full documentation on how to get things done.
Can somebody explain exactly why some people think that adding a model.cfg is the fix here? How come my liveries donât need that and many of them work just fine?
The inconsistency of package structure and field values is maddening!
Some people set dependencies on the plane, which seems to have broken now, whereas others have a dependency on propdefs, or there are others with no dependencies. I cannot figure out how the game knows whatâs what.
And thatâs just one concept, texture.cfg files are all over the place in where they point, and so many other consistencies, ie model.cfg. Model.cfg unchanged just shouldnât be necessary.
Yeah, no, Iâm not adding a model.cfg till somebody explains why thatâs a fix.
1 Like
All these âfixesâ are going to break your game at some point.
There has been âfixesâ for FSP, AP, lights and what everâŠ
Do not use these âfixesâ, EVER, or you WILL get bored of always âfixingâ things after EVERY update.
Scenery updates and fixes are mostly working fine, but again, if you donât need it right that moment, then donât use it.
NEVER edit game files! But if you do, be sure to know exactly what you are doing.
2 Likes
âDiscovery requires experimentationâ - Werner Reinhardt.
I like tweaking things, and fixing things. I get enjoyment from figuring out why something is broken, and when I try one thing and another until it works. It feels really good. And if the fix breaks something else, then I get enjoyment to look for it again and make another fix in that.. I guess thatâs just me.
Okidoki I think you can use the same installer you downloaded to uninstall Python and it should work.
If you removed/deleted the Python 3.9 installer download it again, install it again and then run it again but choose âuninstallâ.
Iâve done none of thatâŠall I did was move all the liveries out of my Community folder, started and closed MSFS and then moved the liveries back. Then restarted MSFS and apart from the MB-339 all my old liveries work again.
CorrectionâŠactually Iâve just discovered a couple that are not working for some reason. The Loganair liveries I have for the CJ4 and King Air donât work but they do on the C208B. And Iâve picked random A320, 747 and 152 liveries and they seem to work fine. So a mixed response sorry.
Yep,
like I said, it looks like the planes are developed with differing structures, so thereâs no consistency in how to make liveries work across planes. Frustrating.
So true. Iâm quite happy with the stock scenery and liveries. I;ve dabbled with the working title G3000 mod, but made sure I removed it before updating and then I simply wait for working title to update it. If they donât - no biggie.
1 Like
Iâve just joined this forum because I canât get liveries to show up in my hangar. Yesterday was my 3rd try: I joined Discord, and re-downloaded LiveriesMegaPackVersion11.3.zip. Extracted all and installed selected liveries in my Community folder. They still donât show up!
I have of course installed all âMandatory Updates,â or at least think I have. I have a hunch, though, that one of them may not have installed, because after the DL, I never saw a progress bar when I started the sim. Somewhere in this thread thereâs a suggestion to âreinstallâ an update. How is that possible? And would it help with my liveries issue?
Thanks all,
Mac6737
I did that too. Downloaded the MegaPack through Discord. The liveries I selected are complete and in my Community folder. Not a one of them shows up in the sim.
Oddly, the addon sceneries in the Community folder work fine.
Mac6737
Did you delete all the previous liveries before you install the new update?
I find that with the latest patch, itâs better to clear all your community folder and reinstall the mod one at a time using the latest version, so it doesnât âconflictâ with the older files.