blumenmann

Updated the script. Now new names for the layers. Also added a Layer "new add-ons" where all the sceneries with no default layer apears. So really all sceneries will show up. Maybe that will make it easer to deal with new installed sceneries, when the program can not find a default scenery.

Thank you very much for your feedback. I was never thinking too much about the layer names, but your idea is really good. When I defined the different layers I were thinking not to the user direction. The bug with the missing sceneries is in the queue. I think I there will be another section with new or unsorted sceneries. That makes it easier to handle the new sceneries. Thanks for testing.

Yes this is exactly what I think. But I also think that the ini file in combination with the default airports need another solution. Laminar have choosen the easy and fast way to include default sceneries, but no solution the way sceneries are grouped than. At this point it is not the part of the user to manually sort the ini file. To start a discussion and to give a possible solution I made xpstart. I future xpstart should generate exclusion sceneries automaticly, but that will take a little bit more time. In summer I don't have so much time to program.

Your plugin goes one step back and don't solve conflicts with the default sceneries. The behaviour would be as it was in XP9. When there will be more and more default airports all custom sceneries should start with a letter before "G" that they load after Global Airports ;-)

Here is the short screencast:

Hi everybody, last months I worked a little bit with that tool and a simple gui and it is working now. Some extra nice feature is a small report, when there is more than one scenery to a ICAO. The report opens inside the browser as a html page and it is really usefull, when you have a lot of sceneries installed. Download at: http://lyckade.github.io/xpstart/ Soon I will upload some screencasts at youtube as documentation. Have fun and happy landings Andreas

I did and he just mentioned a gui. And that would be wrong. Because not the user should do that. There has to be a solution for the scenery creator. For this something like layers could be a good way.

I forgot to mention that step 3 of the user process is not implemented yet.

Sorry. It is real complicated for me to write all important points. A good documentation is missing definatly. But let me try to describe the processes in short bullets. Process for the simple user: 1) instead of clicking on the x-plane.exe, a click on xpsatrt.py is done. 2) script runs looks for new installed sceneries orders them and updates the ini file. 3) script starts xplane. Ready Process to a scenery developer: 1) Creating the scenery 2) before publishing next to the library.txt the scenery.txt is added with the information about the optimal layer Ready Nothing else has to be done. I think this feature should be inside xplane. It is not complicated, but it solves the problem with the ini file. At the moment xpstart also has some rules where it can detect a default layer for every scenery without scenery.txt definition. I just want to give a solution where I see a important but missing feature in xplane.

I am working on a small tool which sorts the entries inside the scenery_packs.ini file. I made the tool, because it should show an easy solution for the not so optimal situation like the sceneries are handled. At the moment it is more beta than something else, but I think the results are not so bad. Later that script could be used to start xplane, because the ini update should made before the xp start. For this that script would execute the x-plane.exe (or other file depending on your os). Because of that I gave it the name xpstart. But what is the idea? I defined layers for the sceneries. Every scenery is part of a specific layer and the layer defines where inside the scenery_packs.ini should be ordered. The script analyses the files inside a scenery and decides which layer should be used by default. Inside a scenery the scenery creator can overwrite the default rules inside a textfile called scenery.txt Some more information the download is availiable at: http://lyckade.github.io/xpstart/ To use that script python has to be installed. Also the first run can take some minutes, depending how much sceneries you have installed, but all the indexes are cached so the next time it will just take some seconds. What do you think? Should I work more on that or is it just useless? Would love to get some feedback before I invest more time into it. Greetings Andreas

Oh sorry. Just added a short installation message to the gihub wiki: https://github.com/lyckade/XP_Airports/wiki/Installation But there is no real installation of the script needed. Make sure that you have python (http://www.python.org/) installed on your computer. If you are using a Mac or Linux there should be python. If you have no python installation on your computer download the newest 2.7 version and install it on your system. Run the main.py file with python. Thats it.

Udo Thiel had a great idea and made the great program XAirport: http://www.udo-thiel...grammieren.html I think this tool is so usefull that everyone should have something like that. But XAirport is programed with XCode and is just availiable for Apple devices. So I started to make something similar with python an TKinter. The tool can be downloaded from my blog: http://xplane.lycka....nload.php?id=22 This is just a first beta Version, but it should run with every 2.X Python version. But for the other planed features I need help from some python developers. Following features are planed in future: provide an .exe version for Windows users automatic update of the navigation data a version which runs as a x-plane plugin For colaboration I started a github project: https://github.com/lyckade/XP_Airports So if you have a lot of experience with python and want to help me. Feel free to contact me. Greetings Andreas

Hi Philipp! Thank you very much for that long explanation. That also explains some effects from the Planning Worksheet. I think it is also very interesting how strong the effect of the fuel and the cargo is. Andreas

Thank you for your answer. Yes I know the spreadsheet and I am using it. But my question is different. I try to make an example: If you fill out that Planning Worksheet there is an index calculated for taxi, take off, cruise and landing. This index changes during the flight and that is also the thing I would expect. This index is used by the pilot to calculate the stab trim. This is clear. So the question is do I need to adjust the balance point inside my plane settings (same menue like the fuel settings so I do not mean the stab trim settings)? If yes, there would be the next question: Is the calculated index the same value for the blance point settings? Or index * (-1) = balance point index or something different... The next question would be: When I fly (as real as it gets) do I have to adjust the balance point setting after take off, during cruise and before landing? I ask this, because if I use the correkt stab trim for take off and landing, the balance point must be set correct, too.

Hi everyone, thanks for the great CRJ-200. I love this plane and it is so much fun to fly it. But I have one small question. If my plane is fully loaded not only the weight changes also the balance point, but how do I calculate the correct value for my settings? Is it the index which I calculate on page 4 in the Pilot HandBook or is there another way to calculate the balance point? Or is this done just with adjusting the weight? Thanks for all answers. Greetings Andreas