As I understand it Working title have Updated the 530/430 in the base sim. I keep hearing about Market Place versions (the ones with the units as thumbnails)
I have these also, but I keep reading on different forums that they should be removed because XYZ Plane does not work because of them or some other issue.
What is the deal with these, and do i really need/not need them? It is all very confusing?
You are right they have not done a great job at explaining this to the average user and in particular it is a poor way to roll it out. Just better naming of the packages as they appear in the content manager would of helped whatever written instructions they put out.
Anyhow here is my best attempt at explaining what they all are.
All the content that you see in the content manager when you search on working title that has the grey background with the MSFS logo on are the new Working Title packages. All of these fall into that category.
G1000Nxi, G3000, GNS430/530 and WT21.
The other 2 items you may have are the additional what I call the linker or redirector packages for the G1000Nxi and the GNS 430/530. These are the ones with the actual pictures of the product. These are only required if you have a third party aircraft that is yet to be updated to call up the new package. So for instance if the aircraft uses a GNS and it hasn’t been updated to point to the new GNS package then it will point to the old version. All these linker files do is redirect that link so the addon aircraft uses the new package. If and when every aircraft is updated to point to the new package then these files are no longer required.
If you have anything else in the content manager that says ‘community’ in the last column on the right rather than ‘up to date’ then this resides in your community folder and should be removed because it could interfere with the operation of these new builds.
It’s a little long winded but as already discussed it’s not the smoothest way to implement this and have everyone understand it. I hope that helps in some way.
Thank you very much for the helpful and easy to understand response. It makes total sense to me now.
Is there a way of knowing which planes use this? I have nearly all the Good payware GA. Is it a case of, I remove them and see what planes no longer work?
I guess you could do that but they are not doing any harm even if they have all changed. Again this is another thing that could of been researched before the release and a list published with the release so we all knew the situation for each aircraft. I wonder if they have a plan to remove the linker files at some point. If they do it would be nice to have some official communication on the matter.
Even if all planes that need the the linker packages get updated, you might as well keep them. Some freeware maker may come up and say “Hey, I’ve had this for a year and ever did anything with it, so I’m releasing it as-is.” That plane may still be coded for the older files. The two packages together are only 53.1 Kb, so with the size of todays storage drives, deleting them would be like Chewbacca pulling out one hair. When such small files can provide so much potential benefit, there’s no sense getting rid of them.
I think a lot of the confusion is because multiple 3rd party devs have said to remove those due to conflicts with their products.
Who exactly are these devs and what aircraft. Unfortunately if it’s true that they interfere then one can’t remove them if they are needed for another aircraft. It’s another conflict situation created by a sim update if that is indeed the case.
If a 3rd party dev tells you to remove something from the Official folder, then that dev needs to do some updates.
I think the third parties have said to remove the mod versions in the community folder - e.g. the WT G3000 mod from github etc - these should definitely all be removed.
They were specific to the WT 550 in the marketplace. I think everyone is getting updates out to resolve it now.
As already said here. If a dev is asking for official content to be removed to make their content work properly then that’s not right. That said the way sim updates just continue to disregard what’s already out there with no plan on being compatible with existing content is really poor. It’s no wonder the devs are getting fed up with this. The good ones must spend a lot of time having to continually update established products, if there is such a thing in MSFS.