Leaderboard

Hello guys! Just between two graphs and calculations for the L-410 as a rest, I've started to make Iasi airport, where the HA-LAR crashed on 27th JAN 2005. Some little things needs to cleaned up, but it's ready. It was a really fun to make something different, and before this I can't imagine how easy to make scenery in xplane. This was made in 5(!) hours of non-stop work. Gee, I still can't belive it Used OpenSceneryX and R2 Library for the objects, nothing custom. Release: tomorrow (23. nov 2011)

Hi Simmon, The scenery website is where i'm storing pre made scenery files. You can download files for nearly every place in the world there, the problem is that i didn't updated them since june, and it was made with osm2xp 1.1 so no sploped roofs for exemple, old data etc... So you'd better generate scenery yourself with the latest osm2xp version. I will update the scenery website as soon as posible, but i'm working on a brand new version, so i'm waiting to finish it before regenerating dsf files, here are a few WIP screens: About osm2xp , there's no "team", i'm alone on that project (with beta testers of course!) Maybe when i will make it open source people will want to work on it , maybe to support others flight sims. If someone is interested, a little technical part about how osm2xp works now: Osm2xp 2.0 was made with that in mind, make something modular that just read openStreetMap data and translate it to something readable for another software. Here's a little screen about the workflow and objects used: Parser, Translator and Writer are interfaces, in short they describe behaviors, and you can write objects that implement those "contracts". So right now, if you use osm2xp 2 to generate a dsf scenery from a .pbf file , here's what's going on: The .pbf file is given to a Pbf Parser implementation, which will read the osm data , put it in a more readable form, and send it to the translator. We're working for a dsf output, so the translator is a Dsf Translator, its job is to transform the data the parser sent him to something that will be written in a dsf output. That's where most of the job is done, check if the openStreetMap object that was sent is a building, an object or a forest, compute wich facade will be used, geometry checks to respect xplane facades specification etc... When the translator is done, it sends the transformed data to the writer, in our case a Dsf Writer , that will write this data in a .dsf file (the writer also do other things around the dsf file, like write the header, polygons /objects declarations etc). Now let's imagine i want to add support for let's say flightGear, i just need to write an implentation of Translator and Writer object. Maybe i will also need to change something in the user interface? No problem , as osm2xp is built around eclipse rcp, i can write a new perspective for flighGear (perspective are a set of views and windows, right now there are 2 perspectives in osm2xp , configuration and build, but we can imagine in the future a xplaneConfiguration perspective, and a flightGearPerspective). These well separated layers are also nice to enhance/change what is generated, let's imagine i want to have osm2xp generate sim city like buildings into xplane, you know green/yellow/blue buildings , well i just need to write a new Translator for it, a few lines of code and i'm good. So with all these changes, it's now an open tool to transform OpenStreetMap data to something else, right now xplane, maybe tomorrow flightGear, flight, FarmingSimulator...