Error "terminating after critical error. see orbiter.log for details"

[carebear]

i have this problem, when i download a addons and try to launch ex project mercury it gives start to load, and then crashes with the message "terminating after critical error. see orbiter.log for details". what i do when i download is to unzip the folder into the orbiter folder, and then copy the .scn files into the scenarios folder, can any please help me with this issue?

thanks in advance

 

[TSPenguin]

When you install the addon make sure to leave the directory structure intact. If you have to copy scenarios manualy, then you did it wrong.

 

[carebear]

so i shall unzip it into scenarios or just into the orbiter folder?

 

[tblaxland]

so i shall unzip it into scenarios or just into the orbiter folder?

Just into the Orbiter folder, but preserve the directory structure of the zip file.

 

[carebear]

when i just unzip it into the orbiter folder i cant find it in overview of scenarios

 

[TSPenguin]

You have to keep the existing folder structure inside the zip intact when unzipping. There is an option to do so in everything that can unzip.
What are you using? Windows own unzipper? 7zip? WinRAR? something else?

 

[carebear]

using WinRar, i reinstalled orbiter and it worked for some time, but now it gives the same error

 

[dbeachy1]

Errors like this are almost always caused by a buggy add-on (or add-ons). The best way to pin down the problem is via a standard troubleshooting approach:

1. Install a clean instance of Orbiter to a new directory.
2. Bring up Orbiter and test it; it should work.
3. Now install one of your add-ons and test again. If it fails, you've found the buggy add-on.
4. Otherwise, repeat step 3 until the problem occurs.

It is also possible that more than one add-on is causing the CTD, so you have to be careful to install only one add-on at a time and test after each one.

 

[martins]

i have this problem, when i download a addons and try to launch ex project mercury it gives start to load, and then crashes with the message "terminating after critical error. see orbiter.log for details".

Did you actually look into orbiter.log to see if this gives any further clues?