Ben posted a few weeks ago about our quest for “One Bug Base to Rule Them All“—our goal of cleaning up the fact that we had no fewer than five bug bases running, each for different products, with no communication between them.

This situation is understandably confusing—bugs that dealt with the Airport Scenery Gateway wound up in the WED database, bugs filed against WED wound up in the X-Plane database, and so on.

I’m happy to report that we’ve taken the first steps toward unification: today, we have just one place to report issues with:

  • any of the scenery tools (WED, MeshTool, the AC3D plugin, etc.),
  • airports and scenery packs in the Gateway or in X-Plane, and
  • the Scenery Gateway itself.

All you need to do is:

  1. Create a free Scenery Gateway account and log in.
  2. Click the “Report a Problem” link in the navigation at the top of the page.
  3. Use the tabs to select the type of bug you’re reporting: does it deal with an airport/scenery pack, the Gateway site, or the scenery tools?
  4. Fill in the reporting form with as much detail as you can, and hit Report Issue.

In the future, we’ll move to a similar system for the plugin system and X-Plane itself. At that point, we’ll have one page (probably on the main X-Plane site, rather than the Gateway) with a tab for all the things you might need to file a bug for.

About Tyler Young

Tyler is a software developer for X-Plane. Among other projects, he was in charge of the new X-Plane 11 user interface.

4 comments on “An Update on Our Quest for the One Bug Base to Rule Them All

  1. Speaking of the plugin bug base, Tyler, who is supporting the SDK at this point? Sandy Barbour was doing this with great elan over on the .Org, but he’s flown the coup and has left his website up in legacy mode only. Where do we ask questions if we’ve got ’em — aside from bugs, that is?

    1. First, we have to distinguish between the SDK and Sandy’s personal pantheon of plugins. From what I know, a lot of his own stuff is now in legacy support mode. That’s his call and his alone.

      For the SDK itself, the x-plane-dev mailing list is still in use; I’m on that list so if others don’t have an answer to a Q I can back-stop.

      One of the problems we have is that the SDK website is built on MediaWiki, which was in hindsight not a great decision by me. 🙁 So the infrastructure needs an overhaul that I haven’t had time for.

  2. Please add support for Oculus DK2 or at least steroscopic 3D view since headtracking works fine with Opentrack 2.x!

Comments are closed.