• 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.

Stable vs development release

How many versions of ModelConverterX should there be?

  • One, only the stable release is enough for me.

    Votes: 0 0.0%

  • One, only the development release is enough for me.

    Votes: 0 0.0%

  • Two, it is good to have a stable and a development release.

    Votes: 0 0.0%

  • Other, please specify in a reply to this thread.

    Votes: 0 0.0%
  • Total voters
    0
  • Poll closed .
arno

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,354
Country
netherlands
Hi,

Since a long time there are two versions of ModelConverterX, a stable release and a development release. The idea is that the stable release is more stable (so less bugs). Traditionally this version also has an up to date manual. The development release has the latest features, but might be a bit buggy.

I haven't updated the stable release for a long time, that gives issues with people using the stable release, but expecting features in it that are only in the development release.

So I am now busy with updating the manual with all the changes I made in the last 1.5 year. I am planning to release a stable release 1.3 after that.

But I was just thinking, should we keep those two versions? So that's what this poll is about. Let me know if you think two versions are useful or that you prefer only one. And yes, if we might only have the development release in the future, I will keep the manual more up to date :).
 
I would think on a Lite version and and full version , the lite could be the stable, the last versions are becoming a little heavier when loading, so the first one should be with the basic tools, and so on. But to have two version is good.
 
Hello Arno,

Just between you and the diapers, I always try out the newest developer release, but admit I sometimes have to switch back to an earlier version because of some bugs.
Sometimes I report them and sometimes I do not because I think I am the one that is not doing it coreectly.
In short, keep the two seperate and keep up the good work.

Roby

And as usual:

PS: I have not yet updated to the newest one because the one I use is working OK and the changes are not really relevant for what I am doing with it. Does not mean I will not update at all, but will wait until some more changes will be implemented.
 
Hi Arno,

I tend to agree with what's been said already.

MCX has become a necessary tool. As amazing as those additions are in the development release, I think most will want to know that a stable, 'non-buggy' (although minor), version will always be available.

Thanks!
 
Last edited:
Hi Arno,

I actually haven't used a copy of the stable release for a year or so, and I usually grab the latest dev release every time the pop-up balloon thing tells me there's one available.

I keep an MCX download folder with a "last working version" subfolder inside, and when I download the new version I rotate the previous download (.zip) into the "last working version" folder (overwriting the existing .zip) just in case something may have gotten broken in the new release. Then of course I download the new release and save it to the main MCX download folder.

I keep a working "ModelConverterX" folder where I run the program from, and I have an MCX shortcut pinned to the taskbar from that folder. When I download the latest version I Ctrl+A and delete everything in that folder and then extract the new release .zip file there. This keeps all my settings in MCX intact. If I find a bug that prevents MCX from doing what I need it to do (which I never have) I can restore the previous version from the "last working version" download folder to get the job done.

From my perspective there is no need for the stable release and my vote reflects that. Thanks for this(these) great tool(s) BTW!

Jim
 
In my eyes a stable release only confuses people. Remember how often users had problems and the first answer was this feature is only implemented in the development release, the same with problem reports. Please install the latest development release first.
I keep some history of the development releases so I know I have a stable vesion available. Perhaps it would be a better idea of making some earlier releases still available for download. These versions are probably more useful for most of us.
Jörg

Gesendet von meinem GT-P7501 mit Tapatalk 2
 
Hi

I've voted for 'One, only the development release is enough for me..'

I think this is the best idea because it gives you more scope for users to iron out those pesky bugs. Those who use the 'stable' version may never use the dev version so not only are they missing out on the extra features, you are also missing out on the extra help finding and reporting bugs to advance the program further.

I've never used the stable release

;)
 
I voted for Stable, and Dev release.

Having said that, Arno, your coding is so sound that I find the Dev release is generally all I use and need. :o
 
I have have voted for one, the development release.

Well,.. as Arno pointed out, why not just one where the manual would be more updated. Also, it relieves the burden of people thinking one has the lastest functions. As for the bugs,.. most of the major bugs, I feel, have been fixed.

If I remember correctly, Arno has rewritten the base of MCX to make it more modular, making it more efficienct. Since this has been done, and with most of the kinks out, I feel any bugs left would be new or added functions in the future. Please Correct me if I'm wrong Arno :).

But there is my reasoning behind the one, development release.
 
Thanks for all the feedback. Based on this feedback I will do the following from now on:

  • There will still be two releases, a stable and a development release
  • I will update the stable release more often, version 1.2 was de stable release for 2 years and that is too long. I will now aim to have a new stable release 2 or 3 times a year.
  • Old versions of both the stable and development release will be accesible from the site now, so that means it is easier to try an old version if a new one has some issues.

So, and now that the 1.3 stable release is there, I can put some new buggy features in the development relesae again :mischievo
 
You must log in or register to reply here.
Back
Top