Since the release of FlyJSim’s Q4XP, the primary complaint from most users has been the poor frame rates experienced when flying the aircraft. FlyJSim has been working away to improve the experience in the aircraft and has today shipped out the first update to address the issue.

Today’s update is not the first to be released for the aircraft since release, many smaller patches have been released over the weeks following the release, mainly fixed bugs and crashes discovered by users throughout their use.

Many of these issues were driven by the sheer amount of manipulators found in the cockpit, mainly driven by each circuit breaker. Today’s update has replaced many of the manipulators with new, low poly, click spots and command-driven manipulators. The primary goal of such a change was to reduce the strain on users systems when trying to read each individual manipulator.

The cockpit performance was not the only area the update addressed, the new build also brings initial support for VR, as well as many bug fixes relating to the UNS system.

Here is the changelog for V1.11:

Performance

• Cockpit manipulators were replaced with low poly count click spots as well as command-driven manipulators.
• These new manipulators improve performance in and out of VR as well as facilitate those who need commands driving hardware such as cockpit builders.
• Larger click spots make many switches and knobs easier to select.
• Performance increases will vary by user, more improvements will come next year.

VR

• Initial support for VR comes with the new manipulators as well as much improved performance.
  

UNS

• Fix crash when inserting index 0 on the VTO page.
• Fix WPT ALERT not computed when Track-to-Fix termination conditions aren't met.
• Fix hold legs not getting pre-computed when WPT ALERT isn't triggered.
• Fix DF leg computation when the target location is within turn radius (RTT 3J departure LOWI).
• Fix waypoint ETA clipping on MFD map.

Visuals

• No more shiny control seals.

JPad

• New Option was added to give you different options for throttle and prop handle manipulators.

It is worth noting that FlyJSim states that the new update will require a reactivation of the aircraft after updating from V1.10.

Don’t own the Q4XP yet? Find out if the aircraft is for you by reading our review of the aircraft or watching our media department’s thoughts on our YouTube Channel.

Make sure to not miss any Q4XP updates by keeping an eye on the FlyJSim Discord.