Black Shark Freezes on Pad after Launch

[JHzlwd]

I have been running BS on my "System A" for over a year with no problems (patched to 1.01). This system is Win 7 Ultimate, I7-920, 6 GB RAM, Logitech G110 KB, Saitek X52 Pro, ATI 5850. I recently put together a bigger and better "System B" which is Win 7 Professional, I7-2600K, 6 GB RAM, Logitech 510 KB, Saitek X52 Pro, ATI 6970.

 

BS (1.01) was installed on the new System B and *worked perfectly for a couple of days*. Of course I was fine-tuning some things which is likely where the problem happened. Anyway, after that initial period of success the sim is now frozen every time following launch where the helicopter is sitting on the pad and you are asked to click "Pause/Break" to get going. You can click it all you like but nothing happens. There is no sound and the sim is totally unresponsive to *all* KB input. Task Manager cannot kill it but you can clear BS out of the system by logging out of Win 7 which, at least, avoids a complete reset/reboot.

 

I have tried the following:

 

- Changed screen resolution/mode

- Installed 1.02 Patch

- Tried compatibility mode and ensured running as Admin

- Downgraded video options

- Tested trying to fly with no keyboard programming loaded.

- Checked FAQs. There is an item relating to this exact problem having to do with "NewView". I have no idea what NewView is and cannot find any evidence of it on either system.

 

I am convinced I did something after the initial 2 days of success to hang this sim but hours of effort have not determined what it might be. Any suggestions would be most appreciated.

 

Best wishes,

JH

[ZoomBoy27]

does the same thing happen when you fly a mission with a Mid-Air start - Like the Quick Action?

[JHzlwd]

does the same thing happen when you fly a mission with a Mid-Air start - Like the Quick Action?

 

Yes.

[JHzlwd]

Black Shark Can't be Unpaused - Problem Solved

 

The cause and solution to this problem are so obvious it embarrasses me to post this but as I am sure from other messages here and elsewhere that others have been afflicted in the same way, here goes:

 

(1) It is vital to keep in mind there are always TWO profiles active ... one for the keyboard and one for the stick.

 

(2) Before loading a profile you must highlight either the KB column or the stick column (OPTIONS/CONTROLS) and then load an appropriate profile.

 

(3) It is all too easy to highlight the wrong column ... the simulation profiler will happily load a stick profile into the keyboard or vice versa. If you are in a hurry and don't check you might then end up with a bogus KB profile *in which PAUSE/UNPAUSE has been cleared* and therefore inoperative. It's a small design weakness in the sim that it doesn't determine which is which.

 

(4) So, be careful. If you are tweaking profiles a lot it's easy to get caught. I now make a habit when starting up the sim to take a quick look in CONTROLS and ensure everything is OK. If you messed up, just reload your KB profile, then highlight stick column and reload that.

 

It's a good idea to keep backups. I have inadvertently saved a stick profile under same name as KB profile and you then have to work back from the KB defaults which can be tedious if you did a lot of customization.

 

Best wishes,

JH