7 hours ago, Dominique_K said:

And, it would be nice if the download didn’t bring with it all their liveries yet again : waste of a capped bandwidth, waste of SSD space.

Hrmmm... I uninstalled all those Asobo liveries several weeks ago. They were NOT downloaded again during the WU6 update process.

There must be something different about how you and I went about either uninstalling the liveries, or how you and I went about doing the WU6 update.

Or maybe it has something to do with which version (Steam or MSStore) we are using.

Would you be interested in investigating further?

...jim

 

Edited September 8, 20214 yr by JimBrown

7 hours ago, ThrottleUp said:

Just curious and wanted to know what the restarting does. Is it something to do with the Registry? Thanks for any info 🙂

It is not suggested by Asobo as far as I know and the sim does not ask you to restart after doing the update so it is probably a completely unnecessary step. It is born of my OCD when installing software (or doing a major multi GB update) to always restart before diving in.

 

4 minutes ago, JimBrown said:

Hrmmm... I uninstalled all those Asobo liveries several weeks ago. They were NOT downloaded again during the WU6 update process.

There must be something different about how you and I went about either uninstalling the liveries, or how you and I went about doing the WU6 update.

Would you be interested in investigating further?

...jim

 

I suppose that I selected them through a keyword like xbox or kenmore etc. in the content manager and deleted them in block. I didn't keep track of the procedure then. The Aviator (non xbox) liveries were not redownloaded. 

Two things would make the update process proceed in a less confusing manner. It’s actually logical if you think about what’s going on, but a little too manual.

First, the option to allow store apps to update every time Windows starts is needed. Not sure what the algorithm is, but that doesn’t seem to happen. I usually have to manually update.

Second, the Content Manager updates such as the World Updates should be a scripted part of the sim update. Have the routine automatically call Content Manager and begin downloading any updates.

Of course as soon as I say that, if they did that, there will be people complaining that their bandwidth is being used or they didn’t want to update item X because they’re sticking with version 1.2.3.4 forever because they read that the updates cause issues. It would probably be a no win situation. 

6 minutes ago, JimBrown said:

There must be something different about how you and I went about either uninstalling the liveries, or how you and I went about doing the WU6 update.

I suspect I know why I ended up with them again, after having removed them previously . I did not click the individual items selectively to update in the Content Manager. I selected using the button to ‘update all’. That was probably the open invitation to reinstall them…..

8 hours ago, Bert Pieke said:

That is truly a waste of time... and accomplishes nothing... Sorry!

Why is it a waste of time??

 I for one vote this is the best approach, it's a 5 second step, better then having to copy and paste all to a different folder. 

Just now, RaptyrOne said:

I suspect I know why I ended up with them again, after having removed them previously . I did not click the individual items selectively to update in the Content Manager. I selected using the button to ‘update all’. That was probably the open invitation to reinstall them…..

I did select the updates one by one as I flushed out all the challenges, bush trips etc. that I am not interested in.

7 hours ago, bobcat999 said:

I really dislike this mythology that is put out there with no logic - it just wastes people time.  It is like the people reinstalling windows and the whole sim all of the time to fix something that is normally a simple config error - crazy!

Agreed. And there’s a lot of it on forums. Folks assume things with no understanding of the actual or underlying process.

People wouldn’t make the same assumptions with physical things like a building or a car, but they assume digital things like software is simple.

This current version of MSFS is way more complex than P3D or FSX. An order of magnitude more complex. That’s not an excuse for bugs, but the “wave a magic wand” thinking is off. 

8 minutes ago, CarlosF said:

Why is it a waste of time??

Besause, as has been stated many times before. It has zero effect on the update process. Once again, the update process does not fiddle with the community folder at all!

Edited September 8, 20214 yr by Rimshot

10 minutes ago, Rimshot said:

Besause, as has been stated many times before. It has zero effect on the update process. Once again, the update process does not fiddle with the community folder at all!

Don't tell me, tell that to MS, here is what they suggest you do. So renaming the community folder DOES accomplish something.

Download Instructions

1. For PC users: Some packages in your community folder may not have been updated and, as a result, may have an unexpected impact on the title’s performance and behavior. Please move your community package(s) to another folder before relaunching the title if you suffer from stability issues or long loading times.

Edited September 8, 20214 yr by CarlosF

13 minutes ago, CarlosF said:

Don't tell me, tell that to MS, here is what they suggest you do. So renaming the community folder DOES accomplish something.

Download Instructions

1. For PC users: Some packages in your community folder may not have been updated and, as a result, may have an unexpected impact on the title’s performance and behavior. Please move your community package(s) to another folder before relaunching the title if you suffer from stability issues or long loading times.

What that is saying is that after the update process is finished and IF you experience any impact on performance and/or behavior, THEN start messing with the Community folder.

It does not say you need to do anything to the Community folder before doing the update.

...jim

Yep, the IF word is key. Everyone seems to misread or misunderstand that rather straight forward sentence, twisting it into some sort of doomsday warning.

12 minutes ago, JimBrown said:

What that is saying is that after the update process is finished and IF you experience any impact on performance and/or behavior, THEN start messing with the Community folder.

It does not say you need to do anything to the Community folder before doing the update.

...jim

Whatever, to each his own.

To be on the safe side so I don't end up complaining about CTD here in AVSIM..what I do, is to rename the community folder before the update (even if the update does not do anything to it) launch FS so to make sure the update went fine, fly around a bit,  if all ok, then I go back and rename the folder to its original name. That is MY process,  its NOT a waste of time and it DOES accomplish something. It has worked for me, cause I haven't had one single CTD...yet!

Edited September 8, 20214 yr by CarlosF

2 minutes ago, CarlosF said:

Whatever, to each his own.

To be on the safe side so I don't end up complaining about CTD here in AVSIM..what I do, is to rename the community folder before the update (even if the update does not do anything to it) launch FS so to make sure the update went fine, fly around a bit,  if all ok, then I go back and rename the folder to its original name. That is MY process,  its NOT a waste of time and it DOES accomplish something. It has worked for me, cause I haven't had one single CTD...yet!

Well that doesn't make sense at all, because if you named it back and had no CTD, that means you would have had no CTD without doing any of that in the first place, because the files are exactly the same.

But whatever.  As my old school teacher used to say - 'it's your own time you are wasting!'  

I 100% agree with everyone stating there is no need to touch the community folder when doing an update.  It is fact, not opinion, that the update process does not touch the community folder.  It certainly doesn't hurt the process to remove the contents of the community folder before doing an update, just like eating a bagel and drinking coffee does nothing to hurt the update process either.  But make no mistake about it...  It IS a complete waste of time...

Having said that, there is always a chance that one or more of your community folder mods/scenery/aircraft will be incompatible after an update.  This can cause anything from incorrect textures showing to full CTDs.  So if you do see issues like that, your only recourse is to experiment with enabling/disabling your various mods until the culprit(s) are found.  But these are all POST UPDATE tasks, so it serves no purpose to delete the community folder before an update and then restore the folder after the update...

I highly recommend the use of an add-on linker program to manage your community folder mods.  Using a linker makes enabling/disabling mods as easy as a click of the mouse button.

Edited September 8, 20214 yr by PlumCrazy