Bonkers

Certainly.

Although I'd like to pull, I push. Reason: I also fly RC helicopters so don't want to confuse my aged brain, a fraction of a second's hesitation and I might wipe out a grand's worth of model.

As you are using Vista, if you aren't already, use an affinity utility such as Wombat's DSCAFF to make better use of your quad processor. Also set your option to use fullscreen. There are several threads in this forum on getting the best out of one's system.

Slayer: The reason I copied the Eagle Dynamics folder to the drive root was to facilitate the running of the acmi utility Tacman. For some reason when I run BS from the Program Files folder (NOT as an administrator) the program fails to update various files in the Ka50\temp folder thus causing Tacman not to work. These files are updated if I run BS as an administrator, however I found other issues with running as an administrator with regard to Tacman. Relocating the BS installation solved all these problems for me. Both SP and MP work just fine (when run NOT as an administrator) and Tacman is great for learning where you went wrong and who downed you. However if you want to retain your logbook and campaign progress you have to copy the Players.lua from your original installation after you have run BS for the first time from the new location as the program behaves as if it is being run for the first time ie you have to adjust the settings in Options to your liking. Of course, you have to alter the properties of any shortcuts to reflect the new location. I also use the excellent affinity tool by Wombat, DSCaff, to make better use of my Quad core processor and gain valuable frames. The point I was trying to make to Lionpride was that as an experiment I tried running both SP and MP as an administrator. The SP still worked fine but trying to run the MP resulted in an error message. I thought it must be worth a try, I feel bad when someone can't run this superb sim, knowing what they're missing.

Lionman I am running a similar system, quad cpu, nvidia 8800GTX driver v181.22 (nvidia control panel slider set to Quality), 4Gb ram, under Vista Ultimate 32. I have moved my BS installation to the root of my d: drive. Both BS single player and multi player run fine, however I do not run BS as an administrator. When I tried to run MP as an administrator I got the same response as you ie "Windows cannot find 'bin\stable\DCS.exe'. Make sure you typed the name correctly, and then try again". However SP still runs if I run it as an administrator. I suggest you try running BS not as an administrator.

@ntonis, do any of the keys work? I mean go to Options, Controls then press any key, say "M". Does the display jump to highlight the Action "Master caution push-light"?

DCS homepage and log in using the nickname and password you used when buying the sim (not necessarily the same as your forum password), then Files, Products. You should see your serial no and a download button (plus a buy again button). Hit the download button, I presume you won't be charged again.

Found this in readme1.0.txt: "Q: The sim does not respond to keyboard commands and I cannot un-pause the sim. I’m unable to save and restore my joystick profiles. A: If you are running NewView, this is probably the source of the problem. You need to either Alt-Tab out and back into the sim or rename the NewView folder prior to starting the sim."

I have Vista 32. Try installing to the root of your drive instead of the default Program files folder. Good luck.

Like Congo, I copied my BS installation (the Eagle Dynamics folder) to the root of my d: drive, adjusted the target path in the properties of the desktop shortcut and BS runs fine. The first time you run it from the new location it behaves as if it is being run for the first time, so you will have to set your options to your preferred settings. If you want to preserve your logbook and campaign progress then copy over your Players.lua file from the original \Eagle Dynamics\Ka-50\BlackShark\data\scripts\Logbook folder. Also amend the Start in field in the shortcut properties.

I've had a similar problem. I was messing around with my system, updating drivers. Ran BS and could not call up the Communications menu by pressing \. I had to reassign the key for that Action via Options,Controls - clear the field then Add. I suggest you check via Options the Action (should be Pause) that is called up by pressing the pause/break key.

Hurrah!

Same problem here.

Look for a copy of your original Players.lua (with all your hard earned hours plus any progress in campaigns) in a location similar to this: \Users\Bill\AppData\Local\VirtualStore\Program Files\Eagle Dynamics\Ka-50\BlackShark\data\scripts\Logbook if so, replace the one in \Program Files\Eagle Dynamics\Ka-50\BlackShark\data\scripts\Logbook with this copy. There are other files in the Users Virtual store such as mission files (.miz) To get TrackIR to work as it should, that too has to be run as an administrator. Now I find that Wombat's excellent core tool dscaff no longer works thus losing valuable frames. I have come to the conclusion that the easiest way to have Tacview working with BS is to copy the whole BS installation to a folder outside of Program Files ie right click on the Eagle Dynamics folder within Program Files and copy and paste to the root of your drive. There is then no need to run anything as administrator. Again when you first run BS from this location it starts up as if for the first time. However copy over your Players.lua into logbook, set up your preferred settings via Options and voila all's well again.

Count Sessine Tacview also would not work for me (not writing the *.acmi files in the temp folder) even after following Wombat's and Lobo's advice. My Vista 32 BS installation was in \Program Files. You will need to run the launcher as an administrator. You can do this by navigating to \Program Files\Eagle Dynamics\Ka-50\bin\stable\launcher.exe, right click and select properties, click on Compatablity tag and tick the "Run this program as an administrator" box. The *.acmi file, in addition to LastMissionTrack.trk plus some log files, will now appear in the temp folder after you have exited a mission. If BS is installed in a folder outside of Program Files then this problem does not occur. Hope this helps.