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

Installer pain

Messages
226
Country
germany
As you may recognized, I recently released San Pedro de Atacama for both simulators.
I made an installer for it using the ClickTeam Install Creator.
I read in some threads that some people prefer just zipped folders and I wondered why...installers make life so easy mainly for people how are not that familiar with the FS folders structure.
Now I know why...
A few days ago came a problem on the ORBX forums up that FS Central didn't find the FSX folder anymore since the San Pedro de Atacama installation.
The ClickTeam installer changed the FSX registry entry...but WHY?
I searched on some forums on how to let the installer find the correct FS directory.
The problem is that if one want to install the scenery to...lets say a folder on the desktop, the installer changes the FSX registry entry to this direction!
but why...I think because "Update key" was selected by default when creating the installer. I simply didn't know (nor could I imagine!!) that this changes the registry entry when selecting another folder and nowhere was a warning about this. And when you google it, you don't find usefull information about this option.
Wow, thats a real fail. It caused a lot of headache to some guys who couldn't switch back to their ORBX region anymore nor were able to install new sceneries/aircraft.
I'm very sorry about this, I provided a new package which is archive only and built new installers but the scenery was already downloaded 2000 times! Which means 2000 dangerous installers.
What to do now?
Unbelievable that a simple tick on one option caused a lot of damage and bad feelings for me.....:(
And now people may say: Be aware of twentynine palms scenery design.
Fantastic...

Just had to write this down, understand this as a warning.
In every thread in this forum about how to let the Install Creator find the correct directory should be written:
And never, never have "Update key" selected!
 
I have had bad experiences with ClickTeam. My issue was that it cant usually find FS. I have since discovered that some installers change the registry by one symbol or entry making it suddenly invisible to other installers.

That and some WIndows are set to hide Registries and folders, as a self defense against invasion programs.

Lastly, when I buy other payware, it usually will not find my FS installation either, so I dont feel so bad.



Another issue is that when you have files like 'soundgauge.dll' in there, and you have a 'uninstall', if they run it, it will take out things that will cause many other planes to not function properly, so with my own fleet, I have stopped putting in the uninstaller. The customer can easily enough run the Installer into a 'new folder' on Desktop, see the names of the files, and go in and hand delete them. This is far better then their Sim being rendered unflyable by their fave planes.


Bill
 
Installer or no installer is a no win. With ADE we have a group of users who just do not want to use the installer - they want control over where things go. We released our last version first with a non installer zip. It caused trouble.... well it would of course. Now some users emailed me to ask when the installer version would be released so that they could use that - they just could not or would not deal with a manual install. So in the end we provide both. We also provide an automated updater and a manual update file. To be honest from our point of view the installers are less trouble in terms of user problems than a manual install. We had to make a bit note in the manual updater file not to click on the executable. Users will since although it is actually an updated copy of the application a good number thought it was an installer or that the program would somehow run if they double clicked this in the manual update package.

I can go on in the number of ways that it can go wrong but I better stop :)
 
Whats bad to add to that Jon is that many customers and enthusiasts of FS are over 70 and new to computers but they want to fly so bad so they are learning all they can.

So, they buy some planes, or download them, and know nothing about installing them. The installers cannot find the sim and they panic. I have educated many many people on long emails about how to do a manual install with a installer going into a 'new folder' on Desktop.

It helps to tell them that this will be good info on learning as some are manually installed such as freeware, and I tell them that in the early days of FS, we had to create folder systems for the planes we downloaded, lol... Man, that was an eye opener for me, only getting several files in a download and having to create the airplanes folder system. ackk...!


So much to learn, teach, help, etc...
 
With ADE we have a group of users who just do not want to use the installer - they want control over where things go.

You have described me to a T. How far will I go to avoid an installer messing with my FSX folder? I rename my original FSX folder, create a dummy FSX folder to look like my original FSX folder, run the installer, then go through the renaming process in reverse. You can use a program like Regshot to take a before and after snapshot of your registry to see if the installer made any changes to that.
 
For you we provide a manual installer :)
 
Thanks for your comments guys!
This helps me regarding future projects.
I'll provide two versions, installer + archive because I can imagine that some people didn't download SCPE because its installer only.
And the example in the first post shows what it can wreak...

btw. I recently provided an archive-version of SCPE for FSX on my website ;)
 
It is a pain to have to maintain archive and installer versions and remember to keep them in sync but it is worth it in my option :)
 
What seemed to worked best for us was we did create a installer (install was something like 500MB), but we explained in the User's Manual a complete step-by-step what was happening. They could then decide to install automatically or install to a dummy/temp folder and then move things over manually if they wished.

I think the thing is keep the simmer informed on what you plan to install/how/where and they won't feel so wary. That gave us the least amount of support issues after we did that.

Personally, I install in a temp folder if I am not familiar with the company and/or make a restore point.

Clutch
 
I purchased the Professional version of WIN 7 solely for its ability to run XP as a virtual computer. I had been installing programs to a temp folder but then realized that that that did not prevent an automatic installer from messing with the registry or menus. Or locating an uninstaller wherever it liked.
Some installers won't work unless they find a valid copy of FSX installed but these are the programs that could cause problems so I don't see it as a negative.

Jim F.
 
I know that a lot of folks swear by the "Clickteam" installer program, and some have even licensed the "commercial" version. But it seems to me that in both cases the actual instructions for using the program are incomplete and occasionally quite vague.

Several years ago I discovered NSIS* (Nullsoft Scriptable Install System), which is a well-established Open Source program. What was most surprising though, was discovering that quite a few well-known commercial software publishers have been using NSIS for years! Companies such as Google, Adobe and McAfee, to name just a few...

There are also many, many freeware overlays for NSIS, which provide anything from a basic GUI to an advanced GUI for creating custom installer scripts. The one I've chosen to use is called "HM NIS Edit."***

What I've discovered however is that I only needed to use the "script generator" once. Now I simply use the "Editor" function to re-configure the actual folders/files to be included in a new installer package. Everything else can remain the same.

Of particular interest is that not one single time has an installer created by NSIS failed to find the FS9 and/or FSX Registry entries, or if the Registry entries were somehow FUBARED, found FS9 and/or FSX via a search of the user's computer. :D

For whatever it's worth, I don't bother creating an "uninstaller" either, although I could easily do so and only remove specific files, leaving (possibily) common files such as Gaugesound.dll in place.

I would not be the least bit surprised if the basis of the "Clickteam" installer was found to be NSIS.

* http://nsis.sourceforge.net/Main_Page
** http://en.wikipedia.org/wiki/Nullsoft_Scriptable_Install_System
*** http://hmne.sourceforge.net/index.php
 
Last edited:
"I don't trust any installer not to mess up my system."
I agree with George.
I prefer to mess up things myself:), that way, at least, I know it is my own fault and it will probably not have affected my registry.
I always put my downloads in a temp file when it comes with an installer or an .exe and read the readme.
 
@ robystar:

Then better don't do that with my installer ;)

@ Bill:

Thanks for the information concerning NSIS, I'm gonna take a look at it!

...

Now I know how much attention one should pay on how to release his work. At least beta-test the installer as much as the scenery itself because a simple fault in it can devaluate all the work you've done over months on developing the scenery because it damages the users registry....
 
Now I know how much attention one should pay on how to release his work. At least beta-test the installer as much as the scenery itself because a simple fault in it can devaluate all the work you've done over months on developing the scenery because it damages the users registry....

I throughly test all of my installers on a "virgin system" I maintain just for that purpose. After each test I run a restore on it to "reset back" to "virgin" status.
 
I am making some scenery airfields which for the first time will be "Payware" and there will be No installers.....a simple Zip and complete instructions in English and Spanish on how to install the files.
 
This thread does give the impression that a lot of users don't like installers, but really I think this applies more to developers, who know what can go wrong! These days I try and build an installer which does everything with the least amount of effort from the user. Pre-purchase emails asking how easy it is to install my scenery are very common.

But I can appreciate how much damage a faulty installer can cause, mainly to your reputation. My testers are very useful here, and testing the installer can't be rushed.

I love NSIS because I can actually see the script line by line, so I feel like I have total control over the result. But since I'm not a natural coder, it can take me a while to build a new feature. At the moment I'm working on an installer which will allow an installation to both FSX and Prepar3D, depending on what it finds installed. This is different enough to cause a few headaches, and my lack of programming knowledge does mean that my first efforts generally don't account for all the issues which might crop up. But I'll get there, and once I do I know that I'll have a useful script that can be reused when I need it.
 
You will only need to create a dialog, then allow the user to fork to the correct Registry path lookup:

InstallDirRegKey HKLM "Software\Microsoft\Microsoft Games\flight simulator\10.0" SetupPath

-or-

InstallDirRegKey HKLM "Software\Wow6432Node\LockheedMartin\Prepar3D" SetupPath
 
You will only need to create a dialog, then allow the user to fork to the correct Registry path lookup:

InstallDirRegKey HKLM "Software\Microsoft\Microsoft Games\flight simulator\10.0" SetupPath

-or-

InstallDirRegKey HKLM "Software\Wow6432Node\LockheedMartin\Prepar3D" SetupPath

Yes, the selection is easy enough, it's just things like version checking, uninstalling and adding the scenery to the Scenery.cfg which need some thought.

By the way, from the Prepar3D SDK:

Prepar3D's registry key information depends on whether or not you are running a x64 bit or x32 bit Windows machine.

Registry information for computers using a 32-bit architecture is here:

>HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D

For computers using a 64-bit architecture the registry key information for the 32 bit Prepar3D application is here:
>HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LockheedMartin\Prepar3D

Two places to look, adds to the fun...

EDIT: I did discover NSIS Dialog Designer recently, and I will need to go back a press the 'donate' button, since it does most of the work.
 
Last edited:
Back
Top