Thank you very much!  🙂

Hide option is already put to use, very handy indeed! I am also using colored tags to mark 2024 compatible add-ons.

A quick update from me, in the unlikely event that anyone is interested!

Having both the luxury of space and a very large (2.5 TB) addons environment, I have decided to "clone" my addons environment and have completely separate setups for 2020 and 2024. So I took a backup of everything just prior to installing 2024, and that will be my 2020 system, but I will do no further updates to the addons in that folder structure.

The original folder structure now becomes the exclusive property of 2024, and that's where I will add any further addons, and also where I will appy any updates to existing addons. I can then take my time going through that environment deleting any now unnecessary features (stuff like "I love VFR" etc) or anything I now find doesn't work in 2024.

And of course, both environments managed by the Linker, as before. Two separate shortcuts, one for the 2020 exe and one for the 2024 exe, each pointing to the appropriate environment.

Of course, easier to describe here than it has been (is still) to do, what with all my internal symlinks etc, but once it's finished I'll have two firewalled systems with no danger of either corrupting the other. And if I end up deciding to drop 2020 altogether, I'll just go back to using that drive for a backup of the 2024 system.

9 hours ago, andy1252 said:

And of course, both environments managed by the Linker, as before. Two separate shortcuts, one for the 2020 exe and one for the 2024 exe, each pointing to the appropriate environment.

More or less what I'm doing too. I'm copying then moving my addons one by one (or in small batches) to a location that's 100% MSFS 2024 compatible. AL makes it easy to keep track of what's where.

I have three tags set up for this purpose: "2024 Yes", "2024 No" and "2024 Partial" - each coloured accordingly. I also make use of the Description field to make a note of any incompatibility problems.

When pressing the F8 on any addon I try, it will always show that it doesn't belong to any preset even though it does (MSFS_AddonsLinker_2024.exe) .

I tried many addons that are in one or more preset(s).
If i select / apply the preset it does populate my community folder with the Symbolic links, but on the preset assignment (F8) it doesn't reflect that those are part of any preset(s). Also CTRL+M (preset manager), I do see all my addons in the correct presets, so they are for sure in those presets.

 

 

 

Edited December 6, 20241 yr by Akila

@Akila .. sounds like a bug somewhere, sorry for that 😱

Would you mind sending me via private message the content of one of your preset file (they are here C:\ProgramData\MSFS Addons Linker 2024\Presets and are simple text files, you can open with notepad and copy/paste)

And then also a screenshot showing me on which addon you click F8 which is on the preset file but doesn't show checked on the new screen (or use the right click option menu, i guess you get the same result, try that if you haven't please)

Hopefully i'll understand what is happening because 'unfortunately' on my end i can't replicate

Thank you 🍻

Edited December 6, 20241 yr by Bad_T

Hi @Bad_T , I am sending you all the AddonLinker data (ProgramData/Presets - Total size: 800k), that way I assume you can reproduce the error.

https://www.mediafire.com/folder/p2tzv7vbwhhb2/AddonLinker

BTW - pressing F8 or via the menu has no difference.

NOTE: it might be related. the presets & Addons_SymbolicLinks.bin, were all migrated from 2020. it might be related to the issue.

 

Edited December 6, 20241 yr by Akila

@Akila Thank you 🍻, i got the file if you want to remove them, investigating ....🤞

Edited December 6, 20241 yr by Bad_T

@Akila I found the issue thanks to your files, it has to do with uppercase/lowercase ... your folder is B737-800 and in the preset it's saved b737-800 and the code should check in a 'case insensitive' way but it doesn't 😔

i will publish a hotfix (it's rare i can get it right the first time 😱 😁 😁)

Also, not sure if you are already aware of it, but if you have some addons that you want to have almost always activated, you don't need to put them in every presets, just use the 'Persistent' option and they will not get disabled unless you disable them manually. There are also some button on the toolbar to enable all persistent addons, or disable everything except the persistent ones.

Thanks for reporting 🍻

 

 

Edited December 6, 20241 yr by Bad_T

Nice one. for me all my folders are mixed case (uppercase and lower case).
I believe many people use mixed case in the folder structure  / names (my assumption).

Example:

 

Another Example:

 

 

 

Edited December 6, 20241 yr by Akila

yup, you're right, it's normal to have a mix of uppercase/lowercase, but i did my tests on fake 'addons / folders / presets' to create multiple scenarios and i had them all lowercase (which obviously doesn't match the reality 😱) so i didn't notice .. oh well 😋

hotfix has been uploaded on FS.to .. hopefully it will be ok now 🤞

Thanks again 🍻

Edited December 6, 20241 yr by Bad_T

Yes, it is fixed. thanks!!!!

Again, just in case anybody else can get anything out of this.

I've now finished setting up my 2020 and 2024 configuration. This should give me two completely separate installations now, and my current thinking is that I won't buy any more addons for 2020 and just consider that system frozen. Of course, I may yet succumb if anything really enticing comes along, but hopefully we'll start to see genuine 2024 addons showing up now.

Here's what I ended up with. Again, not suggesting this is "how to do it", but it is "how I've done it"

I also am an avid user of Addons Linker.  Have not found the need to maintain separate libraries.  I have over 300 addon airports, the vast majority freeware.  Separate libraries would just require too much space.

Thanks for the new Addons Linker support for the dual sims, I am using one common well-organized set of folders shared by both 2020 and 2024. To date I have discovered only one addon airport that is not at all yet compatible with 2024, and the 2024 default for that airport is not bad.  All of the other addon airports I have visited so far work quite well.  The most common issue I see are a mere sprinkling of static aircraft that are pink.  i.e. Missing textures. 

Most of the addon aircraft I use are 3rd party-developed.  The most common issue there is that I am a TDS GTN user and the TDS GTNs are not yet compatible.  My best working 2020 addon aircraft is the FlightFX Hjet, which I fly often.  It works well but suffers from some MS2024 simulator bugs with interior and exterior lights.  It also suffers from the GMT vs local time bug causing disparity between time-sensed cockpit lighting vs environment lighting. 

As I go forward, my method for discerning which of my common library addons are 2024 compatible is this. 

I append each addon's root folder name.  If I find the addon is totally 2024 compatible I append the folder's name with a space and then a +4.  If I find the addon is not 2024 compatible I append the folder name with a -4.  If I find the addon is 2024 compatible enough to use I append the folder name with a 4-.   An addon for KESN Easton MD is the only addon so far that is not working at all.

I am doing this as I go, flight to flight, destination to destination.  Here are examples:

KDAL Dallas Love Field TX (iBY) 4-

KBMG Monroe County Bloomington IN 4-

KESN Easton-Neunam Field Easton MD -4

KTYQ Indianapolis Exec IN (UK2000)  4-

------
Hjet Hondajet Flight FX v2_1_2  4-

------

Shift-Z _FPS display mod +4 

If you open the spoiler window below you can see my folder organization with an expanded look at scenery addon organization.
 

Spoiler

 

 

 

 

39 minutes ago, fppilot said:

If I find the addon is totally 2024 compatible I append the folder's name with a space and then a +4.  If I find the addon is not 2024 compatible I append the folder name with a -4.  If I find the addon is 2024 compatible enough to use I append the folder name with a 4-. 

Hello, if you don't want to go through the hassle of having to rename folders, are you aware of those features :

- with the latest version you can hide incompatible addons so that they don't bother you anymore (see my last post of page 5 if you need more info about this)

- AL has a 'TAG feature', you can define tags in the options screen (for example 'compatible', 'partially compatible', 'incompatible' each with a different color) and you can then easily add tags to each addons via the right click menu and the tags will show up in the main view for quick identification.

Maybe you are aware of that already, but just posting this in case you don't because i think it might be a bit easier that way than having to rename the folder on the disk (just a matter of personal preference i guess).

🍻

Edited December 10, 20241 yr by Bad_T

1 hour ago, Bad_T said:

Hello, if you don't want to go through the hassle of having to rename folders, are you aware of those features :

- with the latest version you can hide incompatible addons so that they don't bother you anymore (see my last post of page 5 if you need more info about this)

- AL has a 'TAG feature', you can define tags in the options screen (for example 'compatible', 'partially compatible', 'incompatible' each with a different color) and you can then easily add tags to each addons via the right click menu and the tags will show up in the main view for quick identification.

Maybe you are aware of that already, but just posting this in case you don't because i think it might be a bit easier that way than having to rename the folder on the disk (just a matter of personal preference i guess).

🍻

Did not know about the tag feature or the hide feature.  Will definitely check them out.  I assume both are 2020/2024 app-app specific?  t.e. hide in one but not in the other.