Msfs Free Liveries

[Carmine Osterland]

Justgot a new PC and have installed MSFS20 and all my addons etc. All working well. I have redownloaded liveries ftom flightsim.to for the ATR-600 and extracted the zip files to my community folder within MSFS. When I open MSFS and select the ATR-600 - only the liveries that come with the ATR are visible, and none of those that I have downloaded and extracted to the MSFS community folder are visible. I can see that they are in the community folder, but have no idea as to why I cannot see or access them within MSFS. Any thoughts or suggestions?

I remember when files came with Readme.txt that explained what addon version it was for, how to install, where you'd find it in your game. Everyone just seems in a race to package stuff up and throw it on the internet now like it's some kinda race.

On Flightsimto it is all nicely categorized. In the search bar you can type ATR and then in the dropdown choose the Asobo ATR Category (should be MS imho). All liveries for AS ATR plane then show up with a new searchbar for a specific livery in that category.

I tried going to my settings for the Fenix Livery Manager to set it to my custom location so that I can use MSFS Addons Linker. But for some reason it's not working. Whenever downloading the liveries, it only shows up 2 json files. Anyone know how to properly set this up?

What I did was download the Fenix liveries to the MSFS Community folder. I have MSFS data set up in folders on a different drive. So,I have a folder for the Fenix 320 and a folder for A320 liveries. Move the files from the Community folder to the new folders Check them off in the Addons Linker and it should load into the simulator ok.

Okay, move or copy the folder over to the new location? If you move the original folder, then when you download new liveries using the Fenix Livery Manager, it won't find the folder to download the liveres to I'm assuming?

If I drag the fnx_liveries or whatever it is called into my addon linker folder and enable it from there, will it create the sym_links for that folder on my second hard drive? So that the liveries I DL from the Fenix app show up there?

I can't seem to activate/deactivate single liveries with the B2 - it's one in, all in (I have the same issue with PMDG liveries) I had no problems with activating single liveries in the previous Fenix version, and still activate single liveries in all my other aircraft with the addonlinker The folder structure in B2 seems to have changed, preventing this, or what am I doing wrong with the B2.

With B2, all the liveries are combined into one folder in the community folder. The folder name is fnx-aircraft-320-liveries. To be able to install/remove liveries from Livery Manager, the folder has to be present in the community folder.

That's because by checking these items they are directly copied into the root community folder, so you'll have "fnx-aircraft-320-VOExxxx" in the community folder. For B2 to recognize them they have to be inside the fnx-aircraft-320-liveries folder, though.. Not sure how to do this with AddonLinker, but I'm quite sure it's possible (because it's a great tool).

Support has been helping me with this issue for these last couple of days. Try to deactivate whatever antivirus/VPN Software you have installed. If that doesn't work, try to connect to a different country using a VPN software (The latter worked for me).

Don't know whether this will help anyone, but when I downloaded A310 liveries from inimanager, they didn't appear in my MSFS A310, under 'liveries'. So I checked my Community folder, and the liveries were not there, but they were in the main Microsoft Flight Simulator folder. I then moved them into the 'Community' folder, and now they are available.

Dose anyone know of anyways to show the correct Airline liveries at the right airports, for example I am seeing Frontier Airlines at Heathrow airport, I want to make flight simulator a realistic experience but its hard to come by at the moment.

Its quite difficult to alter this. There are static options on flightsim.to called Static AI that attempts to correct this but its limited and you have to turn static aircraft down to zero in the sim settings to prevent double parked aircraft. And it does also require having models and liveries such as IVAO to make it work. Its not very satisfactory.

I learned something today about the effect a defective livery can have on MSFS, at least it did in my case. After a successful flight as usual in my DC6, I decided to set up a flight for the Seminole. I had downloaded a livery from Flightsim.to, and dropped it into the community folder after extracting it. I also decided to check to see if there were any updates for any of my market place add ons in content manager, and there was one for the Key West airport I purchased months ago, so I installed that.

Now I started up MSFS, and selected the new livery for the Seminole, and spawned it at KEYW to see what it looked like. As soon as I hit Fly Now, I got a CTD, which I haven't had in many months. I restarted MSFS, and the blue line that appeared while it was loading, moved extremely slowly, like I was on a hard drive instead of an SSD, After a couple of minutes of watching the blue line slowly creep along, finally get to the end, and that was it. Didn't get to the main menu screen to start a flight, just sat there with the blue line all the way at the end. I shut down MSFS, and tried the same thing, with the same result. Now I figured a restart of the PC would solve the problem so I restarted, restarted MSFS and same exact thing happened.

Now I am starting to get really concerned. The only two things I changed were the Livery and updating the Keywest Airport. I thought, if the airport is the problem, this is not good, because I can't even get into the program to uninstall the airport. So the only thing I can try is remove the new livery from the community folder, which I did. I restarted MSFS, and the blue line moved at normal speed, MSFS started up as normal, and problem solved.

The reason I am posting this is because I learned that something as simple as a livery, ( which had been tested for SU6 according to the download site,) can cause a real problem in getting MSFS to run properly. This is another reason when I change things in a sim, I only like to change only one thing at a time, rather than two or more, so if one of the new additions creates a problem, it is really simple to roll back what I added.

That's my livery - it's the only one I forgot to update when I batch updated all my Carenado stuff a little while ago. It's not it a big deal ..(freezing your sim I mean) You just remove it from the community folder till it is fixed. I added a fix to your post over at that site and will upload a new one when their site stops being slow hehe.

People are pretty responsive over there so I'd just say what issue you have (not deduct any stars until they can find a fix) and then rate your download after it's all resolved. That one guy rating my Seneca paints as 1 star got past the long filenames bug apparently everything is a okay.

Asobo changed something again (seriously they change things back a forth a few times - I've seen it with repaints - there would be a dollar sign in front of something, then it's behind etc etc) - in this case, @Tim-HH found a tiny change that I missed - it was simple dropping the model.03 to just 'model' in the model.cfg. I spent a lot of time looking for the issue but it took an expert repainter like Tim to find the real issue haha.

I learned about this with SU5. Before then, I'd never experienced any crashes due to incompatible liveries. Then with SU5, I started experiencing the same thing. I soon discovered, through a lot of troubleshooting, that liveries can cause crashes with not just an aircraft you select to fly, but also with AI traffic that uses the bad liveries. So, sometimes you will have a livery in your community folder for some time without any issues, but once that livery is loaded with an aircraft in the area you are flying, that crash can happen at any time. If the sim is loading when it gets to a faulty livery, it can stop the loading completely, usually with a CTD, but not always.

3a8082e126