An advanced apology to anyone whose comment gets nuked as spam. This blog, like all blogs, gets attacked by spammers who put links in their comments to boost their pagerank.
So if I’m not sure if you’re a real commenter or a spammer, sorry, but I’m going to err on the side of the chainsaw.
The Cessna 172SP isn’t the fastest plane, but it would get you there a little quicker if it was a twin prop.

(This is what happens when I leave the AI planes on while randomly testing rendering bugs in the middle of nowhere. On the bright side, the two planes do shadow each other.)
Robin sent this out to the news list:
A quick note for X-Plane airport designers (if you are not an X-Plane airport designer then please disregard this message).
Good News – it is still possible to submit new or revised airport designs for inclusion in the X-Plane version 10 scenery generation process. Please send me any submissions before February 7, 2011 so that I can consolidate them and generate the special data files that will be used to generate the new global scenery. I need just the apt.dat file for each airport – if you have multiple airports, please consolidate the data into a single file.
Why is this important? When new global scenery is generated for X-Plane 10, the latest airport data will be used to:
- Define the “land use” in the vicinity of the airport. This will ensure that an appropriate terrain texture is used under the airport, and will also suppress the trees and auto-gen buildings.
- Smooth any terrain undulations in the vicinity of the airport.
- Ensure that runways have “land” underneath them – especially important for airports alongside rivers, lakes or oceans.
The best way to help this process is to define an accurate airport boundary in World Editor (WED). If no boundary is defined, we will try to approximate a boundary based upon all other available data for an airport. If you only have time to create an accurate boundary (but not the rest of the airport details) then that is fine also – I can still use such data for this process.
Let me know if you have any questions
– Robin
My apologies for the earlier false deadline – we thought we were going to cut the global scenery a lot sooner.
X-Plane’s log file is our attempt to capture everything we could possibly want to know about your computer in case something goes wrong. (There’s no personal information in there – we want to know things like what kind of CPU and graphics card do you have.) We do this because a fair amount of tech support comes from configuration problems; having the sim tell us the configuration saves tech support time in explaining how to gather configuration information and eliminates the risk of user error.
This matters because a fair number of bugs and tech support requests come from strange system configurations…often we don’t even know what was wrong until the user later reports fixing the problem by adjusting a piece of hardware that we didn’t know existed. Here’s one example from last week:
Hi Guys, I just wanted to let you know, I got X-Plane working! It turned out it was my sound card. I don’t actually have a sound card…I replaced my RealTek USB speakers with a small gnome that lives on top of my motherboard. The gnome yodels what he thinks I should be hearing.
Well, it turned out that last week the gnome went on a wicked bender and passed out and shorted out my PCIe bus…I think that’s what was causing X-Plane to freeze. I gave the gnome some charcoal pills and black coffee and the sim runs great!
BTW when is X-Plane 10 coming out? Do you need beta testers? 🙂 🙂 🙂
Okay, I admit, I made that up. But…that’s not far off from reality – just replace “gnome” with your favorite barely-compatible-with-DirectSound pro-level recording sound card. Anyway, our response to this kind of thing is visible in the log…e.g.:
Sound Card: gnome (B.A.C. = 0.02%)
There is one down-side to the log: some users seem to like to report every single line of the log to us, with the question “is this a problem?” We’ve been trying to make it more obvious what’s an error and what’s just information. (Hint: most of it is information…except for the lines with the word ERROR in big bold letters.)
Therefore I make this suggestion to plugin developers re: the use of the log file.
- Do identify all log output as coming from your plugin.
- Do log serious errors that will be needed in crash forensics.
- Do not log errors that are reported to the user. If the user opens a file and it’s the wrong version, and your plugin presents a dialog box, you probably don’t need to also log the error.
- Do log configuration information needed to triage a system.
- Do not log routine status from normal operation – not in a release build please!
Google announced today that the Android market is now available on the web. It’s really quite nice and the best feature is that apps can be purchased directly from your desktop computer and installed over-the-air (that means no tethering like in iTunes) directly to your Android device. It’s quite cool!
Here are the links to our stuff. Please share them with your friends. You can even tweet about it right from the market listing.
https://market.android.com/details?id=com.laminarresearch.xplane_default
https://market.android.com/details?id=com.laminarresearch.giant_robots
Well, they are new at least. The new installers/updaters are now posted. Version 2.06 fixes Linux DVD problems, but also has two features that should be nice for users who beta test heavily (and grab full demo installs off the net to do so):
- The new installer/updater keeps net connections alive, which really helps download rates per connection.
- The new installer/updater connects once to each server, balancing the load between servers.
Previously you had to pick one server and poke around until you found the fastest one. By keeping connections alive and using all servers, we should get fast, even download times for everyone.
…and who gave him access to source control?
Seriously, Chris is the third and most recent developer to join the team – he’s been full time with us for a while now, working mainly on the new ATC system for X-Plane 10 and the Android port of X-Plane mobile.
Like Randy and Austin, Chris is a real-world pilot. He also worked on some of VATSIM’s core technology back in the day – AVC and VATSIM’s voice-over-IP tech and XSquawkBox.
Please don’t flood him with “will ATC do X, Y and Z” questions; since version 1 of the new ATC engine hasn’t been released yet, it’s a little bit too early to start the discussion on how to extend it.
If I had a dollar for every time I saw this question asked on Facebook, forums etc I’d be richer than Warren Buffett. I have to say though, I can’t really blame people for asking because our track record for releasing news has not been stellar but that’s changing as we improve our online front. Stay tuned for more news on that!
You have to understand that it is not as if we’re keeping the release date a secret, it’s that we don’t have a hard date set at the moment. I will reiterate that we’re all working really really hard. This is not a 9-5 job where you punch in and punch out and go home and forget about work. We’re all pretty much chained to our computers most of the time because like you, we REALLY want X-Plane 10 to go live as well. It’s going to be a great step forward for the flight simulator community.
So when is it coming out? When it’s ready and not a moment sooner or later! Trust me, you’ll be the first to know when we have updates to share.
For the last few weeks we’ve been working behind the scenes to modernize our web infrastructure. Now that we have the new web server running, I (and by me I really mean Chris, because he did all the work, which makes this the best transition ever) am merging the X-Plane Scenery blog into the new development blog.
All of the old posts have been transferred to the new blog. The old blog is still in place; the main page will redirect here but the individual articles will “stay” in your browser for convenience – there are plenty of links to the old blog on various forum posts, etc.
If you have the scenery blog bookmarked, please update it to http://www.x-plane.com/blog/.
Posted in News
by
Ben Supnik |
A quick update on a few X-Plane 9 bug fixes we have in the works. We will hopefully cut a new beta of X-Plane 96x in the next few days.
- Linux DVD recognition was unreliable and required work-arounds; my attempt to fix this in X-Plane 964 made this work, but we have a real fix.
- We have a handful of hang-on-startup problems with NVidia cards and Windows 7. I am working directly with a few users to figure out what’s going on, but I hope to have a work-around in a patch as soon as we ID it.
- We have new installers that I need to roll into beta; they will address DVD location issues on Linux and also improve net performance.
The numbering scheme for v9 is a little bit odd at this point. Since we are putting so few changes into each build, Austin has been numbering them as “release candidates” – that is, 962 was final, then he cut a 964 and 965. 964 and 965 were both only available by checking “get betas”, and both turned out to have defects. When 966 is ready, it will be available via “get betas”, and we will promote it to a “real” release if it turns out our bug fixes actually fix things.
So: egg on my face for being 0 for 2 with 964 (in that both my QuickTime fix and Linux DVD fix actually made things worse).