On the edge of the dense fog enveloping the approach, the landing lights create a mysterious and captivating atmosphere.
Airbus aircraft are known for their automated systems. We are currently working our way through the electrical system to make sure it works properly in all situations.
Fixing one line of code significantly improved the performance when importing external flight plans.
We are currently configuring the startup situation of the flight deck. Can you spot the "errors"?
… and another milestone ticked off: Engine performance tuning and tweaking is now done!
Our testers can finally get back on track. We are aware that it is sometimes very frustrating for testers when things don't work properly and you can't complete the flight successfully as a result. However, this phase seems to have finally been overcome. Fortunately, we have many testers who fly to different airports all over the world with all sorts of arrivals and approaches. This shows how good our custom flight management system really is and where things still need improving. The most common error is the handling of the different waypoint types. We will now gradually eliminate these, which can be quite a time-consuming task. Fortunately, it's not a question of whether, but only how quickly we can get it done.
We are also continuing to work diligently on the vertical autopilot modes and on the documentation, which will come in both text and video form. It's quite an extensive undertaking, but we're already pretty far along and are continuously adapting the documentation to our development progress.
The end-of-the-year sprint is underway and we will try to make as much progress as possible before the Christmas break – and we're already looking forward to next year!
We have worked our way through several valleys in the code and got rid of many loose ends from the P3D. As is so often the case, most of the problems are relatively easy to solve, but there are those 2-3 things that are supposed to be small problems, but in reality turn out to be bigger and more extensive. This is particularly true for the Airbus, where the systems are very closely interlinked.
An important milestone was setting the performance of the engines correctly, because only then can our sound engineer continue working.
Another point was the lateral tracking of the autopilot. Do you remember the screenshot with the egg dance flight path? Fortunately, that's history.
Now there is another important building block that we have to cover. The aircraft systems calculate the planned flight route, speed, altitude, vertical climb/descent, etc. based on various factors. We've come this far. Now we have to teach the autopilot to work with this data. But the best planning is useless if reality gets in the way. So this data must also be constantly recalculated in real time. We are currently working on this.
As you can see from the previous screenshots, we have almost finished the 3D model. So this milestone has already been mastered. Now we "just" need the systems to do what we want them to do. We will give you more information on this soon.
The use of checklists is not only important in real aviation, but also in flight simulation. Especially for new users of MSFS, checklists can be extremely helpful. They serve as a learning aid by explaining the necessary steps and procedures step by step. The integration of checklists into our A330 addon is very important to us. This allows users to practice the same procedures and processes that are used in real aviation. Especially beginners tend to forget important steps or settings, which can lead to unwanted problems.
In addition to our future online documentation, we offer a direct and interactive way to familiarize yourself with the aircraft with the standard MSFS Checklist menu. Due to the complexity of some procedures, we cannot guarantee the auto-complete feature everywhere. However, each checklist item is provided with a clickspot that allows users to quickly and easily navigate to the appropriate area in the cockpit.
This means that Xbox users and newcomers in particular need not be put off by the complexity of the A330. Instead, they will quickly be able to get used to the handling of this large aircraft.
In the world of aircraft, there are many fantastic liveries. Each airline has its own unique design, and in Microsoft Flight Simulator, these repaints come to life with stunning realism. Our A330 takes advantage of cutting-edge technology provided by Asobo to deliver both high detail and smooth performance, making even the tiniest logos and details appear sharp.
We've already crafted some highly detailed liveries for the A330, and these will be available for everyone when the plane is released. Now, we're also introducing a voting system that allows you to have a say in which liveries will be included on top of that. The list includes liveries from some of the most iconic airlines, both past and present, operating the A330-343 with RR engines. For this, we’re collaborating with skilled artists renowned for their livery design expertise. This means we'll be able to offer more liveries from day one, and they'll be available to both PC and Xbox players.
Additionally, we've put together a kit with easy-to-follow instructions, making it accessible for anyone to create their own livery designs using the “old” texture technology.
The voting has ended. Thank you for participating!
It is said that there are people who like numbers. Our team happens to consist almost exclusively of such people. On one side, there are the programmers, who solve the most exciting functions with acrobatic calculations. On the other side, there is the project manager, who is ultimately measured by the numbers. So, it's time for a few insights:
The A330 is currently undergoing internal testing. We have around 20 testers who are tirelessly putting the aircraft through its paces. We currently have 285 reported bugs and improvement requests on our development board. About 30 of these are low priority and therefore at the bottom of the list. An additional 90 have already been fully evaluated, assigned to employees and are ready for processing. 29 others have already been resolved and are awaiting the next release for the test team. The remaining batch requires more detailed evaluation before it can be phased into the "production" process.
The issue categories in the graph can give you a good idea of the current status of the aircraft. Of course, it must be taken into account that none of the figures reflect the complexity of the individual tasks. It is quite conceivable that 9 out of 10 bugs can be solved within a week, but the 10th takes a whole week. Our current focus is to sort out the bugs first before continuing to add more features. Nevertheless, the numbers are important for us to measure our own productivity and - once the numbers are lower overall - to estimate a potential release date.
The A330 platform project is truly extensive. Although we already have a good A330 product for Prepar3D, we have repositioned for the MSFS variant. For example, the 3D model was designed from scratch for the Asobo 3D engine and various systems were not simply taken over, but fundamentally changed to provide a stable and smooth experience.
Currently, the aircraft is at a stage where almost all the planned systems work and you can get the aircraft from A to B safely. There are a lot of things that are really fun. The 3D model looks great, the EFB is a highlight, and many systems are very extensively coded. However, there are also some cases that pop up during flight testing that are not yet handled correctly by the aircraft systems. This is because critical systems such as the flight management system and autopilot had to be coded from scratch.
Here are a few examples where things are not yet running smoothly:
- The lateral tracking of the ILS approach is not precise enough under certain circumstances and lets the aircraft touch down next to the runway.
- With certain waypoint types the autopilot does not intercept the following track correctly but oscillates around the track.
- After importing a flight plan into the MCDU, performance losses are noticeable. Entering the same route manually, however, does not cause any problems.
Furthermore, we are still working on the soundscape and the usability of the cockpit. At the same time, we are already working on the documentation. We also want to produce tutorial videos in advance. After all, there should be enough learning material available from day 1 to give everyone an understanding of this complex aircraft.
A quick look into the project technology: There are currently some technical restructurings taking place. This means that server structures are being changed, workflows are being optimized, cooperation with the testers is being improved and -where possible- processes are being automated. This all contributes to creating a professional and stable development environment, which consequently leads to our developers working more efficiently and progress being published faster.