Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

A Livery can kill MSFS

Featured Replies

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. 

 

 

 

Bob if you fly the A320X from FlyByWire, their installer alerts you to a faulty livery when you use it.

It is a pity MS2020 doesn't have a similar feature built in. Excuse my ignorance in this - I have no idea how difficult that would be to implement within the Sim.

Ray

I can not speak officially, but in my case - absolutely yes.

I recall when this happened to me I was somewhat amazed this could be the case but never really got a good answer as to why.  The fix was simple enough, remove the offending livery.

CPU: Core i5-6600K 4 core (3.5GHz) - overclock to 4.3 | RAM: (1066 MHz) 16GB
MOBO: ASUS Z170 Pro |  GeForce GTX 1070 8GB | MONITOR: 2560 X 1440 2K

Yes, we have to be careful especially with liveries. I saw one today advertised as 10K -- yes, 10K -- and decided to skip it, even though it was one I wanted.

MSFS 2024. Primary Planes: Black Square TBM850, Duke, Baron, Caravan; A2A Comanche; FSReborn Phenom; Fexix A321; PMDG 737-7, 777: Utilities: Active Sky (Passive Mode); BATC, FSLTL.

1 hour ago, Bobsk8 said:

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.

So, you didn't re-installed Windows this time?.

Cheers, Ed

MSFS2020 Steam  // Rig: Corsair Graphite 760T Full Tower - ASUS MBoard Maximus XII Hero Z490 - CPU Intel i9-10900K - 64GB RAM - MSI RTX2080 Super 8GB - [1xNVMe M.2 1TB + 1xNVMe M.2 2TB (Samsung)] + [1xSSD 1TB + 1xSSD 2TB (Crucial)] + [1xSSD 1TB (Samsung)] + 1 HDD Seagate 2TB + 1 HDD Seagate External 4TB - Monitor LG 29UC97C UWHD Curved - PSU Corsair RM1000x // Thrustmaster FCS & MS XBOX Controllers

  • Author
Just now, edpatino said:

So, you didn't re-installed Windows this time?.

No, but I reformatted my SSD....LOL

 

 

 

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.

My Liveries | FAA ZMP | PPL ASEL |
| Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |

 

 

11 minutes ago, ryanbatcund said:

It's not it a big deal ..(freezing your sim I mean)

Hi Ryan, yes, that's right, but just in case you already now is your livery!, LOL

Edited by edpatino

Cheers, Ed

MSFS2020 Steam  // Rig: Corsair Graphite 760T Full Tower - ASUS MBoard Maximus XII Hero Z490 - CPU Intel i9-10900K - 64GB RAM - MSI RTX2080 Super 8GB - [1xNVMe M.2 1TB + 1xNVMe M.2 2TB (Samsung)] + [1xSSD 1TB + 1xSSD 2TB (Crucial)] + [1xSSD 1TB (Samsung)] + 1 HDD Seagate 2TB + 1 HDD Seagate External 4TB - Monitor LG 29UC97C UWHD Curved - PSU Corsair RM1000x // Thrustmaster FCS & MS XBOX Controllers

  • Author
15 minutes ago, ryanbatcund said:

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.

OH OK. I posted on the download page the problem I had, but didn't want to mention which specific one it  was on my post, thinking that maybe it was just me that had a problem with it. 

 

 

 

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.

My Liveries | FAA ZMP | PPL ASEL |
| Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |

 

 

@Bobsk8 I uploaded a new file with the fix....sorry for breaking your sim hehe!

https://flightsim.to/file/5787/red-stripes-livery-for-carenado-pa44-seminole

My Liveries | FAA ZMP | PPL ASEL |
| Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |

 

 

Just now, ryanbatcund said:

@Bobsk8 I uploaded a new file with the fix....sorry for breaking your sim hehe!

https://flightsim.to/file/5787/red-stripes-livery-for-carenado-pa44-seminole

That there is one dapper-looking livery Ryan.

So what causes the liveries to crash the sim?  Is it a fallback texture or something like that?

Rhett

7800X3D 96 GB G.Skill Flare  Gigabyte 4090  Crucial P5 Plus 2TB

5 minutes ago, Mace said:

That there is one dapper-looking livery Ryan.

So what causes the liveries to crash the sim?  Is it a fallback texture or something like that?

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.

My Liveries | FAA ZMP | PPL ASEL |
| Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |

 

 

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.

 32GB DDR4 3200Mhz  i7-9700K  RTX 3060  12GB GDDR6

1 hour ago, ryanbatcund said:

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.

How do you fix a livery? I know I have several I really like, but can't use, because they will cause the sim to crash.

 32GB DDR4 3200Mhz  i7-9700K  RTX 3060  12GB GDDR6

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.