Unable to save settings - English version

[BoneDust]

The "OK" button in the Options screen does not work.

 

Oops posted this twice...sorry. Nonetheless anyone else have this issue

 

Vista 32Bit OS

[BoneDust]

No one else is having this issue?

[BoneDust]

This is a major issue because I cannot setup the game....anyone????

[BoneDust]

Problems with OK button

 

Are none of you guys with the English version having a problem with the "OK" button in the Options screen not working????

[169th_Viking]

OK button works fine here.

[Groove]

I moved your question to the appropriate forums section.

[BoneDust]

So does anyone have and idea why it doesn't work for me?

[Acedy]

And I merged two of your threads about this problem and deleted the 3rd. ;)

 

I don't know what causes this issue, my guess would have been that no write permissions were set or Vista's file virtualization is causing it, but you probably checked that already.

 

Anyway, as a temporary workaround until the solution has been found you can manually edit the options.lua file to adjust your gameplay and graphics/audio settings, just compare the entries with the options screen to find out what is what. The file can be found here: \Eagle Dynamics\Ka-50\BlackShark\data\scripts. Do not use Windows notepad to edit it, but a good editor like Notepad++. In order to map joystick buttons you will have to use your profiling software, the only issue that may remain is if BS assigns the wrong joystick axises.

[Ulrich]

The "OK" button in the Options screen does not work.

 

Oops posted this twice...sorry. Nonetheless anyone else have this issue

 

Vista 32Bit OS

 

Please remove "--console" text from lable properties, clean up your profiles (if they exist) at \Config\Input\Aircrafts, try again and report if it will work after it. We need console text to see what is happening.

[BoneDust]

I'll ckeck options.lua file mate.

Edited December 11, 2008 by BoneDust

[BoneDust]

Please remove "--console" text from lable properties, clean up your profiles (if they exist) at \Config\Input\Aircrafts, try again and report if it will work after it. We need console text to see what is happening.

 

No profiles...removed --console >> still doesn't work.

[BoneDust]

I think I have it sorted. It's a vista issue as usual involving permissions. Even though I am an admin I had to change my users settings too, which make no sense to me since I am an admin. God I hate Vista! :)

[Acedy]

No profiles...removed --console >> still doesn't work.

 

The console is a diagnostics tool to show what's going on under the hood of BS, enabling it does not solve anything. When you enable it by removing the --console parameter a window will appear in the background once you start BS that logs all kinds of actions. To see it and make a screenshot you may have to alt-tab out of the game, or use window mode.

 

I think I have it sorted. It's a vista issue as usual involving permissions. Even though I am an admin I had to change my users settings too, which make no sense to me since I am an admin. God I hate Vista! :)

 

Vista's rights management is different from the one XP used. Even if you are logged into an Admin account you still only have user rights unless you grant yourself or your program admin rights.

[BoneDust]

Here's another stupid question mate. Howcome I am not able to put the

--console back into the target window? Vista keeps saying it's not valid.

[Acedy]

Did you put it behind the last quotes? I get that error if I put it in front of the quotes.

[BoneDust]

Yep...that was the problem. :)

[Raz_Specter]

I also have the same issue, entering into the options I change my deadzone and smoothing curve for my Warthog, click clicking the ok button does absolutly nothing. I can only click cancel.

 

However if I go into the options and change something like, sync my controls with Warhog I am able to click the OK button.

 

Strange one