Update 11 JAN 2017 @ 20:30z:
We’ve been following the forums and Andrew from FSLabs has clarified some important information.
We have every intention to release the A320 for P3D.
We are not going to wait months for LM to produce another hotfix.
We are working around the clock on this – if LM can help, that’s great. If not – we’ll be taking additional steps with the A320-X to mitigate (as much as we can) the memory problems introduced in P3D v3.4.
So there we go, the team aren’t resting until LM fix the issues, but are continuing to work regardless of the outcome.
Lefteris from FSLabs has taken to the FSLabs forums to update the world with what’s going on with the team for this year. Not only the long-awaited Prepar3d version of the A320X, but also snippets of the future.
He began detailing what will come in 2017 for Simmers. He confirmed that the next update for the A320X will be with us very soon. This will fix several bugs (e.g. MCDU freezes and autoland flare logic) as well as other improvements. Of course, once we get closer to a release, we can expect a full list of details. Whilst this update won’t bring in features like detailed winds, we can expect that in a service pack later this year. The team have broken the service pack down into smaller tasks to push updates faster, as well as add any improvements and user feedback along the way.
Now, like me, you really just want to know when the Prepar3d version of the ‘bus is coming out! Lefteris has said that there are no ‘major bugs’ with the version the team have, but as awaiting some more fixes from Lockheed Martin with their most recent version of Prepar3d. Some users have reported VAS issues and an error message called “DXGI_DEVICE“. I’ve personally not experienced either, so can’t comment, but the logic is, FSLabs don’t want common users to associated the issues with their product and build up a huge list of support issues not meant for them. I can understand the frustration of users especially after hearing there’s no bugs, but completely understand their position. With development fast and active, hopefully it won’t be long until LM solve the issue.
Further information was also given about the ‘cockpit builder’ features. Basically, lots of vendors want to work with FSLabs (and vice versa) to bring the best hardware to the community to work with the A320X. FSLabs are asking you to contact your favourite vendor to contact them to begin the discussions!
Finally, the forums have had a spring clean to make things easier to find and more helpful. The team are also looking at different ways to use support facilities to help people who have purchased the product!
Other than that, that’s about it. We’re excited and eager to get our hands on the plane. Come on Lockheed, chop chop!
Don’t forget to vote in our FSElite 2016 User Awards for FSLabs A320X to be your aircraft of the year, and FSLabs to be your Aircraft Developer of the year.
You could even possibly win a prize just for voting!