• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Open Source scenProc

nickhod

nickhod

Messages
1
Country
unitedkingdom
Hi @arno

I wondered if you'd ever considered open sourcing scenProc? I had some ideas for enhancements to the Aerofly tasks, and I'd be happy to have a go at coding those if the code was open.

Specifically, it would be great to have it place non-autogen models where appropriate from OSM data, e.g. pylons, masts, wind turbines, fuel storage tanks etc.

I'd also like to add a GUI front end for scenProc in my AeroScenery tool, where the user can easily select the area they want to download, draw exclusion zones, change options.

I understand if you want to keep it closed source, but thought I'd ask.
Thanks for your work on scenProc for Aerofly so far.
 
Hi,

I have considered to make my tools open source in the past, but in the end I decided not to do so. The current way of developing them as a hobby is what I like.

But I do always consider to extend them.

What would be needed to place non-autogen model in AF2? For FS scenProc has steps to place library objects. If I know how they are placed in AF2 I can probably easily add a similar step for AF2.

About a GUI, I have been thinking about that as well. But to make a user friendly GUI and remain all the flexibility the tool has is hard I think. That's why I never started on it. The flexibility is something I like to keep, so that you can process all kinds of geo data. I also use that in my projects where I use scenProc.

Maybe if you restrict the data to OSM it is easier ot make a GUI. I have been thinking about a user friendly OSM wizard to make autogen before. People just select an area and make a few choices and then the tool will make the autogen with some basic rules. That's probably doable.

What are your ideas on a GUI? Maybe we can combine some ideas. Also, it would be possible to make a separate GUI. As long as it makes the scenProc configuration file as output, the GUI could run scenProc in the background.
 
You must log in or register to reply here.
Back
Top