FSDreamTeam forum
November 26, 2020, 01:00:28 AM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News:
 
   Home   Help Login Register  
Pages: [1]
  Print  
Author Topic: Activate and Deactivate Scernery-Link to Community-Folder MSFS  (Read 91 times)
Dashjockey
Newbie
*
Posts: 1


« on: November 21, 2020, 05:51:03 PM »

Dear FSDreamTeam,

I have just bought the Zürich Scenery for MSFS and I am very happy about it, beautiful Scenery!

Would it be possible to design the existing link of the scenery to the MSFS community folder so that the user can activate and deactivate it? Could something like that be integrated into the addon manager? That would be a really helpful feature.

Many users want to keep the community folder as small as possible and empty it completely when updating MSFS.

It would be great if this could be made possible at some point.

Thanks in advance and best regards from Hamburg!
Christoph

Logged
virtuali
Administrator
Hero Member
*****
Posts: 40072



WWW
« Reply #1 on: November 23, 2020, 02:06:55 PM »

Would it be possible to design the existing link of the scenery to the MSFS community folder so that the user can activate and deactivate it? Could something like that be integrated into the addon manager? That would be a really helpful feature.

Many users want to keep the community folder as small as possible and empty it completely when updating MSFS.

We use a link for the precise reason of keeping the community folder as small as possible and empty it completely when updating MSFS, because the link means we don't have any files there so, disabling it would be completely useless, the MSFS update process is surely not affected by a link, just because "it's there".

In general, is not even needed to remove any add-on in the Community folder that is NOT replacing any default files, which is surely the case for sceneries. You might have read somewhere that, in order to have a smooth update, it might be best to clean the Community folder but, people say that for simplicity, when in fact they should say:

"If one of your add-ons in the Community folder has ( VIRTUALLY ) replaced a stock file, it might be a good idea to remove it, and check with the developer if they have an updated version of that file that would work with the new update"

Of course, that's more complex to explain than simply saying "wipe out the Community folder before updates", which is overkill but, if you don't what to explain the whole story ( which would require explaining what "VIRTUALLY replacing" really means ), it's easy to just say that.

So, while I understand that, with some add-ons ( for example the A320 mod ) that "virtually" replace stock files, it's best to check if there's an update that supports the MSFS update before using them, is surely not the case of our add-ons and, if we'll ever release an add-on that would do that, we'd clearly alert users about the issue when a simulator update is coming.

So, for the time being, you can be assured is not required to remove any of our add-ons before an update of the simulator, so that option is currently not needed.
Logged

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!