Guys,
Is there any hard advice on what, if anything, we should do with the contents of the community folder (add ons) prior to doing an update? Is this content overwritten/corrupted or is it safe to leave there?
During the last update my community folder was empty but now I have add-ons in it. Just thinking ahead…
1 Like
I’d imagine it’d be fine but just, back it up in case if your worried.
1 Like
Community files are un-effected, left them in there during the last update and had no issue’s.
1 Like
I wondering the same thing, corruption off game files. I about 2 do a clean install.
Hi,
it depends on developers of these community add-ons. They should develop their add-ons considering the codebase on which they build could somehow change in the future.
In other words, if they, let’s say, hardcode things and copy-paste part’s of Asobo’s code to their work, it’s rather dangerous way ho to do it.
For example, people behind my current favourite project flybywiresim/A32NX are aware of this and don’t release code updates (git commits) that don’t respect these principles of coding.
In the other hand it also depends on how Asobo will change their code base / interfaces / SDK in the future and how it affect thigs that are already built on that. Basically they could but they shouldn’t do this to much. There are ways how to keep thigs backward compatible and ho to give developers some time to adapt to new release and properly documented approaches.
EDIT: And yes, as @DORRAGER already mentioned above, community folder shouldn’t be affected by Asobo’s updates of their codebase. In case of any incompatibilities, community devs will provide updates of their add-ons.
1 Like
My community folder has been affected if I leave all my addons in the community folder … the Ms 2020 software no longer works as it should … if I remove all my addons in the community folder everything starts working normally again . Do you have a solution?
Are you shure ?? community folder make CTD immédiatly.. Please.. do somethings
Chances are high you have mods in your community folder that conflict with changes the update made then. For me the folder stayed untouched throughout the patch installation and the sim conitnues to work fine.
So empty your community folder and start looking for the conflict by installing one mod after the other while repeatedly testing at what point the sim stops working.
Mods that change systems and gauges, like “performance” or “Garmin” mods, are far more liikely to cause such problems than static scenery addons.
2 Likes
Yes, I’m 100% sure. Content of community folder is really untouched by Asobo updates. Files there are / will be exactly the same as before the update / patch.
Compatibility between community content and updated Asobo’s code base is complete different story. As I wrote before: “n case of any incompatibilities, community devs will provide updates of their add-ons.” And they should of course. In case of a32nx project they are just merging base A320 changes that was published by Asobo patch update.
See this github issue thread Porting aircraft changes from 1.8.3.0 · Issue #719 · flybywiresim/aircraft · GitHub if interested in some detail on what exactly was changed by Asobo in this particular case and what needs to be merged to a32nx code then…
In case of big changes in base code like this one (by Asobo) there is always need to revise/adapt the code that explicitly relies on the code base. That’s the risk which a32nx developers has taken in account when started with this abitious project.