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.
X-Plane 11.35 beta 4 is now live – run our updater and check “get betas”. Release notes here.
Steam users: we’ll release this tomorrow if there isn’t a sign of a huge fire overnight – it’s already uploaded to the servers.
Add-on Developers: if you haven’t run your add-on in 11.35, please put it through its paces now. Everything that might be risky or weird is already in and we’re just killing off bugs now. If your add-on has a compatibility problem, we need to know now if we’re going to fix the problem during beta. While we’ve tried to make everything “just work” with old add-ons, there’s always the chance that your add-on does something special we didn’t think of. Please test now!
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.
Here’s our keynote talk from FlightSimExpo 2019 last week!
Evans video team really did a fantastic job with the feed this year – everything was live-streamed in great quality, and the talk has a direct feed to the slides and good quality audio. Totally what we were hoping for!
In the past, our posts breaking down X-Plane usage data have been… well… intermittent at best. Not because we don’t think sharing this stuff is important—it absolutely is—but simply because gathering the data, putting it into nice charts, and writing up a blog post took time away from developing X-Plane itself.
Whenever we encounter a problem like this, we try to pull back and take the humans out of the process. Out of that philosophy, let me present to you:
It has been some time! I have been working as hard as I can on the
converter (to great applause so far!), but, there have still been some
features and fixes developed along the way. By now it was time to
collect and release them!
As always This is a beta. It makes data model changes which may still have bugs. Make backups!
“Cast Shadow (Local)”
Previously, you could only set “Cast Shadow” to be on or off for “Scenery” and “Instanced Scenery” export types. This would, for the whole object, turn on and off shadows. Now, “Cast Shadow” has been removed from the OBJ settings and “Cast Shadow (Local)” has been placed in the material settings. With this, individual meshes can have shadows or not and it works for Aircraft and Cockpit objects too!
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:
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.
As you may have heard, we’ll be at FlightSimExpo 2019 in Orlando this weekend! If you are attending, please stop by our booth and drop in on our talk Saturday afternoon. We’ll be qualifying people for a VR landing contest too.
For developers: Austin, Philipp, Chris and I will all be there – find us to talk about developing add-ons for X-Plane!
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.