SceneryDesign.org
I have just put a release candidate of the Autogen Configuration Merger tool on the FSDeveloper forum. So if you are interested please test this version as well, hopefully there are no more bugs and a formal release will be there soon.
All details are in the forum post, but basically all I need to finish are the manuals. The last version has an installation mode that will make sure the tool gets properly installed.
The last year has been very busy, with the moving to a new house, the renovation of that house and the birth of our second child. But even now that things have become a bit more normal again, I still notice that I have much less time than before.
A few weeks ago our oldest child was staying with my parents for a few days, and suddenly we noticed how much easier it was with only one child at home. There was suddenly a lot more time in the evenings to spend on hobbies and other things.
So it’s just a fact that I’m quite short on time for my flightsim hobbies most of the time. In a typical week I can sit down 2 or 3 times behind my FS development PC for maybe an hour or so (that’s the amount of time I would spend on the hobby per evening before). Luckily I can read the forums from my smartphone as well.
So quite often I think fixing this bug or adding this feature shouldn’t be that much work, I’ll have it done in a few days. But when it’s finally done a month has passed again most of the time. So development is going a bit slower than I would want sometimes and there isn’t always the time to work on the ideas I have in my mind.
Let me be clear, I’m not complaining about this situation. Because I do also enjoy the new activities that I now (have to) do in the time I could spend on flightsim before. It’s great fun to spend time with the children and see how they develop. I just wanted to share this with you, so that you understand better why things sometimes go a bit slower. And hopefully when the children are a bit older, there will be more hobby time again…
I guess nobody has missed that Microsoft released Windows 10 recently. I have upgraded my development laptop as well and things seem to be running fine. Until now I haven’t encountered conversion issues with any of my tools yet, they all seem to be working fine.
ModelConverterX uses OpenGL, so make sure you have the latest Windows 10 driver for your graphics card installed, but that’s the only feedback I got from some users.
So upgrading to Windows 10 seems save, from my tools point of view. I also haven’t had trouble with running FSX (Steam Edition) and the other development tool I often use. But of course I’m not running the tools of a typical flightsimmer, so don’t base your decision to upgrade as well only on my advice 😉
I have added some extra functionality to the hierarchy viewer of ModelConverterX in the last two days. This feature to allow filtering in all the nodes was on the wishlist for quite a while already and since I needed it to debug an issue I have now finally added it.
The filtering can be done in two ways. First there is the checkbox in the toolbar to only show nodes of the active LOD. When this checkbox is off, all nodes of the model are shown. When it is selected only the nodes of the currently shown LOD in the preview are shown. So if you are looking for issues in a specific LOD this will help to narrow down the amount of nodes to check.
The second way to filter the nodes is even more powerful and that is the search box that you can now also find in the toolbar. If you type any text in this search box only nodes will be shown that match this text. The search is done in material names, animation names, visibility condition names and mouse rectangle names. The picture below shows the default Cessna 172 model where only the rudder parts of the active LOD are shown.
If you clear the search text after you have found the right node, that node will still be selected in the total scenegraph, so that should make it easier to evaluate the parent and child nodes of that specific node.
The isolate button at the toolbar is also new and it will isolate the selected node. What this means is that it will make the selected node the new root node of the model and prune all other nodes. This can be quite destructive so use with care.
I have just released the first beta version of the new Autogen Configuration Merger tool. I would like to encourage other scenery developers to test this tool and let me know how it works for you. For more details, please see this post on FSDeveloper.
My new tool Autogen Configuration Merger is almost ready. I hope to have a beta version that other developers can test soon. In the mean time I have setup a forum at FSDeveloper now to discuss this tool and I have already put some questions there for topics I need some guidance on to finish the tool.
I have changed the way the autogen configurations are read into scenProc. From tomorrow the development release will use the Flight Toolkit SimProp library to read the autogen configurations, instead of using spb2xml in the background to decompile to XML.
This change should not really be noticeable, since the new approach should return the same information for the auto completion. While switching to the new library I have also improved the way the autogen configuration is read a bit, so it should be even more stable. But if you notice any issues with the development release, just let me know.
Now that the stable release of scenProc is out, I can finally put some changes I have been working on in the past weeks in the development release. So here is a quick update of the things that I have added today:
Especially the changes in the second bullet can mean that you old script doesn’t work as before anymore. So be careful to check your script when updating to this release.
It’s party time! The release of the first stable version of scenProc is there, I have just put scenProc 1.0 online.
Obviously it’s based on the latest development release, if you download the stable release now you will notice the main difference is the completed manual.
Now that I have a stable release out, I can go ahead and implement some of the changes I have planned for scenProc. These will change how certain things work and might give some discussion initially, but that’s why I think it’s good to have a stable release to fall back to in case of emergency.
So let’s celebrate this release now and from tomorrow I’ll continue to improve this tool in the 1.1 development release.
About a week ago I changed the default behaviour of scenProc. Before the configuration file was saved automatically every time you run it, but some users complained that this was not what they expected. Since I agreed it was not very “nice” to automatically save on each run, I changed the behaviour to only save when the save button was pressed.
All sounds fine so far, but since this change I noticed that I often lost changes I wanted to save, because I forgot to press the save button. So today I decided to add a warning when there are unsaved changes when you quit or try to load another document. The message will just ask you if you want to save before continuing or not. So hopefully this will minimize lost edits.
And to make clear there are unsaved changes I do now also display the asterisk behind the filename in the window tile when there are unsaved changes.