Also with this update noticed the cockpit gauges (text) is crystal clear now they were a bit fuzzy before - good stuff

Guys,

I have just posted this in the Robert Young G36 bonanza v2 topic.

Before the upgrade i saved the community folder to a new drive.

I installed the upgrade and then pasted the moved community folder back to where it was.

G36 Bonanza was there and liveries were not,

I removed both those folders from the Community folder and then reinstalled the Turbov2 mod and followed that up with a re-install of the liveries pack.  All working now.

As for the G1000 and G3000, at this time I have not flown the relevant aircraft (other than the G36)

It would appear that this is going to have to be the process for all modded aircraft following upgrades of the core platform.  It would be nice if it was not necessary, but that procedure has worked for all my previous upgrades.  It also pays to update the content folder (toggle all) after each upgrade.

Tony

14 minutes ago, himmelhorse said:

Guys,

I have just posted this in the Robert Young G36 bonanza v2 topic.

Before the upgrade i saved the community folder to a new drive.

I installed the upgrade and then pasted the moved community folder back to where it was.

G36 Bonanza was there and liveries were not,

I removed both those folders from the Community folder and then reinstalled the Turbov2 mod and followed that up with a re-install of the liveries pack.  All working now.

As for the G1000 and G3000, at this time I have not flown the relevant aircraft (other than the G36)

It would appear that this is going to have to be the process for all modded aircraft following upgrades of the core platform.  It would be nice if it was not necessary, but that procedure has worked for all my previous upgrades.  It also pays to update the content folder (toggle all) after each upgrade.

Tony

Hi Tony,

It gets more and more bizarre. There is no rational reason why removing a mod from the community folder, then unzipping the original and putting the contents back in the folder should work, but if you say it does then it must be true. I just cannot fathom what is different, but it's true, the liveries are not loadable unless you either do what you did OR do this: In hanger, load a livery. It will not appear. You'll get the default. Now open a project in dev mode and open aircraft editor in dev mode. Now press "resync" and the chosen addon livery appears!

I can't imagine what on earth Asobo did to mess up the community folder, but they managed to do it! I'm simply baffled that clearly nobody on the dev team bothered to check such a simple thing like seeing if a livery loads, before unleashing yet another update on several hundred thousand or perhaps millions of customers. I'm just staggered by the basic lack of the most rudimentary checks. They need to employ a team of QA people whose sole job it is to start the sim and load scenery, aircraft, check the hanger, check the gauges, and check anything the update could influence.

Edited October 30, 20205 yr by robert young

I noticed many of the liveries were not there after the update too, but since re-starting the sim, they have all been there every time ... try re-starting if you have just loaded the update, would be my suggestion.

3 hours ago, robert young said:

Hi Tony,

It gets more and more bizarre. There is no rational reason why removing a mod from the community folder, then unzipping the original and putting the contents back in the folder should work, but if you say it does then it must be true. I just cannot fathom what is different, but it's true, the liveries are not loadable unless you either do what you did OR do this: In hanger, load a livery. It will not appear. You'll get the default. Now open a project in dev mode and open aircraft editor in dev mode. Now press "resync" and the chosen addon livery appears!

I can't imagine what on earth Asobo did to mess up the community folder, but they managed to do it! I'm simply baffled that clearly nobody on the dev team bothered to check such a simple thing like seeing if a livery loads, before unleashing yet another update on several hundred thousand or perhaps millions of customers. I'm just staggered by the basic lack of the most rudimentary checks. They need to employ a team of QA people whose sole job it is to start the sim and load scenery, aircraft, check the hanger, check the gauges, and check anything the update could influence.

This patch/update whatever they want to call it was a disaster waiting to happen to our community.

I think that they came to their senses and pulled it because some simmers are writing that they got lucky.

They need to get their act together. I've spent a great deal of time and money on this sim and there's no reason for to have to waste all afternoon testing why my USB peripherals are not loading the sim.

Ridiculous!

BTW, the liveries showed up after a few restarts of the sim, even more ridiculous.

They say they have improved the performance on the aircraft selection and liveries page.  It does seem a bit slicker.

My guess is that they have some kind of caching system now that can take it's time to scan and catch up.

That's the only way I can explain it, and if so, the system obviously needs another little 'tweak'. 🙂

46 minutes ago, bobcat999 said:

My guess is that they have some kind of caching system now that can take it's time to scan and catch up.

🙂

Interesting.

This sim needs a manual along with constant updates as patches are released.

5 hours ago, robert young said:

They need to employ a team of QA people whose sole job it is to start the sim and load scenery, aircraft, check the hanger, check the gauges, and check anything the update could influence.

I think this may wake them up mate. I have just heard a scramble of staff getting to desks in their office looking at computer screens for a google version of what QA is, and how they might comply. However, that eventual proposal will have to be referred to a committee for intense scrutinization before the proposal is rejected in its entirety. LOL

Regards

Tony

PS I am still a very happy little vegemite as far as MSFS is concerned .... niggles aside

41 minutes ago, DJJose said:

This sim needs a manual along with constant updates as patches are released.

Hello mate,

I am really surprised nobody has mentioned a manual for MSFS before this. (he says, hunting through previous topics and posts.)

A MANUAL is sorely needed      + 37,592,019,595 bumps

Tony

My liveries are working fine. Before loading any patch I always start with an empty Community folder and then add back in content one by one and check all is OK. If you are going to use non-standard items, that is, Community folder content, then you should expect to have to do this. Not for items in the Marketplace though.

EDIT - take that back. Liveries don't crash sim and can be selected but don't appear on the plane, default livery still there

 

CJ

Edited October 30, 20205 yr by CJ1045

5 hours ago, CJ1045 said:

My liveries are working fine. Before loading any patch I always start with an empty Community folder and then add back in content one by one and check all is OK. If you are going to use non-standard items, that is, Community folder content, then you should expect to have to do this. Not for items in the Marketplace though.

EDIT - take that back. Liveries don't crash sim and can be selected but don't appear on the plane, default livery still there

 

CJ

I did, and many others did, remove their community contents before updating.  For Asobo to now imply that it is a user error that an official update screws up that folder is a bit much!. If you update Windows 10, the update doesn't wipe, move or stop access to your stored emails, documents or programs!

31 minutes ago, robert young said:

I did, and many others did, remove their community contents before updating.  For Asobo to now imply that it is a user error that an official update screws up that folder is a bit much!. If you update Windows 10, the update doesn't wipe, move or stop access to your stored emails, documents or programs!

I agree and it's even more bonkers to state that it's user error when the average mortal user doesn't know an update is going to install until they launch the program and get the update message.

In the field I work in, the expected functionality of the update install process would be to look for any content that could be a concern, move it to a temporary location, perform the upgrade, and restore the content without the user intervening.  The whole point of automated installs is that they are automated.  And rigorously tested for known conditions prior to release.

 

Edited October 30, 20205 yr by Stoopy

I'm having the same problem with all my aircraft and all liveries. I can't change liveries within MSFS. The livery change is not working in [PROFILE][MY HANGAR][LIVERIES] nor when I go FLY.

However, if I change aircraft/livery within MSFS (livery do not change) and then restart MSFS the aircrafts appear in the livery choose before restarting MSFS.

This might be a clue.

PS
Otherwise I think the update is great.

 

 

The freeware developer community has already figured out a fix to the livery issue. Updated paints will be forthcoming.

https://flightsim.to/blog/flight-simulator-patch-1-10-7-0-brakes-liveries-heres-how-you-fix-it/

Lee

Being a bit lazy - is the 747 reversed livery on one side of the plane cured yet?

 

CJ