Category: News

X-Plane 10.30 Beta 4 Is Out

A few notes on beta 4, which went live today:

• Austin fixed a bunch of METAR parsing bugs.  As before, please include the METAR and airport any time there is a METAR parsing issue.  There were a few common cases that were broken in beta 3 that caused most of the bug reports, so we should be in better shape now.
• Philipp fixed a pile of bugs.
• I did not.  My C drive died again, and I am ordering a new PC now.  So unfortunately I can’t look at AMD or Windows performance bugs until I get new hardware.
• This build contains a rework of our cylindrical projection code – this is a feature that our Pro key enables; we’ve been working with customers for a while now to design the new system.  We’ll be working out the kinks over the rest of beta.

One last note on METARs: when X-Plane finds a METAR with “unlimited” visibility (e.g. 9999, CAVOK, etc.) it will look at the temperature-dewpoint spread to determine the humidity, and then pick a visibility distance that is lower when humid and higher when dry.  So under truly dry conditions you should get a less hazy view, while visibility will continue to be constrained on humid days.

Update: the 32-bit Mac version of beta 4 won’t run due to a build configuration problem. We’re working on it now, but I’m guessing it will be 36 hours before we get beta 5 posted. 🙁

X-Plane 10.30 Beta 3 Is Out

Beta 3 just went live.  Release notes are still here – the document grows!  When the beta is done I’m going to have it printed and use it as a weapon to squash house flies.  Bug reporter is still here.  Bug reporter is still not the comments section in this post.*

The short summary is: Philipp crushed a huge pile of GPS bugs, and I crushed none of the cloud-related bugs.  So please read the bug fix list carefully before you report.  We try to make sure there’s a bug list bullet for every single fix in the beta, so that you don’t have to waste your time (or ours!) re-reporting a bug that isn’t fixed.  If you reported (hypothetically 🙂 that cloud performance makes you weep (and not in a good way), there’s no need to re-report, I haven’t gotten to it yet.

If you have not tested your payware add-on with X-Plane 1030, please do so ASAP!  We do not have a pile of known issues with third party drawing, so if you see something, say something.  (We have a number of possible bugs that aren’t reproducible yet – so your bug report might be what lets us get to the bottom of things efficiently.  Only you can prevent forest fires!)

* This post comes with an extra helping of snarkiness…Chris and I made the really poor decision to try to debug part of the X-Plane airport gateway deployment from 11:30 PM to 3:30 AM land night.  Since we both have small children who didn’t get the memo and woke up at their normal time, I am, at this point, pretty much unaware of what I am typing.

X-Plane 10.30 Beta 2 is out

I’m a little slow at blogging this, but 10.30 beta 2 is out – beta 1 users received an auto-update notice.

Please report bugs here.  Starting now I am going to delete comments that are bug reports.  I really can’t be any more clear about this: please report bugs in the bug report form and not on the blog post.*

The release notes are here.  I broke up the bug fix section by beta so you can see what is new in beta 2.

I have already received reports that the “fix” to the slow local map is not actually a fix at all. Unfortunately my C drive lost sectors (again) so I am behind in investigating both this and general performance complaints.  I’ll need to rebuild the machine before I can get to these things.

* Why am I being such a jerk about this?  Two reasons:

1. I don’t want bug reports to get lost.  Sending me a private email, posting on a blog, etc. — these are all recipes for bugs to get lost.
2. Efficiency.  I just spent an hour triaging X-Plane 10.30 bug reports and that was only bugs that actually went into the bug reporter.  Those are the fastest bugs to triage because we have an efficient system to deal with them.  Every bug that is in the wrong place takes twice as long for me to deal with.

So bugs posted to forums, blogs, email, these are at best slowing down the beta process and at worst getting lost.  (Especially forums – since I don’t read them, they are by definition lost.)

And as a final rant: emailing with “should I file a bug about X” is inefficient for everyone. It takes as long for you to write the email as to file the bug.  It takes us time to read the email, answer, then get the bug.  Just file the bug!

The What And When of X-Plane 10.30

(Spoiler alert: the answer to the “when” question is going to be deeply unsatisfying and annoy you.  Sorry – there isn’t a date.  But at least you’ll know what’s going on.)

It’s been over four weeks since Philipp publicly demonstrated an early X-Plane 10.30 build with the new GPS.  What’s going on now?  What about 10.30?

What’s In X-Plane 10.30

Here’s a rough overview of what’s going into 10.30.  We’ll have a complete change log when we release a public beta; right now the change log is not compiled, and it’s going to be long enough that I can’t go through everything now for a blog post.  (To give you an idea, Austin has 158 commits on his branch going in.)

The one truly big new features is the new GPS Navigator that will ship in X-Plane 10.30.  Please note that an aircraft must be modified to take advantage of it.  It looks like a basic modification (e.g. if the aircraft already has the old G430) should be a few clicks in Plane-Maker.  Similarly, you can add the GPS to your aircraft with drag-and-drop in the panel editor.

Philipp has Oculus Rift support working but we’re still trying to figure out whether to ship it in 10.30 or wait; the actual Rift support is usable but the user interface is still quirky.  Since they’re not actually selling devices to consumers yet we may wait.

We’re working on a number of visual improvements:

• Tuning and improvements to the look of the clouds, including their behavior as you fly into and out of them.
• Optionally increasing the distance the DSF scenery is drawn for better long-range rendering.
• Better fog in lower visibility situations.  (I’ll try to post some experimental pictures over the next few days.)

This stuff is not finished – in particular, my fog work is not done yet, but if we can get it all working together it should make the visual experience in X-Plane 10 a lot better, and a lot closer to what we imagined.

Under the hood 10.30 contains major changes to Plane-Maker’s panel editor and the entire OpenGL stack; these changes don’t provide any immediate features – this is just us putting in new infrastructure for future updates.  I mention this only for completeness; infrastructure changes can cause bugs that we’ll fix before and during beta, but they’re necessary to keep the product evolving.  The OpenGL changes in particular can affect plugins if they haven’t followed plugin SDK guidelines.

10.30 has some small extensions for third party developers, including a number of new dataref-based interfaces to customize sim behavior; we held off on this kind of thing during 10.20 to ship 64-bits faster so now we’re catching up on adding flexibility for third parties.  I’ll post a complete list with the release notes; some of this work is already done and some is still in-progress.

Finally there’s just a huge number of bug fixes, including a number of high profile and stubborn bugs.  Please do not ask about your favorite bug in the comments (I will nuke your comment!).  We will post complete release notes when we reach public beta.

The Release Process

We’re trying two changes to our release process for X-Plane 10.30:

• We are doing extensive private pre-beta testing before the public beta.  Normally we release a public beta and get 300 reports that all tell us the same one big bug.  This time we are starting with a much smaller group of testers and slowly growing it; this gives us much more efficient feedback and should speed the whole process up.
• We are doing private testing on parts of the sim individually before we jam them all together.  I’ve had users test my “lots of DSFs” code separately from Philipp having people test the GPS.  Traditionally we’d test everything at once, and the chaos of having so much new code in one single build made life hard for both testers and developers.  So this time we’re  starting small and slowly bringing the pieces together.

(Please do not email or post requesting private beta access – we are not looking for additional testers at this time.)

This process is an experiment; when 10.30 is done we’ll have to step back and see if the added complexity saved us real development time.

When Will 10.30 Be Released

We are currently privately testing some parts of 10.30.  My expectation is that we will reach a public beta of 10.30 with the GPS, but without all fog-related features in weeks. (I don’t know how many weeks – it depends on how fast the current bugs get fixed and what new bugs are found.)  Austin and I have differing views on this; I always push toward “don’t public beta until all of the bugs are gone” and Austin pushes toward “let’s get people the new GPS ASAP.”  I think the actual public beta will be somewhere in the middle.

The current plan is to get the GPS public before we integrate some of the newer fog features so that users can use the GPS (and third parties can start to add it to their airplanes) without everyone being held back on my incomplete fog code.  We’ll roll the fog code in when it becomes stable enough.

What Else Is Going On That’s Not In 10.30

A few things that are not part of 10.30:

• Alex is still working on autogen; we’ll release art assets when they are complete and shippable, but 10.30 won’t wait for them.  (10.30 does have the autogen engine enhancements he needs.)
• I still have a bug left to fix for DSF recuts; those also aren’t tied directly to 10.30.
• The Airport Gateway and WED 1.3 (to send airports to the gateway) are in late development and early test; they’ll ship as soon as they are ready, but don’t require an X-Plane update.
• Once the Airport Gateway is live, we’ll gather up all of the airports users have shared with us since X-Plane 10.25.  We’ll include those airports in an X-Plane patch whenever they’re ready – if that’s after 10.30 we can do a small update to push out airports very easily.

Put another way, X-Plane 10.30 is mainly about code changes; if the various art asset and data updates become available early enough, they’ll go into 10.30 but if they don’t, we’ll do a 10.35 or some other small patch to get them to you as soon as we can.

A Dispatch From Fearless Leader

From the big boss, earlier today:

OK you folks have not heard from me in forever, but trust me when I say it is because I am busier coding than you can imagine!

We are getting very close to X-Plane 10.30 Beta 1, and the feature-list is simply extraordinarily huge.

These will all be “making it work just perfectly” type features to really dial X-Plane in to the point that it is doing the job it needs to do, free of bugs or other quirkiness that make complex programs difficult to use. I will be announcing the beta when it is ready for public testing (we have been in private beta for some weeks now).

Next: Here is a cool new helo that was just introduced for X-Plane:

//xplanereviews.com/index.php?/topic/175-aircraft-review-bell-407-by-dreamfoil-creations/

I usually do not announce each new craft for X-Plane since there are so many of them, but in this case I just had to make an exception since this bird looks just so darn good.

So, look for the public 10.30 Beta soon, and give the Dreamfoil 407 a try if you like!

austin

I’ve been meaning to post something about 10.30 too, but every day is exactly the same: I wake up, think I should post a status update and go “oh, I’ll do that later when I’m too tired to code.”  Follow that with: code all day, survive dinner and bed-time with a two-year-old, and inevitably I end up being too tired to even post a status update.

I’ll get a few details up in the next 24 hours.  Having put it in writing, now I can’t put it off anymore.

New approach-capable GPS navigator in X-Plane 10.30

X-Plane has been lacking a decent navigation solution for general aviation aircraft for a long time. The built-in GNS430 instrument could only do direct-to navigation and not use X-Plane’s FMS plans, making long IFR flights inconvenient.

In X-Plane 10.30 we are introducing a new generation of the X-Plane 430 GPS navigator, modeled more closely after the Garmin 430W that is very popular in general aviation aircraft. The 430W is a popular aftermarket GPS replacement in many older general aviation aircraft, because it is approved for WAAS approaches and thus an easy upgrade to allow flying instrument approaches at lots of smaller airports without ILS.

The new X-Plane unit can create and fly multi-leg flightplans in addition to the direct-to function:

You can create directs or flight plans using a worldwide database of airports, fixes and navaids:

Loading or saving the route works using the X-Plane FMS format. Many online services for virtual flight planning are compatible with that:

You can then navigate along your flight plan using one of different map views that provide situational awareness:

While flying under VFR, stay alert to any Bravo, Charlie, Delta or special use airspace in the United states (open database, user-expandable):

You will be warned when you are about to violate an airspace:

using the nearest airport function you always know your nearest alternatives for landing (though we all know X-Avion does a much better job at that!)

With a little help from your friend, knowing when to start your descend becomes easy:

Before landing, always know who to call:

For IFR approaches, load precision and non-precision approaches from a world-wide, updatable database:

Review approach transitions and initial approach fixes:

and then load any approach and transition into your flight plan:

Under ATC (read: when flying online) the vector-to-final function will often be used instead of a transition:

The X-Plane 430 is there to help you stay alert to common errors in approach navigation:

The GPS is capable of flying non-precision GPS-approaches with a localizer-like guidance and varying CDI sensitivity:

If you don’t see the runway at the minimum descend altitude, continue to the missed approach point and the flight plan sequencing will go into suspend. At the missed approach point, if you still don’t see the runway, begin your missed approach:

and then get help choosing the right entry to the missed approach holding:

The new GNS430 is a drop-in replacement for the old one, so every X-Plane aircraft equipped with the GNS430 automagically becomes more IFR-capable with the 10.30 update. We also provide an additional instrument in style of the bigger GNS530, that designers can use in their aircraft starting with Plane-Maker 10.30. It also allows for dual installations that can either use separate flight plans or cross-fill.

The interaction of the GPS with the rest of the panel, especially the CDI and the autopilot, has been improved, offering a few more options for aircraft designers. Two additional posts explaining the new options in Plane-Maker will follow shortly.

The database from which approaches are loaded is provided by Aerosoft. A current database will be provided once with X-Plane 10.30, and further updates will be available on a subscription basis.

You might have noticed stupid COM frequencies in some screenshots. This is not a bug, but a feature: X-Plane 10.30 supports 8.33kHz channel spacing, that is now mandatory in the European upper airspace and will become more important over the next few years.

For the inevitable question “will it have X and does it simulate Y?” I do have one answer:
I chose the feature-set for the 10.30 release carefully to fulfill two requirements:

1. It must simulate the functions I use every day. After spending about 40 hours flying a C172P with this equipment, I have developed some pattern in day-to-day use. The simulated equipment must have the functions I use every day.
2. It must simulate what I need for my IFR checkride preparation. I’m currently studying for the instrument rating. All IFR GPS functions that are needed during the lessons must be simulated so I can use X-Plane to practice at home.

This does not cover all functions of the real unit, but it covers what the pilot absolutely needs every day.

Irons in the Fire

Here is a quick update on some of what we are working on.  This post won’t contain everything, as some development efforts are still under the radar, and it’s not a comprehensive list of 10.30 features.

(I am not ready to post a 10.30 feature list yet; please do not comment with “will XXX be in 10.30”.)

The Airport Gateway.  That’s what we are calling the website we are developing for sharing lego brick airports.  The X-Plane Airport Gateway is under construction and has already reached an internal milestone; when finished it will be the portal through which you can share lego-brick airports with the community for inclusion in X-Plane.

We have decided to provide direct upload to the gateway from WED in the initial roll-out of the gateway; it’s a simpler work-flow and it is what we always planned to do eventually.  So there will be a WED release (probably 1.2.2) to match the gateway.

I believe the gateway may go live before 10.30 goes final. (I believe this mostly because I think 10.30 will need a loooooong beta) so at this point we’re looking at how to transfer all shared airports into the gateway, rather than looking at how to release airports without the gateway the way we did in 10.25.  We do want to upload all of the data we already have into 10.25.

Autogen.  Alex is working on a set of autogen that will greatly improve the coverage, variety, and correctness of US autogen.  I do not know when he will complete this task; we will release the work whenever it is ready, possibly in a point release of X-Plane just for autogen.  Basically if 10.30 is in beta when he is done, the work will be rolled into 10.30 betas; if it isn’t, we’ll do a 10.35 or something for the autogen.  The autogen is basically an art-asset update, so it isn’t strongly tied to X-Plane code.

Bug Fixes.  A big part of 10.30 is bug fixes and quality improvements, and a lot of the bugs that we are working on are hard to fix.  (If they were cheap to fix, we would have fixed them in 10.22 or 10.25.)  Our view of X-Plane 10 is that there are a lot of new features that need tuning to meet their full potential, so we are trying to focus on high quality for what X-Plane 10 does, not on expanding X-Plane 10 into (even more) new territory.

As get some of those bugs fixed, I may post a few “call to test” posts – we are looking to do significantly more private beta testing in 10.30 to get specific features tested before the flying circus of public beta starts.  (Please do not request private beta access unless we’re calling for testers.  Our goal is to have new features and bugs fixed by people who are specialists in that part of the sim.)

Third Party Interfaces.  We’ve built up a number of requests for datarefs, third party interfaces, etc. that we haven’t been able to implement in ‘small’ releases like 10.22 or 10.25.  I’m hoping we’ll get through most or all of these in 10.30.  I’ll write up more details when we get closer to a public beta.

DSFs.  We still need to figure out how we will release DSF recuts, but they should be ready when 10.30 is; pretty much all of the work for the recut is already done.

I’ll post more on the 10.30 beta process in a few weeks when we get closer to it.  As of now, the basic coding work for 10.30 is not yet done, so while we have some code to test, 10.30 is not “in the can”.