February 7, 20251 yr I am slightly amazed that this topic does not get more attention. Do you all have no issues at all getting the MSFS2020 stuff into MSFS2024? Do you all simply link it via Addonslinker? I ask specifically because I want to get rid of MSFS2020 but not loose potentially compatible stuff. E.g. FlyTampa: most of it is not yet officially working in MSFS2024, yet it is shown as compatible on the FSElite list. BUT: I guess I cant simply install it into MSFS2024 (most of them on ORBX), so the only solution would be to have it installed in MSFS2020 and then link via Addonlinker, correct? Or how do you guys get MSFS2020 stuff into MSFS2024 when installed via ORBX, Contrail or any other installer that discriminates MSFS2020 and MSFS2024? I started to link stuff via Addonlinker directly out of my MSFS2020 community folder into MSFS2024 and it works, but it is a huuuuge mess and extremly "difficult" to maintain. Any better idea? Greetings, Chris AMD Ryzen 7 9800X3D, 2x32GB DDR5 6000MT/s RAM, MSI RTX 4090 Ventus 3X, Windows 11 Home, MSFS2024
February 7, 20251 yr Most scenery works, if it’s not officially compatible with 2024 (ie no direct installation to the 2024 community folder) I just copy it over from my 2020 community folder. I use addon linker for all of my 2020 freeware that I have sorted by region. Most work fine, occasionally there will be trees in weird places or some elevation issues but I’ve found those to be rare. Aircraft are a different story as 2020 aircraft working in 2024 is much more hit or miss. You’ll want to do some checking to see if they work rather than assuming that they will. Dave Current System (Running at 4k): ASUS ROG STRIX X670E-F, Ryzen 7800X3D, RTX 5090, 55" Samsung Q80T, 64GB DDR5 6000 RAM, EVGA CLC 280mm AIO Cooler, Brunner CLS-E NG Yoke, Thrustmaster Warthog HOTAS & Stick, Thrustmaster TCA Quadrant & Add-on, VirtualFly Ruddo+, TQ6+ and Yoko+, GoFlight MCP-PRO and EFIS, Skalarki FCU and MCDU
February 7, 20251 yr I don't put anything in 2024 unless it's officially supported. For example, I set the ORBX app to FS2024 and click 'My Products', then I install any products that are now compatible. Cutting and pasting stuff to see what happens doesn't appeal to me. FS2024 • PMDG 738, 77F • FSL A321 • A2A Comanche, Aerostar • BS Baron, Bonanza, Caravan Pro • JF Tomahawk • TAOG H500C BeyondATC • GSX Pro • ChasePlane & Flow Pro • TDS GTNXi • FSUIPC • AutoFPS • RealTurb 9800X3D B650E • ROG OC RTX 5090 • 64GB DDR5-6000 • VKB Gladiator, STECS, T-Rudder • Tobii 5 • ISP 1 Gbps
February 7, 20251 yr 45 minutes ago, flyingscampi said: I don't put anything in 2024 unless it's officially supported. For example, I set the ORBX app to FS2024 and click 'My Products', then I install any products that are now compatible. Cutting and pasting stuff to see what happens doesn't appeal to me. I also think this is where a lot of problems get introduced... I agree, keep 24 with "made for 24" and if it's not in 24 and you MUST have it then continue in 2020 until it's supported (cough cough 777 cough cough) Have a Wonderful Day -Paul Solk
February 7, 20251 yr If you must add potentially incompatible things to MSFS 2024 and you don't want to keep MSFS (2020), this will be useful to you: You may well be opening a can of worms though.
February 7, 20251 yr 1 hour ago, AnkH said: so the only solution would be to have it installed in MSFS2020 and then link via Addonlinker, correct? Or how do you guys get MSFS2020 stuff into MSFS2024 when installed via ORBX, Contrail or any other installer that discriminates MSFS2020 and MSFS2024? I started to link stuff via Addonlinker directly out of my MSFS2020 community folder into MSFS2024 and it works, but it is a huuuuge mess and extremly "difficult" to maintain. Any better idea? You shouldn't do that with Add-on Linker. You put your add-ons in a separate folder that is not in the MSFS 2020, or the MSFS 2024 folder branch. So make a neutral folder to put your add-ons in. Then with Add-on Linker, when you enable the add-on, it will create symbolic folder links in your MSFS 2020 and MSFS 2024 Community folders. If you are doing this right with Add-On Linker, your Community folders for both MSFS 2020 and MSFS 2024 should never physically store any add-ons. Then with Add-On Linker, you can quickly enable or disable add-ons in both MSFS 2020 or MSFS 2024. i5-12400, RTX 3060 Ti, 32 GB RAM
February 7, 20251 yr Author 54 minutes ago, abrams_tank said: You shouldn't do that with Add-on Linker. I am aware, but my setup for MSFS2020 was as such that I only used AddonsLinker for addons that did not come with a specific installer. All coming with an installer, be it directly for the addon itself or via ORBX, Contrail etc., I did not add using AddonLinker but by installing it directly. Either via another library (like for ORBX) or in very few cases, sadly directly into the community folder of MSFS2020. And now, e.g. FlyTampa Sydney, is not offered by ORBX as installable option into MSFS2024. But I can link it out of the ORBX library into the MSFS2024 community folder. This works, fine. But if I then uninstall MSFS2020 completely, I have to be careful not to remove everything from MSFS2020. E.g. I would then need to keep the ORBX library for 2020, but without MSFS2020 installed, ORBX wont show me MSFS2020 anymore as selectable option. You see my problem? Greetings, Chris AMD Ryzen 7 9800X3D, 2x32GB DDR5 6000MT/s RAM, MSI RTX 4090 Ventus 3X, Windows 11 Home, MSFS2024
February 7, 20251 yr 26 minutes ago, AnkH said: I am aware, but my setup for MSFS2020 was as such that I only used AddonsLinker for addons that did not come with a specific installer. All coming with an installer, be it directly for the addon itself or via ORBX, Contrail etc., I did not add using AddonLinker but by installing it directly. Either via another library (like for ORBX) or in very few cases, sadly directly into the community folder of MSFS2020. And now, e.g. FlyTampa Sydney, is not offered by ORBX as installable option into MSFS2024. But I can link it out of the ORBX library into the MSFS2024 community folder. This works, fine. But if I then uninstall MSFS2020 completely, I have to be careful not to remove everything from MSFS2020. E.g. I would then need to keep the ORBX library for 2020, but without MSFS2020 installed, ORBX wont show me MSFS2020 anymore as selectable option. You see my problem? I had the same problem as you with FSDG's Maldives bundle. FSDG's installer will auto detect your Community folder and install the Maldives bundle folders into your Community folder. I cannot redirect the installation of the Maldives bundle folder to anywhere else, it has to be the Community folder. So after FSDG installed the Maldives bundle to my Community folder, I just moved the Maldives bundle from my Community folder to the neutral folder I told you about. Then I used Add-On Linker as usual, and enabled the new Maldives bundle in Add-On Linker. It worked like normal. FYI, I also use Contrail. If Contrail installs any add-ons to my Community folder, I also move those add-ons outside to the neutral folder. Nothing is stopping you from moving the add-ons installed into your Community folder to a neutral folder that Add-On Linker can point to. Even better, you can tell Contrail, OrbX, etc, to install add-ons to your neutral folder. Edited February 7, 20251 yr by abrams_tank i5-12400, RTX 3060 Ti, 32 GB RAM
February 7, 20251 yr Author And with this approach, will FSDT Maldives be updated? You can then simply run the updater or will it mess up totally? ORBX: I consequently used the library instead of installing directly into the community folder, but the ORBX installer has a pulldown menue where you can select MSFS2020 or MSFS2024. If I now uninstall MSFS2020, I guess it wont show up there anymore and consequently all sceneries installed for 2020 are without maintenance, e.g. an update will then end up in nirvana, as ORBX thinks I do not have those installed anymore. Or does ORBX not care about whether or not MSFS is acutally installed and simply controls the GUI via this switch? I do not know... Greetings, Chris AMD Ryzen 7 9800X3D, 2x32GB DDR5 6000MT/s RAM, MSI RTX 4090 Ventus 3X, Windows 11 Home, MSFS2024
February 7, 20251 yr 1 minute ago, AnkH said: And with this approach, will FSDT Maldives be updated? You can then simply run the updater or will it mess up totally? ORBX: I consequently used the library instead of installing directly into the community folder, but the ORBX installer has a pulldown menue where you can select MSFS2020 or MSFS2024. If I now uninstall MSFS2020, I guess it wont show up there anymore and consequently all sceneries installed for 2020 are without maintenance, e.g. an update will then end up in nirvana, as ORBX thinks I do not have those installed anymore. Or does ORBX not care about whether or not MSFS is acutally installed and simply controls the GUI via this switch? I do not know... I don't have the OrbX installer yet. I use Contrail though. I guess Contrail just installs to my Community folder? I then move whatever it installed to my Community folder to my neutral folder. It's not a big deal with Contrail. And if Contrail is unable to detect if I have the latest version, that's not a big deal to me either. I just make Contrail forcefully download whatever scenery I want, if I want the latest version. i5-12400, RTX 3060 Ti, 32 GB RAM
February 7, 20251 yr I'll echo the "only if it is 2024 compatible" statement. I don't load any addon that isn't showing as compatible and/or has been mentioned by the vendor. For example, if the Orbx store isn't showing it for 2024, I'm waiting. What we were told before launch was that "most" addons from 2020 should port over to 2024, but in reality that's not the case. I'm one of those people who have not had major issues with 2024, not sure it is because I am so careful with my addons or not, but that's my guess. I know early on when everything from the MS marketplace was loading in the sim (before they fixed it), my 2024 was a mess. Once they stopped doing that, my problems went away. I uninstalled 2020, so I can't comment on how to run both, but I'd recommend keeping 2024 as "vanilla" as possible until things settle down. ------------------------- Craig from KBUF
February 7, 20251 yr Most scenery seems compatible, though the mesh in 24 is different so you may find terraforming issues and a few pink textures. Some planes are and others not. Blacksquare planes do not work in 24. FSLTL now works, though again, some of the textures are pink, so I guess they will update them over time. I have hundreds of addons and most work fine, though a few have minor issues. Ryzen 5800X3D, Nvidia RTX5080 - 32 Gig DDR4 RAM, 1TB & 2 TB NVME drives - Windows 11 64 bit MSFS 2024 Premium Deluxe Edition Resolution 2560 x 1440 (32 inch curved monitor)
February 7, 20251 yr I'm guessing that PMDG and others are working out how they can charge us for making their planes compatible with 2024 by making out that it's so, so, so hard to do.
February 7, 20251 yr 28 minutes ago, jarmstro said: I'm guessing that PMDG and others are working out how they can charge us for making their planes compatible with 2024 by making out that it's so, so, so hard to do. PMDG have already said they won't charge for 777 and 777F 2024 upgrades. They haven't decided on what they're doing with the 737 yet. Edited February 7, 20251 yr by Tuskin38
February 7, 20251 yr 16 minutes ago, jarmstro said: I'm guessing that PMDG and others are working out how they can charge us for making their planes compatible with 2024 by making out that it's so, so, so hard to do. So far, I have not been made aware of any developer, aircraft or scenery, who is charging anything for an update to MSFS 2024 from MSFS. I am sure that you will have a list. I am so pleased that I don't live in such a dark and bitter world. Edited February 7, 20251 yr by Reader
Create an account or sign in to comment