Launcher.EXE problems

[Dougie]

Hi, whenever I click the single player launcher.exe, the game fails to load and I get an error message

 

"Launcher.exe has a problem and needs to close"

 

With the usual send error message option to microsoft or don't.

 

I don't know why it is doing this, and I only just bought it today so it is annoying me quite a bit.

 

The multiplayer loads fine though...:helpsmilie:

 

Cheers, Dougie

[EtherealN]

There's a sticky here named "help us help you", that lists some information that would help us assist you.

 

First of all, we would need to know what your computer specification is - CPU, RAM, Graphics Card, Operating System, versions of related drivers and such.

 

Also, please inspect the Temp folder within your Black Shark installation and see if you can find the Error.log and Errors.log, and any crash logs. Please upload or copy-paste those here.

 

My guess would be that it's GPU-related, and something to do with the OpenGL drivers. If you are using an ATI/AMD card, you could disable Catalyst AI just to eliminate that as a cause.

[Dougie]

Specs, not very good but runs BS fine for me....

 

2.8Ghz Pent D

ATI X1550

2GB RAM

 

 

 

I always have catalyst turned off.

 

Only thing that came up in any "Error/errors" text document was this

"2009/10/27 23:06"

 

And there is no CRASH document.

 

Cheers, and sorry for not reading that post first time!

[EtherealN]

Which version of the driver suite do you have for the graphics card?

 

I would suggest trying the 8.12 version, which has proven to solve that very same issue on the sibling card x1950.

Edited October 28, 2009 by EtherealN

[Dougie]

I don't think I have updated the drivers for my ATI card in a long time. Although I will install that driver and get back to you.

[EtherealN]

Thing is, windows might have done so for you without asking you about it, and AMD/ATI have been a bit over-enthusiastic in rating which driver versions support which cards. F.ex, 9.3 driver supposedly has full support for the x1950, but the OpenGL part (which launcher.exe uses) only consistently works on the 8.12 as the latest as far as I have seen on this section.

[Dougie]

Version 8.12 does not work, hrmmm...I tihnk I will try using the latest ones and see how that works.

 

It's a shame it doesn't work consistently across the board, but it worked once...so it may work again. Just have a wee bit of troubleshooting to do, and hopefully I get some crash and error reports.!

 

Cheers again, Dougie.

 

______________________________

 

 

EDIT: Tried the newest drivers and nothingis happening....urgh this is annoying.

Edited October 28, 2009 by Dougie

[slug88]

You said you only bought the game yesterday. Have you installed installed the latest patch (1.01c) available on this site? I had occasional crashes like that, but it's never happened since I applied the patch.

[Tez]

It's worth to try everything from the FAQ first:

http://forums.eagle.ru/showthread.php?p=676106#post676106

 

Also consider removing installed codec packs.

 

If nothing helps, look if there are any records about the subject in the windows event log? We need a full error text.

Edited October 29, 2009 by Tez

[Dougie]

Slug, yes I have the patch installed. I run 1.01c

The weird thing is that it did work for a few times then it just didn't. This was after the first tutorial...

 

It just seems so weird that it decides not to function now.

 

Could you tell me where to find the windows error log in a text? I cannot find the directory from the error message.

 

Thanks alot,

 

Dougie.

 

------------------------------

EDIT:

Here's another thing. If I use the launcher.exe found in the KA 50/bin/stable directory, the game loads up just to the bit where you see the loading image...then it jsut cancels itself.

Edited October 29, 2009 by Dougie

[EtherealN]

As far as I can see you have not shared information on which operating system you are using, but this is one way you can use for Vista:

 

Start the Control Panel.

Select System and Maintenance

Select "View Problem History" under "Problem Reports and Solutions"

Find Launcher.exe and right-click an error, then select "View problem details"

 

Note that if you are using XP or 7, or have Classic Mode selected for your Control panel, the route may be different. Also (obviously) if your system is not an english version the selections will change accordingly.

[Dougie]

Oh I'm sorry, I didn't think OS was relevant.

 

Well I'm runing XP Media Center Edition

and yes, I am running in classic mode.

English version.

[EtherealN]

OS is always relevant. It's the one central piece of a computer and the software that provides the framework for how all other software on the system interacts with hardware. ;)

 

I don't have an XP machine available right now to find the equivalent route, but check if there is something named "Problem Reports and Solutions" or similar in your control panel.

[Dougie]

Event Type: Information

Event Source: ACEEventLogSource

Event Category: None

Event ID: 0

Date: 29/10/2009

Time: 13:46:10

User: N/A

Computer: ANTHONY-1102433

Description:

0000000003: 2009-10-29 13:46:10:437 Exception <Load>: Could not load file or assembly 'CLI.AIB.TutorialInfoCentre.Tutorial.Dashboard' or one of its dependencies. The system cannot find the file specified.

Exception Called by: ATI.ACE.LOG.Foundation.Services::LoadAssembly processID:02852 threadID:(CCCThreadNew:Dashboard) domainName:(ccc.exe ) assemblyName:(LOG.Foundation, Version=2.0.3309.28601, Culture=neutral, PublicKeyToken=90ba9c70f846762e)

************************************************************************************************************************

 

That help?

[Tez]

It's all about Catalyst drivers. I suggest to clean up traces of old drivers:

http://www.guru3d.com/category/driversweeper/

[Dougie]

Tez, I used that, re-installed 8-12 drivers and repaired my 1.0.1c installation by re-installing the patch....

 

well now the game runs, BUT it turns my screen off.

 

Message I receive is "No RGB Input"

 

I tihnk it's time to go back to basics and re-install blackshark. It worked straight after the first install, so hopefully this will work.

 

Cross your fingers.

 

Thanks, Dougie.

[Dougie]

Okay. I uninstalled and re-installed Blackshark, and there is no luck.

It loads up but it turns my screen off with the message "RGB no input" followed by the screen turning off with no possibility of turning it back on without rebooting.

:helpsmilie:

 

Dougie.

Edited October 30, 2009 by Dougie

[EtherealN]

The fact that your card ceases it's output to the screen would indicate that you still have a driver-related issue. If your computer has an integrated graphics card on the motherboard you could remove the ATI card and test on that one - it won't play well but it will reinforce the notion that it is indeed the graphics card.

 

And unless the graphics card itself is broken (which I don't think, then stuff like this should really occur irrespective of application and driver version) I would still think it's the drivers that fail to communicate properly. The no RGB input means either that the card ceases to transmit or that it transmit an invalid signal that the screen is unable to accept.

 

You could get Notepad++ and find the file: C:\Games\BlackShark\BlackShark\data\scripts\options.lua

 

(Do NOT use regular windows notepad for that.)

 

In there, locate the following somewhere around line 46

   ["graphics"] = 
   {
       ["multiMonitorSetup"] = "1camera",
       ["color"] = "32",
       ["heatBlr"] = 1,
       ["scenes"] = "high",
       ["water"] = 2,
       ["fullScreen"] = true,
       ["visibRange"] = "High",
       ["aspect"] = 1.6,
       ["textures"] = 2,
       ["shadows"] = 3,
       ["display_mode"] = 
       {

 

The exact values displayed there will of course vary depending on your setup. Change the fullscreen value from true to false. This should prevent it from switching display mode, and while this doesn't really solve the problem it will at least let you verify that everything else works properly. (When it runs in windowed mode it will be forced to follow the screen settings of Windows.)

 

Also, while at it, at line 74 through 77 you have settings for screen size. Verify that those actually fit with what you have on your screen and what your graphics card can output. If they have somehow been set to display something the card or screen cannot accept things like that would indeed happen.

Edited October 30, 2009 by EtherealN

[Dougie]

Okay, trying that now. Will edit my post in about 5 minutes time to show result.

 

I would like to say thank you for all the help, you and Tez. You guys run a tight ship here hehe

 

Dougie.

__________________________________________________

 

(EDIT)

No luck.

My computer did not come with an integrated graphics card, so there is no chance of using that.

Is it possible that changing refresh rate settings and such could affect this? As I did edit some of these settings this morning.

 

Dougie.

Edited October 30, 2009 by Dougie

[EtherealN]

Yes, refresh rate is something some screens are very sensitive to, and an incorrect refresh rate would cause the signal to be rejected. Which screen do you use and what edits did you make?

[Dougie]

Ethereal, I have reset the values back to the default.

And lo-and behold, we have her up and running again.

 

I do have to say getting used to helicopters is extremely tricky and extremely fun.

 

I could never have got there without your help.

 

Thanks a bunch.

 

Dougie.

[EtherealN]

My pleasure. Don't hesitate to call if you need help with anything again, and let me know when you had your first terrifying acquaintance with a Rotor Vortex Ring State. (AKA just falling out of the sky.) :D

[Dougie]

Haha will do... :)

 

You're reputation should be +1 btw.

:thumbup:

 

Dougie