From the Working Title Discord

Quote

There have been a lot of questions and concerns about the Working Title community packages since WU4 dropped, so here's a quick status update:

The G1000 has been updated and released - you can grab the latest on our packages website here: 

https://packages.workingtitle.aero/g1000/2021/04/14/g1000-release-v0.3.5.html

Quote

Due to changes in how planes load their configurations in WU4, we had to change the code that loads custom display gauges from WTEngineDisplay.xml, as is done with our sample for the G36. In order to get these to work now, aircraft creators or modders must put the contents of the WTEngineDisplay section directly into panel.xml, within the body of the main PlaneHTMLConfig section. This is unfortunate, but it was the only way we could preserve this functionality. Doing this to your panel.xml is fully backwards compatible and will not break planes that don’t use the modded G1000. Aircraft modders that are using this capability to customize the engine gauges should reach out to @kaosfere#2833 or another member of our team for more details - best to find us on our Discord server.

Re: The G3000

Quote

We are not aware of any update-related bugs on the G3000, but if you do encounter an update-related problem, or really any bug with it, please log the issue here

https://github.com/Working-Title-MSFS-Mods/fspackages/issues

Re: The G3X

Quote

We have an open bug that pre-dated WU4 where some users experience a problem with SVT; we have (finally) been able to reproduce this problem on one machine, but not the others, and we are actively trying to figure out what's going on here. We hope to have an update that resolves this in the next few days now that we've been able to reproduce it - the bug is not a breaking bug, the G3X can be used without SV with no problem as far as we are aware.

@everyone The CJ4 has been updated and released - you can grab the latest on our packages website here:

https://packages.workingtitle.aero/cj4/2021/04/14/cj4-release-v0.12.1.html

Quote

It's worth noting that the CJ4 was not broken with WU4, we just happen to have a bug fix update ready for release that was in QA this week already. It is purely a coincidence that it is being released at the same time as the G1000 fix.

Re: Updates, QA and our Community/Freeware Packages

Quote

 

Generally, we want to remind everyone what we said after the announcement in March regarding our work with Microsoft. We will make a best effort to keep the community packages updated and functioning, and even continue making enhancements, until these packages are replaced by base sim projects that we've already begun working on. This stuff takes time, but I'm quite confident that many of you will be pleased with product of the work we have planned and have already begun. With respect to the existing packages, since the announcement, we have released major updates to both the G3000 and the CJ4, including a new custom vertical autopilot for the CJ4, and we've shown off the WIP TCAS and Charts for the G3000 in our Discord #progress channel. While I regret even having to say this, any speculation or commentary suggesting that our community packages are no longer important to us or to Microsoft are simply false.

Specifically with respect to the WU4 release causing breakage in the G1000, we definitely regret that this happened. While we continue to emphasize that we make no guarantee that future updates won't cause breakage that requires a fix from us, we are actively working with our partners at Asobo and Microsoft to better prepare for future releases, until such time as our packages are deprecated and replaced. As those that have been with us from the beginning know, we have always been extremely attentive to sim updates and often release fixes within hours. In this case, it took us just about 20 hours to get our fix into QA, and a few more to publish the fix on our website and Discord server - not our fastest, but also not our slowest.

As always, we are humbled by the support many of you have shown us and we appreciate all the feedback - as we said in our partner video, this entire project is a direct result of community feedback and that feedback continues to directly influence our future projects.

 

 

Thanks for sharing this with folks.  🙂     @cwburnett posted the same a little while ago, though:

I'd suggest folks with questions or comments reply there so we don't have the same discussion spread across two threads.  😄