SceneryDesign.org
I have finished updating the algorithm of scenProc to replace building polygons by multiple rectangles. From the tests I have done for the Nantucket area I am quite pleased with the results.
I just spend most of tonight to type in the manual how the algorithm works, so I’m not going to repeat that here now. I would say just download the new development release tomorrow and have a good read in the manual.
The last weeks updates of my tools have been a bit slower than usual. On one hand that was because I have been busy with non-FS activities, but also because I have been experimenting a lot with creating autogen for Nantucket with scenProc. It’s useful to sometimes do some actual work with my own tools, that gives a lot of ideas for future improvements.
For ModelConverterX the highest priority new feature is to improve support for aircraft MDL files. But since I’m quite busy with scenProc now, it might take a few months before I will concentrate on ModelConverterX again. In the mean time I do try to fix bugs that are reported, but that also goes a bit slower than usual.
In the last week I have been working on improving the scenProc algorithm to split complex building footprints in multiple rectangles. I’m almost done with this update, I only need to implement one last improvement that I have in my mind now. After that I will have to update the documentation so that it is clear how to use this improved step.
I had hoped to finish this scenProc improvement by this weekend, but last week I had less time than expected. Next week we’ll go on vacation, so it might be I will only be able to finish it after that. So in that case you would have to wait a few more weeks…
I got some error reports about the scenProc IMPORTOGR step. Sometimes it would throw an error that interleaved reading mode should be used. This mainly happened on bigger, more complex files. But when working on my Nantucket test area I also noticed that reading with certain required attributes stalled and got in some kind of endless loop.
I have now fixed both of these problems. So in the next development release it should be easier to use OpenStreetMap data in scenProc.
In the next development release of scenProc some options are gone from the global options form of the tool. But I have not removed them, I have just moved them to the configuration file. That way it is easier to enter different values for these options for different projects (especially when using batch mode).
So which options are affected by this?
I have just fixed some bugs in the scenProc detect feature step. With these fixes the holes in the detected features should now be processed correctly. Before the holes where not always represented correctly.
Be aware that processing holes in features does take more processing time. So you might see that detecting the features takes longer if you have processing of holes enabled.
When I updated my tools to be Prepar3D v2 compliant there was one tool that I forgot, RADItor. RADItor is a small tool that is mainly used by aircraft developers to edit the radius and bounding box values of a MDL file. Sometimes these values need to be tuned for the aircraft to display correctly in the aircraft selection window for example.
I have now made a new version of RADItor that can edit P3D v2 MDL files as well, besides FSX MDL files. You can get the new version from here.
After the recent move of the FSDeveloper site to another server some of the download links to my tools as reported here on the tools pages were broken. I have now fixed them all.
All of the files are now hosted on this website directly, so you browse all old stable releases in one place if you want.
Today I have finally deprecated most of the pre-OGR importers. So that means that IMPORTSHP, IMPORTOSM and IMPORTKML are no longer available in scenProc as steps. You have to use IMPORTOGR from now on to read those (and many more formats).
One of the main reasons to deprecate them is to get rid of the dependency on the Microsoft Access database driver, which was used by the shapefile library used by IMPORTSHP. This dependency gave a lot of crashes, since it seems not everybody read the manual to check what other dirvers need to be installed.
With the switch to OGR this problems should be less. However I am seeing some crashes now from people that are related to the OGR libraries as well. These seem to be caused by wrong .NET framework versions. Make sure you have .NET framework 2.0 and 3.5 installed when using scenProc.
One of the issues with creating autogen is that vegetation polygons might suppress buildings. When the vegetation overlaps the building the building will not be shown. This can be a bit annoying, since you would like the building to suppress the vegetation normally.
To work around this problem I have added a new step to scenProc. With this step you can subtract features from each other. So this allows you to subtract the buildings from the vegetation polygons. That way both of them will show up correctly in the autogen. As you can see on the picture the step also allows you to add a small buffer zone that removes vegetation that is near the building.
The syntax of the step is as shown below. The first argument is the filter to select the polygons you want to subtract from. In this case I’m selecting forest polygons. The second attribute is the filter to select the features that should be subtracted. In this case I select my buildings. The third argument is the scaling that should be applied to the features that are subtracted. So in this case I double their size to get a buffer area. The last argument is optional. If you provide MINAREAPOLY there the algorithm will subtract the minimum area polygon of the feature (the best fitting rectangle), instead of the feature itself. For buildings that is often what you want, since the autogen buildings are created from this minimum area polygon as well.
SUBTRACTFEATURES|type=forest|type=building|2.0|MINAREAPOLY
From now on you will find a PDF manual inside the scenProc downloads. At the moment not all sections of the manual are finished, but I will try to complete it as soon as possible.
With all the recent changes to scenProc and with some of the functions being quite complex, I think it is important to have an up to date manual with the tool. I will for example describe in detail how the feature detection works.
This PDF manual will replace the manual on the wiki. I generate it from LaTeX source code that I keep together with the scenProc source code. So I’ll try to directly update the manual when I make some changes. That way you should always find up to date information.