FlyJSim, a well-known developer on the flight simulation scene standing behind a high-quality renditions of Boeing 737-200 and 727, has today shared via their website a development update regarding the currently developed Q4XP and Shared Flight.
As the post was very extensive, I will try to summarize everything mentioned in the post here. At first, developers have focused on the current status of the upcoming shared-cockpit plugin called Shared Flight.
Aircraft such as FlightFactor A320, ToLiss A321, Rotate MD-80, IXEG 737-300, or Hotstart TBM900 will be compatible with the plugin at the initial beta launch. A complete list can be seen below on the picture. Keep in mind, that only aircraft that will be compatible at the beta launch have been included in the list.
The plugin has just recently moved to expanded Alpa. The first wave of alpha invites were sent out to FlyJSim Discord members. There are currently over 70 alpha testers.
Our aim with Shared Flight is to have users trust the process. Flying with others shouldn’t be more complicated than flying solo.
An example of a flight flown on Shared Flight was part of the post. FlyJSim wrote:
As you can see by the flight plan, they did not have the most comfortable ride. But this is exactly the type of situation where CRM starts to become an essential part of flight simulation, and Shared Flight enables this.
A hint of ability to spectate the flight as a passenger has been included in the post. This is just a speculation of the author.
This is also quite the spectacle for the real passengers spectating this flight, only available with Shared Flight.
Multiple previews of the UNS and overall system functions have been included in the post. All can be seen below. The development of the aircraft is progressing well.
FlyJSim has explained the difference between UNS and the default FMC. The biggest improvement is, that the UNS takes everything into consideration, and is not only used to route planning.
Therefore, everything gets considered into the simulation. Sensors, electrical input, approach handling, data handling is all a deep part of our simulation.
It was explained, that the developers are aiming for the best realism possible. Each UNS unit will compute at realistic times and will even simulate a linear lag time with a screen change.
More information should be available soon as FlyJSim has decided to not only share development updates quarterly. More alpha invites will be sent in future.