Traffic Global nu geschikt voor X-Plane 11.50+

Wat worden we hier blij van zeg! Gebruikt u net als sommigen van ons ook Just Flight’s Traffic Global voor X-Plane V11+? Dan is er nu heel goed nieuws te melden, versie 1.0.9113 is nu uitgekomen en werkt met X-Plane V11.50+. Deze X-Plane versie maakt gebruik van de nieuwe Vulcan/Metal engine. Het is nog een eerste versie dus nog niet alles werkt perfect, maar wat betreft het AI verkeer werkt het al prima zowel in de lucht als op de grond. Nice! De nieuwe installer kunt u op dit moment nog alleen downloaden via Just Flight, maar andere webwinkels zullen snel volgen.

This is an interim release with one purpose: to support X-Plane 11.50, running in Vulkan/Metal mode. There are very few other changes. This does NOT mean that no other changes are planned! There are many others in the pipeline (see below), but the Vulkan compatibility needed to be added in a hurry and the other work is simply not ready to be released.

This build has been tested against X-Plane 11.50 betas 1 through 4, the latest available at time of writing, and works against each in both OpenGL and Vulkan/Metal modes on both Mac and Windows. It has also been tested against 11.41r1. Given that there are several more X-Plane beta releases planned it’s just not possible to guarantee that this will continue to work while the platform it is running on is changing. If something else gets broken in future X-Plane betas then another interim release like this one will be made as soon as possible.

Many other plugins have been tested as part of this update. There are no known compatibility problems with any of the following:
124thATC, A-Better-Circle, Autogate, AviTab, BetterPushback, JoinFS, Gizmo64, SAM, TerrainRadar, xEnviro, X-ATC-Chatter, XPForce.

Please note that some versions of xPilot crash X-Plane on startup if Traffic Global is installed and TCAS enabled, due to incorrect shutdown of xPilot when it detects that the TCAS system is already in use.

Known Problems
*** This is due to a breaking change in the underlying simulator, ***
*** and unfortunately at least for now these is nothing that can ***
*** be done to fix this. Please don’t raise support tickets for ***
*** missing TCAS! ***

– Transitions between certain go-around/circuit legs are not smooth.
– Airports with poorly-defined taxi routes may still use unnecessarily sharp corners.
– If you are using an external weather engine such as xEnviro, correct weather may not be set for a minute or so after the simulator starts. This will affect runway-in-use for aircraft initialised during this period.
– The custom map layers will re-enable themselves if you disable them, each time X-Plane loads new scenery. This is X-Plane bug XPD-10498 and can not be worked around.
– Custom views do not respond correctly in VR. This is X-Plane bug XPD-10412.
– If very few aircraft are nearby, additional false aircraft are reported via TCAS. This is X-Plane bug XPD-10434.
– Wind direction at airports can still cause the runway-in-use to change far too often with variable winds being fed to X-Plane from external weather systems. A fix for this is under development but is much more involved than it seems, and is not yet ready for release. Please bear with me!

Known problems with fixes under development:
– Further work on controlled changing of airport flows
– Enable multi-runway use on a wider range of badly-defined airports
– Significant changes in how pushback routes are calculated
– Several new datarefs
– Additional help for airport designers in the Flightplan view
– Aircraft may turn off the runway too fast for specific combinations of aircraft, runway, taxiway locations and flow
– Several paint fixes
– More efficient networking
– Field-of-view incorrectly affecting networked displays
– Aircraft continuing a reverse-pushback all the way to the first sharp junction
– … and more!

Changes in this release:
– Compatibility with both OpenGL and Vulkan/Metal modes.
– Fix for reading radio frequencies for certain airports.
– Additional logging around the pseudo-ATC. If the above fix doesn’t help, please contact support with your log.
– Crash fix for random crash which was possible when TCAS was enabled and you changed aircraft mid-flight.
– Crash fix for a small number of third-party schedule files which referred to a specific set of airports.
– Crash fix for random crash when removing aircraft after the density setting had been reduced.
– Potential fix for certain commercial, third-party airports affecting calculation of AI touchdown points at airports at the end of long user flights.
– Wind direction is now calculated using the airport’s elevation rather than the user’s.
– Fix for a potential freeze during shutdown.

In addition, several changes have been submitted to WED to highlight some of the most common problems with ATC flows that Traffic Global
is currently trying to work around.

Geef een reactie

Het e-mailadres wordt niet gepubliceerd. Vereiste velden zijn gemarkeerd met *