#X PLANE 10.50 GENERATOR#
#X PLANE 10.50 MANUAL#
#X PLANE 10.50 PRO#
#X PLANE 10.50 PLUS#

What the sim can cope with depends on the art assets as well as limits within the sim.

#X PLANE 10.50 GENERATOR#

This was less of a problem before OSM, which is a lot like feeding a random number generator into X-Plane.ģ. The guidelines of “what is a terrible idea” are NOT well specified. The crash is at the end of a cascading chain of problems, with the original issue often being lost in the fray.Ģ. When X-plane crashes, _X-plane_ doesn’t know what went wrong. Tony is up against several problems here:ġ. I’m also sure the documentation would be very useful for anyone else developing scenery. I don’t know however what is considered a valid road, so if you could provide a validation rule list of some sort, I can then exclude or sanitise the roads and let the user know of the problematic road ID in OSM to fix. With buildings and forests, W2XP will tell the user in the console which OSM object is buggy and they then have a chance to fix it. Often the crash would give no indication of what the problem was and I think if there was a debug mode in XP10 which would spew out more info to the log as well as better error messages, this would hugely help from my point of view. It was painful decompiling DSF files when a crash occurred, commenting bits out until it worked and isolating the entry (These files are huge). I do however sanitise facades and forests as after a lot of experimentation and bugs from users, I found out what X-Plane would allow.

#X PLANE 10.50 PRO#

My own unreleased version I use for my pro sceneries uses a PostGIS backend, and all the data (often mixes of several sources I get out is sanitised and formatted as needed.

#X PLANE 10.50 PLUS#

This has been a plus for users but mostly a huge headache, as preprocessing large amounts of data and trying to clean it up without a database can be a real pain. W2XP has up until now not needed any sort of database.

#X PLANE 10.50 MANUAL#

This area has always been buggy, it even says so in the manual 😉 Roads are just one of many problems I’ve seen in OSM data. The only preprocessing W2XP does on road data is to try and fix some bridges and doubled up nodes. W2XP simply puts whatever data you give it into the sim, so if the road data in OSM is naff, then it will be given as it was to X-Plane. But I also don’t know how we can guarantee X-plane’s stability when this kind of unmetered low level access to the rendering engine is provided. We’ve always tried to keep the scenery system open, and I think it’s fantastic to see third party developers doing things that we’ve never done with X-Plane. I’m not sure what the long term fix to this is, but it did make me question our scenery strategy. Even with this, I can’t guarantee that there isn’t some OSM data out there, when dumped directly into the simulator, that won’t crash. You’ll see a log warning with w2xp net scenery when this happens telling how many road chains had to be deleted. I’ve gone to the extraordinary step of programming X-Plane to attempt to clean up the road data on DSF load. The problem is that w2xp doesn’t pre-process and sanitize raw OSM data before sending it into the sim the result is that a small number of weird OSM roads are causing a cascade of ever-weirder data in the rendering engine, eventually resulting in a crash. On this last bug: it looks like the w2xp “net” sceneries are responsible for virtually all of the crash on scenery load bugs I’ve seen in beta 5. (This case was getting hit only when the right combination of untextured objects was used.) Black textures and crashes loading airplanes are now fixed.Fix for backward control surfaces (which was intermittent based on what aircraft you had loaded before).Fix for fuel consumption (which was tied to the number of physics cycles you had set).There are some big bug fixes here including a few big ones:

X-Plane 10.50 beta 5 is here – see the release notes for a complete list of bug fixes. If you’re using a supported part of the scenery system now, you can keep doing what you are doing. We are not changing or hiding any file formats. Update: just to clarify, since this post kind of freaked people out: We are not closing off the scenery system. Beta 6 should be out in a day or two addressing both.

Sorry about that! Since the original writing of this it has become clear that only some of the no-texture objects were fixed, and the throttle reversers are borked. Note: beta 5 came out before the long weekend and then I managed to not publish the announcement.

X plane 10.50