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

Which Install Program?

  • Thread starter Thread starter NMG
  • Start date Start date
Ralph Freshour said:
Are you referring to online activation? If so, then no, SimpleInstaller doesn't do that.
Click to expand...

Nope!
Open the spoiler.
Hello guys!
I'm about to finish my first scenery project, and i think that would be nice to have an installer for it. I've tryed to make one with "Advanced Installer", but with no luck, as i don't know how to make it to instal some files in simulator root folder (effects for example), other files, in SODE directory (ProgramData) and finaly, scenery folder to Documents\Prepar3D v4 Add-ons.
I will higly apreciate if some of you will point me to some tutorials in order to achieve what i described above with NSIS. I hope that there is no need to be an programmer to do that. :)

Thank you in advance!!!
 
Hello Mihai,
as you read, I had the same problem. I followed Bill's advice and dug myself into the NSIS installer. It is extremely versatile (can install anything, anywhere) and completely free. Be warned though: it has a steeeeeeeeeeeeep learning curve and is not really intuitive. It takes a while to understand the different modules that are available, but once you got the core process down it's very straight-forward to use. There is a WYSIWYG editor for more elaborate interfaces, make sure to get the Unicode version of the compiler and check out all the samples included.
Just a quick remark, this is my way to get the P3Dv4 path:
Code: 
  Var p3dv4_path
  ;find Prepar3D v4 path:
  ReadRegStr $p3dv4_path HKLM "Software\Lockheed Martin\Prepar3D v4" "SetupPath"
  ${If} $p3dv4_path == ""
    ReadRegStr $p3dv4_path HKCU "Software\Lockheed Martin\Prepar3D v4" "AppPath"
  ${Else}
  ${EndIf}

Cheers,
Vitus
 
Vitus said:
Hello Mihai,
as you read, I had the same problem. I followed Bill's advice and dug myself into the NSIS installer. It is extremely versatile (can install anything, anywhere) and completely free. Be warned though: it has a steeeeeeeeeeeeep learning curve and is not really intuitive. It takes a while to understand the different modules that are available, but once you got the core process down it's very straight-forward to use. There is a WYSIWYG editor for more elaborate interfaces, make sure to get the Unicode version of the compiler and check out all the samples included.
Just a quick remark, this is my way to get the P3Dv4 path:
Code: 
  Var p3dv4_path
  ;find Prepar3D v4 path:
  ReadRegStr $p3dv4_path HKLM "Software\Lockheed Martin\Prepar3D v4" "SetupPath"
  ${If} $p3dv4_path == ""
    ReadRegStr $p3dv4_path HKCU "Software\Lockheed Martin\Prepar3D v4" "AppPath"
  ${Else}
  ${EndIf}

Cheers,
Vitus
Click to expand...

Thank you, @Vitus ! I've opened Tutorials page of NSIS now, so i hope i'll understand the basics, because so far, what you wrote, is just a code for me, that i don't really understand:stirthepo
 
Last edited:
You need to dedicate some serious time to NSIS to grasp it, and I can tell you that you WILL WANT TO SCRATCH OUT YOUR EYES at some point. But I think it's worth it! :eek:
 
FdYIg65.jpg
 
What I've done was to create a "template" NSIS installer script and saved it*. Now I can load the template and just add the additional script to complete the installer. I shared this for other team members to use so that as a company, we have a fairly uniform installer appearance.

*NB: other team members have made some additions and improvements to the original template over the last year or so.
 
You must log in or register to reply here.
Back
Top