Jump to content

Recommended Posts

Posted

Hey madmax59,

 

I take it multiplayer starts and single play gives you grief?

 

Even after deactivation and reactivation no luck?

 

Mate I've tried everything and the only way to enjoy BS is use your old card:joystick:

 

I downloaded my copy and the first install was sweet, I can't understand how changing a graphics card could cause any issues.

 

If it was the card it wouldn't start in multiplayer mode either, it has to be BS related.

MoBo Asus TUF X570-Plus (Wi-Fi) / CPU AMD Ryzen 9 5900X / GPU Asus TUF RTX3080 / RAM 32GB Corsair Vengeance RGB Pro DDR4 @ 3600MHz / V-NAND SSD 1TB Samsung 970 EVO NVMe M.2 / PSU Corsair RM750 / CPU Cooler Corsair H100i Platinum / OS Win 10 :pilotfly: 

Posted (edited)

I've just updated the drivers on my 4870 to Catalyst 9.1 and now I'm getting the same problem :(

 

Edit: Disabling the Catalyst AI fixed the problem

Edited by Highwayman-Ed

Intel i9-9900KF @5.2GHz

MSI Z390 Gaming Pro Carbon

32GB G.Skill Trident Z DDR3200 RAM

MSI RTX 2080 Ti Gaming X Trio

40" Panasonic TH-40DX600U @ 4K

Pimax Vision 8K Plus / Oculus Rift CV1 / HTC Vive

Gametrix JetSeat with SimShaker

Windows 10 64 Bit Home Edition

 

[sIGPIC][/sIGPIC]

Posted

Tried the "final" solution: format c:, new fresh windows XP instalation, newest nvidia driver and nothing else. BS initial menu now appears, my 8800 GTX works!

I'll try to find out when during the installation of the other applications, drivers, etc, BS will run no more again..

  • 3 months later...
Posted
Tried the "final" solution: format c:, new fresh windows XP instalation, newest nvidia driver and nothing else. BS initial menu now appears, my 8800 GTX works!

I'll try to find out when during the installation of the other applications, drivers, etc, BS will run no more again..

 

Yep, it is very likely that this bug is related to another software. I remember having some similar issue with Flamming Cliffs... I couldn't launch, and after a format c: and a re-install, it appeared that a codec pack was the issue.

 

By the way, since Zakk mentions a possible workaround by forcing fullscreen, here's a way to force fullscreen display in the config files:

 

Do a backup and edit the following file: .\Ka-50\BlackShark\data\scripts\options.lua. At line 62, you can see the following:

 

        ["fullScreen"] = false,

 

Change this to:

 

        ["fullScreen"] = true,

 

and it will force fullscreen display. Bear in mind that it's best to edit config files with an advanced text editor (such as Notepad++ for instance), so make a backup copy, just in case ;)

 

Please report any improvement by using this workaround, this might help other users with a similar problem.

 

Thanks :)

sigpic55586_3.gif

icone_Ka-50.png In Mud I Trust. icone_Su-25.png

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...