Some updates after the Connexion London 2017 convention
London 2017 slides
Further testing and road to public beta:
- After testing and fixing issues in the distributed swift system we will gradually move on with flight tests, i.e. testing connected with the various simulators.
- We will first test with few alpha users, as we did for model mappings. Registered alpha users will be asked to join the tests when they start.
- Most likely we will do it one simulator at a time.
- Once those tests are passed, we prepare for a public beta. But the tasks will take some time.
swift and P3Dv4
- We will develop a genuine 64bit P3Dv4 driver
- so we can support new P3Dv4 API features
- and compile a 64bit swift version for P3D
- We need to update our model data to distinguish between new P3Dv4 models and old legacy P3D/FSX models
- You can still join alpha program and participate at any time you like
- If you have registered and not received a confirmation yet, please let us know.
- You need access here to download the alpha software:
- And here to communicate (with us), file error reports etc.
- Creating mappings is still much appreciated. The more aircraft data we have, the better testing will work and the better the pilot client will work.
- Currently we are looking for support mapping new P3Dv4 models, whoever wants to help is welcome.
- Clarification: Many people expect, after registration for alpha, to receive detailed work tasks. This is not how we work. We let you know the overall test scenario (e.g. model mapping). You need to start on your own and we support you when problems arise.
Still we are looking for someone who will manage and coordinate the model mapping. This does not require any programming, but organizational / management skills. We would like to focus on the programming, less on the content side.
Thanks for the feedback guys. Some clarifications and adjustments:
- We have already received more requests for alpha testing than we can currently handle. So we have restricted access for the moment. This is nothing personal, please do not be disappointed. Our first tests are about testing controlled scenarios, not just playing around. We need a small group for that, as we need to give support and guidance.
- So when you are interested in joining alpha testing send us an email to alpha () swift-project.org . Include your simulator and OS (Windows, Linux, …). We will keep a list of potential testers and contact you when it fits (Hollywood principle).
- We will gradually increase the number of users involved. We let you know when this is the case.
- We are still looking for people joining the team as programmer or designer, feel free to contact us.
- This is an early stage of testing. public beta test will follow, but not too soon. We can not tell you a date/time.
Thanks for your understanding.
We have reached our swift version 0.8 milestone. This means that all major components of the swift application ecosystem now basically resemble what we think will be needed for the first release version. But we still have a lot of testing ahead before that can happen. We still can not predict when that first release will be.
The pilot client is not quite ready for public use. But what we would like to do now is invite some people to start trying out our model mapping tool, which was discussed in a previous blog post. This will enable us to learn what we have done well and what we have done poorly, and go about improving some of those poorer aspects and fixing the bugs that people discover. And by providing real data, the testers won’t just be testing, but also improving the model matching of the release version.
We call this phase of testing our “alpha program”. We will be reaching out to potential testers in the next few days and weeks. Please don’t take this post as an invitation to put yourself forward to be a tester. We will have enough names drawn from local regional groups, as too many would overload us. Remember that you won’t be able to fly online with the alpha version. A public beta will come later, when the most egregious bugs have been dealt with.
We have set up our new developer portal where our development will be conducted from now on. This is where our testers will be reporting bugs and missing features. It is also the current home of our user documentation.
We know you have been desperate for news, so here are some of the other things that have been keeping us quiet since our last update:
- Performance optimisation;
- Weather (if enabled, swift uses a smart algorithm mixing VATSIM METAR data with NOAA cloud, precip, and winds aloft data);
- Interim position packets and interpolation (smoothing out aircraft motion);
- Crash reporting tool (if swift crashes, it can “phone home” with the technical details of the crash to help us fix the bug);
- Lots of “behind the scenes” stuff that enables everything to work together.
Model matching is a key feature for swift. It is required because every pilot can have different aircraft models installed, and the naming of aircraft models is not standardized among the different simulators (FSX, XPlane, …). So when pilot Bob flies a FSX B737/DLH we need to find the most suitable aircraft model (representing Bob’s plane) in Alice’s XPlane simulator (this finding process is called “model matching”). Continue reading sneak preview mapping editor