Orbiter installation poll

How should the next Orbiter version be installed?

  • Like before, by unpacking a zip file

    Votes: 118 74.7%
  • With a self-extracting exe file

    Votes: 10 6.3%
  • With a dedicated installer/uninstaller

    Votes: 30 19.0%

  • Total voters
    158
I would like to see in the launch pad (or separate) an add-on manager/installer, with install/uninstall features.

I strongly support this notion, plus a self-extractor. The major reason is not because I would have any problems at all handling my stuff manually, it's majorly for looks... The impression will be more professional the less a user has to copy his files around manually. If an installation has to be done manually, a programm is considered "amateur" (in a negtive kind of way) by a vast majority of users, and Orbiter deserves better.
 
I strongly support this notion, plus a self-extractor. The major reason is not because I would have any problems at all handling my stuff manually, it's majorly for looks... The impression will be more professional the less a user has to copy his files around manually. If an installation has to be done manually, a programm is considered "amateur" (in a negtive kind of way) by a vast majority of users, and Orbiter deserves better.

Why not write such a feature for Orbiter 2006P1 already in form of a launch pad extension? The API is there, somebody would just need to get things started.
 
I voted for the current zip method, it works just fine and it's nice for more advanced users to have the guts out in the open from the get-go. That said, I don't think having the option of using an installer would hurt at all, and it would make things easier for newbies, as well as anyone who just wants to quickly set up a functional install without any fuss.

There actually is an Orbiter installer of sorts available [ame="http://www.orbithangar.com/searchid.php?ID=2970"]here[/ame]. AFAIK it just downloads the files and puts them in their place. I use it a lot and I've never had any problems with it. It's nothing really spectacular (it'd be nice if it installed some of the more popular addon's too, shame the author hasn't done anything further with it), but it does take a few steps out of the process of setting up an new install and I imagine it'd make the process a bit easier for newbies.

I'd really like to see an integrated addon manager or some sort, ala Artlav's suggestion. JSGME gets the job done but it has some drawbacks, like having to remove addons that overwrite each other in order and waiting while it physically moves files around. Something that would allow you to quickly enable and disable addons from the launchpad and that keeps them in separate folders instead of overwriting the Orbiter core files would be very nice.
 
Last edited:
I would like to see in the launch pad (or separate) an add-on manager/installer, with install/uninstall features.

Jones Mod Enabler :whistle:

The thing I would add to Jones is the ability to select the zip file via a file dialogue (or d'n'd) and have it automatically unzip it to the MODS folder in Orbiter root. Also, maybe have it (or equivalent) as a tab on the launchpad.

This is wishful thinking however and I don't think I'm clever enough to write such.
 
With a zip file I can restore certain files from an installation, unlike with installer.
I do not like to have registry modified.
But that's me.
 
With a zip file I can restore certain files from an installation, unlike with installer.
I do not like to have registry modified.
But that's me.

Big agreement there. I'm a fan of .ZIP files because I can extract all, some, or a single file from the archive. Its also a generic enough file type that most computers can open (I find .rar, .7z and other less common archives rather annoying b/c I usually have to use a special extractor).
 
I for one want to know what is going where on my hardrive and I want to have a say, keep it the same.
 
I find the Zip file fine... The only problem I hate is when developers create their own installers that require you to manually find the directory, but I'm not going to name any names... anyway i'm a fan of zip/rar files, of course zip files are able to be opened by anybody. well as long as they have a brain stem...
 
Personaly I prefer the ZIP, but a while ago I made an installer with Inno Setup (http://www.jrsoftware.org/isinfo.php) to have one file handy when I want to "addict" collegues and friends.
The configuration file might not be up to date, but I think it still works.
For the ones who like to test it, here it is:

Code:
; -- orbiter.iss --
; Installer for current Orbiter Version.
; (C)2007 'Kuddel' schnepe2 AT gmx DOT de

; SEE THE INNO SETUP DOCUMENTATION FOR DETAILS ON CREATING .ISS SCRIPT FILES!

[Setup]
AppName=Orbiter
AppVerName=Orbiter 2006-P1

AppPublisher=Martin Schweiger
AppPublisherURL=http://orbit.medphys.ucl.ac.uk/orbit.html
AppVersion=2006-P1

DefaultDirName={pf}\Orbiter
DefaultGroupName=Orbiter
UninstallDisplayIcon={app}\Orbiter.exe
ShowLanguageDialog=yes
OutputDir=.
;OutputBaseFilename=Orbiter_060929_Setup

[Components]
Name: "base"; Description: "Base Files"; Types: compact full custom
Name: "sdk"; Description: "SDK Files"; Types: full
Name: "earth_l10"; Description: "Earth Level 10"; Types: full
Name: "moon_l8"; Description: "Moon Level 8"; Types: full

[Tasks]
Name: desktopicon; Description: "Create a &desktop icon"; GroupDescription: "Additional icons:"; Components: base
Name: desktopiconcommon; Description: "For all users"; GroupDescription: "Additional icons:"; Components: base; Flags: exclusive
Name: desktopiconuser; Description: "For the current user only"; GroupDescription: "Additional icons:"; Components: base; Flags: exclusive unchecked
Name: quicklaunchicon; Description: "Create a &Quick Launch icon"; GroupDescription: "Additional icons:"; Components: base; Flags: unchecked

; Just several languages. I think this selection should work well enough.
; Although "en" should be kind of familiar when you want to use Orbiter ;)
[Languages]
Name: "en"; MessagesFile: "compiler:Default.isl"
Name: "de"; MessagesFile: "compiler:Languages\German.isl"
Name: "fr"; MessagesFile: "compiler:Languages\French.isl"
Name: "nl"; MessagesFile: "compiler:Languages\Dutch.isl"
Name: "ru"; MessagesFile: "compiler:Languages\Russian.isl"

[Files]
; --- Base Component ---
Source: "Orbiter.exe"; DestDir: "{app}"; Components: base
Source: "Constell.bin"; DestDir: "{app}"; Components: base
Source: "Constell2.bin"; DestDir: "{app}"; Components: base
Source: "Star.bin"; DestDir: "{app}"; Components: base
Source: "Config/*"; DestDir: "{app}/Config"; Flags: createallsubdirs recursesubdirs; Components: base
Source: "Doc/*"; DestDir: "{app}/Doc"; Flags: createallsubdirs recursesubdirs; Components: base
Source: "Flights/*"; DestDir: "{app}/Flights"; Flags: createallsubdirs recursesubdirs; Components: base
Source: "Html/*"; DestDir: "{app}/Html"; Flags: createallsubdirs recursesubdirs; Components: base
Source: "Images/*"; DestDir: "{app}/Images"; Flags: createallsubdirs recursesubdirs; Components: base
Source: "Meshes/*"; DestDir: "{app}/Meshes"; Flags: createallsubdirs recursesubdirs; Components: base
Source: "Modules/*"; DestDir: "{app}/Modules"; Flags: createallsubdirs recursesubdirs; Components: base
Source: "Scenarios/*"; DestDir: "{app}/Scenarios"; Flags: createallsubdirs recursesubdirs; Components: base
Source: "Textures/*"; DestDir: "{app}/Textures"; Flags: createallsubdirs recursesubdirs; Components: base
Source: "Textures2/Atlantis/*"; DestDir: "{app}/Textures2/Atlantis"; Flags: createallsubdirs recursesubdirs; Components: base
Source: "Textures2/Atlantis/*"; DestDir: "{app}/Textures2/Atlantis"; Flags: createallsubdirs recursesubdirs; Components: base
Source: "Utils/*"; DestDir: "{app}/Utils"; Components: base
; Mark special readme document
Source: "Doc/2006 Edition log.txt"; DestDir: "{app}"; Flags: isreadme; Components: base

; --- SDK Component ---
Source: "Orbitersdk/*"; DestDir: "{app}/Orbitersdk"; Flags: createallsubdirs recursesubdirs; Components: sdk

; --- Earth L10 Component ---
Source: "Textures2/Earth_tile.bin"; DestDir: "{app}/Textures2"; Components: earth_l10
Source: "Textures2/Earth_cloud.tex"; DestDir: "{app}/Textures2"; Components: earth_l10
Source: "Textures2/Earth_tile.tex"; DestDir: "{app}/Textures2"; Components: earth_l10
Source: "Textures2/Earth_tile_lmask.tex"; DestDir: "{app}/Textures2"; Components: earth_l10

; --- Moon L8 Component ---
Source: "Textures2/Moon.tex"; DestDir: "{app}/Textures2"; Components: moon_l8

[Icons]
Name: "{group}\Orbiter"; Filename: "{app}\Orbiter.exe"
The .ISS file should work in a "clean" installation, to compile. Although I wants Moon060504_L8.zip, Earth060504_L10.zip and the SDK installed.

Nevertheless, I vote for ZIP ;)

/Kuddel
 
Last edited:
Why not the two options? install and zip? :huh:

Zipped version doesn't represent a problem for me but for others... I'm not sure at all.
 
I would like to know if the current way of orbiter installation (as a simple zip file) is ok with users,

Honestly sir, if you can't figure out how to extract files from a zip file and double click a .exe file, you should be playing with EvE and the 'Orbit' button instead of your fine product
 
If the new installation will have an effect on addons I would definitely recommend an "exe" file because i can't get any addons I need for the addons I've installed. The Shuttle/747 they all CTD. LLRV = CTD. I really want to use some of these addons but they don't work. For now to practice Shuttle landing I will just have to jettison the ET and SRB's manally during a powered ascent.
 
Back
Top