Nothing happens when I start program.

[MrAnalogy]

Looking forward to playing.
I tried it on my laptop and it worked fine.

Installed the 64b version on my Windows 7 (64b) desktop fine.
But... when I double click on it...nothing happens.

My user account is an Administrator.
I also set OO to run as Admin
I restarted PC. No love.
I installed 32 bit version. No love.
(I'll try restarting PC later but doubt that'll help as it did not suggest a restart was needed)

any suggestions?


Contents of Latest.log

Opening log for Oolite version 1.84 (x86-64) under Windows 6.1.7601 Service Pack 1 64-bit at 2016-09-20 17:56:45 -0400.
4 processors detected.
Build options: OpenAL, new planets.

Note that the contents of the log file can be adjusted by editing logcontrol.plist.

17:56:45.444 [dataCache.notFound]: No data cache found, starting from scratch.
17:56:45.553 [display.mode.list.native]: Windows native resolution detected: 1499 x 843

[another_commander]

Hi MrAnalogy

Can you please provide us with the full system specifications of the computer you are attempting to install on? Graphics card and driver versions would be very important. Also, can you check if there is a file named stderr.txt remaining after the crash in the oolite,app folder? If there is, can you post its contents here please?

Also, that log you posted, is that the entire log? It seems that it stops at an unusual moment, right before reporting joystick and graphics detection. If there is more, please post everything.

Additionally, if you have any antivirus software running, try disabling it momentarily and see if Oolite runs. I think there have been a couple of cases where an antivirus software was actively blocking the program from starting. Can't find the threads that were discussing this right now but it may be worth a try.

Oh and regarding old versions like 1.80 etc (edit: that was a suggestion from another member who removed their post while I was responding): You can try to install that if you just want to check whether it can run or not, but I would leave the fallback to a previous version solution as the absolute last option. Any version of the game prior to 1.84 is not supported anymore and if you encounter issues with it later on, you will be on your own.

[MrAnalogy]

FYI, I currently have the 32 bit version of OOlite installed. (I tried installing that thinking MAYBE there was a problem running the 64 bit version, although this Win version is 64 bit)

Tried disabling Avast AV for 10 minutes, started Oolite, still doesn't start.

Stderr.txt contains only one line:

AL lib: (EE) alc_cleanup: 1 device not closed

Latest.log contains only about 7 lines:

Opening log for Oolite version 1.84 (x86-32) under Windows 6.1.7601 Service Pack 1 64-bit at 2016-09-25 21:03:42 -0400.
4 processors detected.
Build options: OpenAL, new planets.

Note that the contents of the log file can be adjusted by editing logcontrol.plist.

21:03:42.062 [dataCache.notFound]: No data cache found, starting from scratch.
21:03:42.127 [display.mode.list.native]: Windows native resolution detected: 1920 x 1080

System:

Windows 7 Pro, 64 bit
16 GB RAM
Direct X 11
3 displays, running from 2 Video cards:
Built in Intel HD Graphics
ATI Radeon HD 3400 Series

Any other suggestions?

[another_commander]

You can try the following:
- Run the game from Start->Run and add the -nosplash parameter. I seem to recall some Radeon HDs having problems if this parameter was not provided. This is also the quickest and easiest check you can do.
- Just to see if it's getting confused with the presence of multiple video cards, is it possible to disable one of them and try to run it using only one active?
- Check the configuration options of the Radeon and try to see if there are any named Thread Optimization or Multithread Optimizations or similar (I think it will be on the Advanced tab). If such an option exists and is active, disable it.

Just to be sure about Avast, you run the game while this was disabled, right?

The position in the log where everything stops is quite unusual. I also note that in the second log it recognized a native resolution of 1920 x 1080, while on the first one it finds a (very uncommon) 1499 x 843. This, together with the fact that it fails to report graphics card status, seems to indicate that it chokes most likely at some point during SDL initialization. Or a third party memory resident program is interfering. Tricky case this one, but hopefully one of the above suggestions will work for you.

If all else fails, you can try opening <OoliteInstallDir>\oolite.app\Resources\Config\logcontrol.plist in Wordpad (not Notepad), find this section:

Code: Select all

display.context.create.failed			= $error;
display.mode.found						= no;
display.mode.found.failed				= $error;
display.mode.list						= no;
display.mode.list.none					= $error;
display.mode.list.native				= yes;
display.mode.list.native.failed			= $error;
display.mode.switch.failed				= $error;
display.mode.unknown					= $error;
display.initGL							= no;

and change all no to yes, then run the game again and post the log here.

[Cody]

Check the configuration options of the Radeon and try to see if there are any named Thread Optimization or Multithread Optimizations or similar (I think it will be on the Advanced tab). If such an option exists and is active, disable it.

When I had an ATI Radeon card (HD 3600), I had to disable the Catalyst AI for Oolite - try that too.

[MrAnalogy]

That allowed it to start. Seems to be working OK.
Do I need to do anything else ?

You can try the following:
- Run the game from Start->Run and add the -nosplash parameter. I seem to recall some Radeon HDs having problems if this parameter was not provided. This is also the quickest and easiest check you can do.

[another_commander]

If it starts and runs OK already, I guess the only thing left to do is enjoy the game.

[Cody]

Talking of the splashscreen, why a .bmp and a .png? Which one is used?

[another_commander]

Talking of the splashscreen, why a .bmp and a .png? Which one is used?

For Windows and Linux it's the bmp. Mac not sure, maybe the png. The reason we use bmp is that, when the splash screen launches, png reading is not set up yet so we need to use whatever SDL can read by default.

[Cody]

<nods> I'm using my own splashscreen, but the conversion from .png to .bmp ain't looking quite right.
I'm probably doing something wrong in GIMP though, so I'll keep trying.

[Cody]

<scratches head> I have my chosen image, converted to .bmp, and Oolite displays it perfectly. When I add text to that image, it looks fine in the Images folder, but Oolite doesn't display the text, and the image appears as if in UV or something. Rather strange. I can't obtain a pic, as the screen dump only returns a black screen.

[another_commander]

Can you upload the bmp somewhere? I can try embedding some text in it just to see if and how it works.

[Cody]

Here! It's probably something I'm doing wrong in GIMP - but I've done this before with no such problems.

[another_commander]

And here it is back, with some text added. Seems to work OK here. Is there a specific text and format you would like to use? If you still have problems creating that I could give it a go and try to make it here.

[Cody]

Damn it, that displays perfectly! Back to the drawing board!
Does this image (text added) display okay on your machine?


Oops - wrong link at first!