This version update includes the modified C172.acf and C172_G1000.acf that use the new nosewheel steering parameters, so you can try out the new bungee steering in default aircraft now. We’ve heard pretty positive feedback on the new handling from the pilots we’ve asked to try it so far!
The interaction of the nose wheel with the rudder and brakes now closely resembles a real C172: The nosewheel is no longer rigidly connected to the rudder, but by a spring-loaded steering bungee. This connection allows a steering angle of about 10 degrees, giving you three times the precision in steering that you had previously! But sometimes you don’t want precision, you just want to make a tight turn – in that case, you use differential braking. This will pull the plane around in a tighter turn, and with the new steering bungee, the nosewheel will follow that turn without skidding, because it can castor beyond the steered deflection.
If you don’t actually have hardware brake pedals, X-Plane will add the differential braking for you when you ask for maximum rudder (using your joystick twist axis).
For aircraft authors looking to incorporate the new parameter into their planes, there is a much more detailed description here.
Full release notes here.
Edit to add: As usual, Steam release will be delayed about 24 hours–expect it to be live sometime tomorrow.
A minor patch is now available for LR customers. We expect to release this on Steam in about a day. You will need to run the installer and opt into betas to get this version. It includes improved C172 steering, an asynchronous map, and .lin fixes. Full release notes here.
Update: the announcement here says better C172 steering but actually the aircraft file has not been updated and behaves exactly like the C172 in the previous release. The physics model does have an update that allows authors to simulate bungee-cable steering (like the real C172 has) – we’ll enable this in the default Cessna soon.
It’s officially out the door! (Steam should go “final” later this evening, but you can get the final now by opting into public betas — it’s still marked as a “beta”.) This was a fairly large release, and here’s everything it includes.
We expect to do a bug fix patch in the next week or three, depending on the severity of the seemingly inevitable “bug that got away” during beta testing.
X-Plane 11.35r1 is now available. You should be able to auto-update from within the sim as usual with this version.
This update should just about wrap up the beta for 11.35. If you haven’t tried your add on with 11.35 yet, you have pretty much missed your chance as we expect to mark 11.35 final and roll it out for everyone soon.
Release notes here.
Beta 6 is now available to fix the hang with auto update. Please note that it will actually take two (2) rounds of updates to see the complete fix. B6 will still hang, but it contains the fix so that when you update after that, it should work as usual.
To get beta six, run the updater and click “get betas”. Once you have beta six, the next update will work normally.
Release notes here.
We are nearing the end of the beta cycle and it is highly likely that the next build will be a release candidate. (Release notes here.) I’ll continue to sound like a broken record: please test your addons if you haven’t done so already!
One thing of particular note for aircraft authors in this update: we added datarefs to read the contents of the X-Plane default FMS Control and Display Unit (CDU) screen. You can read more about this addition here.
Beta three is now available to LR customers, and we expect Steam to be available within 24 hours. This beta has the last of our planned code changes for 11.35 (in addition to bug fixes), so we expect the rest of the beta period to be focused on fixing regression bugs.
If you haven’t already, this would be a great beta to test your add ons in to ensure we haven’t broken them. If we have, get at us via the bug report form and be sure to include a copy of your add on.
Edit: 11.35b3 is live on Steam too now.
We have fixed the two high visibility bugs reported over the last couple days, and now have beta two out. This build should have fixed the cloud rendering issue as well as the scenery pack typo.
If you had installed beta 1, you should be auto-prompted to update. It is also live on Steam.
The first public beta for X-Plane 11.35 is now available! (Steam is staged and will be released shortly.) This is an update that includes new Gateway airports, FMOD sound for the Boeing B737-800 and KingAir C90B, improved aircraft systems, and landmark scenery packs for New York and Washington D.C.
Aircraft developers will want to review Philipp’s notes on the:
Bug fix highlights include multiple metar interpretation fixes, an ATC crash bug fix, and fixes to many of the default aircraft.
Full release notes are available here.
Update: We are aware of a cloud rendering bug with anti-aliasing. The work around for now is to turn off or use the lowest setting of anti-aliasing.
We are working on b2 to fix this issue and will be holding the wide release of the Steam beta for the fix. If you really, really, really want to use b1 with this known issue, you can email me directly at my first name @x-plane.com and I’ll get you into the private Steam beta.
You can now grab the WED 2.1 beta here. This is a minor update with bug fixes and enhancements such as extending the facade preview to all types of facades and to the map window. You can also read Michael’s extended release notes here.
New Meta-tag Identifies 2D or 3D Airports
We’d like to point your attention especially to the new “2D” or “3D” meta-tag for export targets of 11.30 or higher. This tag tells the X-Plane GUI to list the airport as “2D” or “3D”.
Before X-Plane 11.35, the information in the “Features” column in the X-Plane airport selection menu came from any scenery in a user’s Custom Scenery directory, rather than being an entry in the system-wide apt.dat in the Resources/default scenery/default apt dat/ directory. The assumption was any addon airport would always be 3D. But starting with X-Plane 11.33, all global airports, even those with 2D-only layouts, were now included
in the Global Airports –which made the X-Plane GUI effectively list every airport as “3D”.
At export, WED 2.1 will analyze the scenery for 3D content and look for the existence of the meta-tag “GUI label”. If the export target is 11.30 or higher it will warn if the tag is missing or improperly set, ultimately leaving it up to the designer how they want the airport to be listed in X-Plane. If the target is “Gateway”, it will forcibly create or update this meta-tag to always be set correctly according to the actual scenery exported.
In order to fix the 2D/3D display in X-Plane 11.35 and later for any scenery not submitted via the Gateway, authors will need to manually add the tag via “Airport->Add Meta Data” and then re-exported to a target of X-Plane 11.30 or higher.