Ornatrix 3dsmax: Installer peculiarity

Hello. I thought of trying the new Ornatrix release under Max 2017 and I came up with a slight problem. The installer identified the various Max installations in the system. In this case, the production one and the Max 2017 trial that I had installed on the same machine. I deselected the production Max and only asked it to install for Max 2017. It did, but before doing that, it uninstalled any previous installations it found, namely the one from the production Max. It was easy to reset it the way it was but the question remains. Why would it do that? They are dfferent installations and it should leave all others alone. I prefer not to switch versions in the middle of projects and still would like to try the new versions in a separate installation. It was easy with the zipped archives (but more work) but I don't see any way to do that with the executable installers. Any chance of tuning te installer to allow that? Thanks.
24 April 2016 #8244
EPHERE	Good question. The way it works right now is that there can be only one version of Ornatrix installed on the computer. If you update to a new version, previous one is uninstalled first as you encountered. I will see if we can do something about this scenario. Marsel Khadiyev (Software Developer, EPHERE Inc.)
26 April 2016 #8260
IvanKolev	An .msi contains a single product. We have built "Ornatrix for 3ds Max" as a single product with a single .msi. The files for the various Max versions are defined as features within the product. When you install a new version of the product, the old version needs to be removed, with all of its features. To achieve isolation by Max version, we'd have to build a separate "Ornatrix for 3ds Max 20xx" product for each Max version, each one contained in its own .msi. I think this would make things more complicated both for us and the users. Ivan Kolev (Software Developer, EPHERE Inc.) E-mail: ivan.kolev at ephere dot com Discord: ikolev

Posted by:		kanenas
Data created:	24 April 2016