I can see both sides here.
Everyone raves on about what great work WT have done but they have also poorly implemented some of these changes. It should have been a lot smoother from a user perspective but they just did the changes and dumped the issue on the aircraft devs. Not really fair.
That said the aircraft devs owe it to their users and themselves to keep up with what the sim is doing. Yes it’s nothing they did that caused this but it’s their product that is affected so I guess it’s their issue to resolve whatever form that may take.
For specifically the issue being discussed here it seems you need to have both WT packages installed. The main GNS and the linker for non updated aircraft.
3 Likes
I’ve left that other software in place as it doesn’t seem to harm planes that natively support the WT GPS.
1 Like
Right, but it does harm planes that don’t (which isn’t a ton at this point), like the SWS RV’s, and apparently this one?
There’s really no point to it, as most of the major products have been updated to use the new default WT530 directly.
I may have misunderstood in that case. The package I refer to is the one that allows the use of WT GPS on planes that don’t natively support it. Without it you have the old Asobo code, with it the new WT code. Natively support planes don’t need it at all, but I’ve not had any problems with them while having that code installed.
I’ve had some weird behaviour when loading flight planes from the map screen but I think that was to do with plans with lots of waypoints with long names. Replacing those with WP1…2 etc. fixed those.
1 Like
It’s hit or miss. Usually what’s broken by the “Marketplace 530” is communication between the 530/430 and other instruments, and the functionality of the Autopilot.
I have kept the PMS50 530/430 installed for those planes, even though it’s no longer supported.
Which, I should have said as well, you can’t have the Marketplace 530 and the PMS50-530 installed at the same time. This might be @SuperSixBravo 's issue? (It’s been quite some time since this issue has popped up and I forgot about that. Funny today there’s a few threads on it)
Be that as it may, most of the planes I fly now have been updated to use the WT530 natively, so it’s a non-issue for those planes.
I definitely don’t have the PMS530 installed now, and haven’t for months.
I’ll install the new Islander update this evening, and see what the GPS looks like. If the addon works it may show the WT 530 instead of the Asobo default one.
1 Like
No PMS 530 Installed, in fact despite owning the PMS 750 I dont have that installed, I only have the TDS 750 installed, and that should not be an issue, and with all due respect the dev of the BN2 would do well to support that as well, or maybe someone has already done it as a mod.
1 Like
I just pulled this from the WT Discord, with regard to implementing the 530W/430W:
These units rely a bit more heavily on compatibility with third party aircraft, due to the necessity for wiring to custom aircraft CDIs and autopilots, so your third party aircraft of choice may not work right away out of the box. Don’t fear, we’ll be working with third party developers over the course of this early access period to ensure that they are working with best practices within their code to make things work properly.
This tells me one of 2 things. Either the message never reached the telegraph pole, or it was ignored! This is form the AAU1 Update I assume?
1 Like
Which update? Was there an updte?
1 Like
It may have been from the initial release of the Beta 530 back in November I think it was…
The “working with developers” is a two way street, both have to be in communication. The developer has to decide they want to put in the effort, which isn’t necessarily simple. And, as I noted above, the whole thing is a work in progress happening over the course of this whole year. There are nav database changes being made (which are necessary before upgrades to the ATC can happen), so there’s a pretty big master plan behind this that we’re not totally privy too (given, as with any development project, stuff changes). Hence, some developers are waiting it out before they put in the effort as they have other projects they’re working on… (Like a Shorts 360 for instance, that really simple project 
).
That’s what I read elsewhere, but perhaps not in that case. 2.1.2 is current, but I have no clue what I have installed currently.
That’s fine, all I was asking for was help, can we agree I did not blame the plane? A simple, we are waiting to make sure the AAU are all done first would be acceptable as opposed to all the defensive responses? or if you have this 530 version installed it has to removed for this plane to work? I think that’s fine I would of been happy with that myself.
As has been said, other dev’s have done this, and made clear their intentions or fixes, why does this have to be so painful.
1 Like
I have
BlackBox_Britten_Norman_BN2_Islander_2020_Setup[v2.1.2].exe as of right now that is the latest I can download.
2 Likes
When I get home I’ll see what I have. I haven’t flown it in ages, so now is as good a time as any.
I don’t even remember if it has any of the ground handling enhancements in it, so may have a play with that as well.
1 Like
The Azurpoly C-160 Transall has a smiliar problem when the Working Title 430/530 from the market place is installed (it’s the one in the content manager with the screenshot thumbnail)
The Garmin unit was stuck in GPS mode, couldn’t be switched to VLOC mode and wouldn’t follow the GPS course with the autopilot. Once I uninstalled the WT 430/530 everything worked properly (although with an old version of the GPS, without startup, pressing OK and all that).
2 Likes
The GNS 430/530 haven’t been WIP in months, they’re fully implemented and documented.
WT documented the changes fully, and implemented several updates based on feedback and work with aircraft developers. They did not “dump” the issue anywhere.
This doesn’t make any sense if developers have been following the releases. There have been very few breaking changes (if any) in sim releases after the initial release of each avionics package, and those come only in sim updates where there is a lengthy beta period to address and test changes (lengthened specifically at the request of addon developers by the way). WT has also specifically said there are no major changes planned to the existing avionics they built so I’m not sure what more anyone would be waiting for.
2 Likes
You’re not thinking big enough. The 430 and 530 are only a small part of the system. There are other issues, and as you can see from the constant updates on the framework, the navigation data/autopilot systems/GNS units system is absolutely still a work in progress. Why would they be releasing AAU2 then? Why isn’t the G3X finished then if they’re all done? Why is there more work on the horizon to be done after AAU2? Because it’s not done yet. Important work takes time.
Have you developed a plane and integrated a GNS / autopilot system yet? (rhetorical question)
Personally, I’m giving developers the benefit of the doubt that if it were simple, it would be done. I also understand they have other projects in development so they can put food on the table. In the case of the BN2, he’s already shown he’ll fix things in time when he’s ready.
And no, at no time were users fully informed the consequences of changes and how it could affect 3rd party developers in a clear and concise format for each plane, what would be broken and how to fix it. At least I haven’t seen it. Then again, I don’t use Discord. But Discord is not an acceptable communication tool in regard to explaining to users exactly how the situation should have been handled. Sure, for those who know what they’re doing, it’s great. But that population is extremely small. Where do you even go to get an invite to the Discord? I’m sure if I searched I can find it, but, what you’re suggesting is that there was a public announcement explaining to users exactly what to do. There was not. Because it was an impossible task really as products from multiple vendors were involved in the shake up, and no one person can know it all in regard to everything. The people who did, PMS50 and WT mostly, where is the information regarding the the 530/430 units? PMS50 said specifically what needed to be installed for the GNS750 and worked hard out of the gate for compatibility, but didn’t really discuss the 530 situation and what to do, because he knew the writing was on the wall and so wasn’t putting any more effort into a free product. Why should he? So users have been left to fend for themselves to figure out what’s best to do.
There is no post on here explaining it all, you have to glean information from various developer and product threads.
3 Likes
