Acedy

I don't know if there is a switch somewhere, but what you can do is this: most reports are generated by the /Scripts/net/events.lua file. Open it with notepad++ and comment those reports out that you don't want to get anymore. Example: if you don't want to see the "x killed y (with z)." message anymore you would scroll down to the on_kill() function and change it from function on_kill(id, weapon, victim) local whom = unit_property(victim, 15) if whom == "" then whom = unit_type(victim) end if weapon and weapon ~= "" then report("killed %s %q with %s.", id, unit_side(victim), whom, weapon) else report("killed %s %q.", id, unit_side(victim), whom) end end to function on_kill(id, weapon, victim) local whom = unit_property(victim, 15) if whom == "" then whom = unit_type(victim) end if weapon and weapon ~= "" then [b][color=red]--[/color][/b] report("killed %s %q with %s.", id, unit_side(victim), whom, weapon) else [b][color=red]--[/color][/b] report("killed %s %q.", id, unit_side(victim), whom) end end And if you want to disable all messages generated in this file you can change the report() and report_noside() functions from local report = function(msg, id, ...) net.recv_chat(string.format("%s %q "..msg, player_side(id), get_name(id), ...)) end local report_noside = function(msg, id, ...) net.recv_chat(string.format("%q "..msg, get_name(id), ...)) end to local report = function(msg, id, ...) [b][color=red]--[/color][/b] net.recv_chat(string.format("%s %q "..msg, player_side(id), get_name(id), ...)) end local report_noside = function(msg, id, ...) [b][color=red]--[/color][/b] net.recv_chat(string.format("%q "..msg, get_name(id), ...)) end Each player has to do this by himself, since the messages are generated on client side. There are also some server-side reports generated by the server, to delete them you would comment the respective lines out in the /Scripts/net/server.lua file.

Well, it isn't necessarily the pilot who has to do the start-up (like EtherealN said). ;) And there are cases where real pilots would start a mission with all systems already running, like after a hotpit refuel/rearming or when they are on something like 5-minute readiness (in the latter case they also might have set all the switches so that they just need to start the engines before being good to go). So it's not completely unrealistic, although maybe unusual.

Check PM.

Maybe Windows also updated some drivers which cause the problem. Check the update log.

Browse to the folders where they should be located, and look for a "compatibility files" button in Explorer's menu bar. Click on it and you will be redirected to their location. This is a Vista security feature called file/folder virtualization.

Isn't that the company Carl Norman is working for?

Please attach your serverconfig.lua and net-server-<timestamp>.log files here so I can check it myself. Plus try Notepad++ to edit the file, and make sure that you save it in ANSI or UTF-8 without BOM (if you use special characters) format. Also, if you use Vista, check that BS has admin rights and that you/your text editor has write access to the Scripts/net folder (i.e. run it as admin as well), otherwise you may get problems with Vista's file virtualization. The problem are not whitespaces in the code, but in your name that you enter in Black Sharks multiplayer options menu. If you accidentally add a tab or space to your name, Black Shark will not show this ingame, but your actual name and the one specified in the serverconfig.lua file won't match, so ServMan refuses the login. Check how your net-server-<timestamp>.log file shows your name. If it contains lines like: '1. invalid subadmin login attempt from "Ramstein "' (note the tab after your name) then you have to reenter your name in the options menu. The /reinit command has to be enabled for subadmins via the "reinit_by_admin" variable, it is disabled by default.

Fellas, if anybody has problems with the copy protection mechanism he will get help of course, but please no more discussions about Black Shark's copy protection scheme in general, we have had this in the past and everything that needed to be said has already been said. All facts and opinions are well known by now, and you can decide yourself before buying if the protection is acceptable for you or not. Eagle knows that they can't make everybody happy, but that's how it is. Thanks!

No, this is not possible atm, however I have asked Eagle if they could add API functions that notify the scripts when a trigger get's activated or overall mission scores change. This way you could easily implement a phased or branching multiplayer campaign. Personally I think this would be enough, functions to deliberately activate triggers or units aren't necessary IMO, I mean that's what you have the mission editor for. We'll see...

Hey, where exactly did you insert your name and password? It should look like this: [color=red]--[[[/color] [color=red]Format/Example:[/color] [color=red]local subadmins=[/color] [color=red]{[/color] [color=red] ["BartS"] = "Ay!Caramba12",[/color] [color=red] ["name"] = "password"[/color] [color=red]}[/color] [color=red]]][/color] [color=seagreen]local subadmins = [/color] [color=seagreen]{[/color] [color=seagreen] ["Ramstein"] = "YourPasswordHere"[/color] [color=seagreen]}[/color] The upper part (red) with BartS etc. is just an example on how it should look like, if you changed that it won't do anything, because it is just a comment that Lua ignores. You have to insert your info into the green part.

Du kannst in BS auch einen "Pinkie" zuweisen (oder auch mehrere), indem Du den gewünschten Knopf als Modifikator zuweist. :)

That dll is part of direct input, so it could indeed be a problem with your input devices. If you have another keyboard and mouse at hand, please try it with them.

This has nothing to do with the mod, it's a BS message that appears when somebody takes a screenshot. Normally there would also be an on screen message, but I removed it. I don't know why the message was there in the first place, maybe making screenshots causes short stutters.

Lapster, was meinst Du mit "Reaktivierungscode"? Es gibt nur den Deaktivierungscode, den brauchst Du immer, um BS zu reaktivieren, und den Aktivierungscode, den brauchst Du nur, wenn Du BS manuell reaktivieren willst, nicht bei der automatischen Reaktivierung. Wenn Du Dir über die StarForce Webseite eine Aktivierungscode geholt hast (was nur bei manueller Reaktivierung notwending ist), und diesen dann bei der automatischen Reaktivierung statt dem Deaktivierungscode hinter der Seriennummer angegeben hast, war das nicht richtig (siehe Handbuch). Ich weiß nicht, wie StarForce in diesem Fall reagiert. Im übrigen ist es normal, dass bei einer Reaktivierung die Anzahl Deiner Aktivierungen um 1 verringert wird, da sie ja vorher bei der Deaktivierung um 1 erhöht wurde (zumindest wenn Du die Deaktivierung komplett abgeschlossen hast, d.h. wenn die Deaktivierung beim StarForce-Server registriert wurde und Du einen Deaktivierungscode erhalten hast).

Ich hab's selbst nicht ausprobiert, aber ich vermute, dass BS (wie viele andere Spiele auch) nicht unter User-Accounts läuft. Selbst wenn Du in Vista als Admin eingeloggt bist, kann es Probleme geben, weil Du trotzdem nur User-Rechte hast, solange Du Dir nicht für bestimmte Aktionen Admin-Rechte gibst. Dass die Aktivierung erneut ausgelöst wird, kann ich mir nur so erklären, dass der Registry-Schlüssel nur für den Admin-Account angelegt wird. Ich denke Du wirst BS im Admin-Modus starten müssen.

justinjgy, here are the system requirements to run Black Shark: http://forums.eagle.ru/showpost.php?p=603352&postcount=50

little-Dog, lösche mal den ganzen Inhalt des Temp Ordners (nicht den Ordner selbst), und schau, ob das nächste Mal ein Crashlog erzeugt wird.

Please try this: download the file from here: ftp://sourceware.org/pub/pthreads-win32/dll-latest/lib/pthreadGC2.dll and put it into your C:/Windows/System32 directory

Did you put both the setup.exe and Data1.cab files in the same folder?

Lapster, ich habe Deinen Thread mal ins deutsche Forum übergesiedelt, ich denke dann ist das mit der Kommunikation einfacher. 1. Wie in dem anderen Thread, wo Du Deine Probleme bereits geschildert hattest, schon gesagt wurde, musst Du Black Shark nicht deaktivieren, wenn Du es einfach nur deinstallieren und dann direkt wieder neuinstallieren willst. Auch das Hinzufügen eines neuen Joysticks sollte ohne Reaktivierung klappen. 2. Du kannst also Black Shark gar nicht mehr reinstallieren, richtig? Hat die DVD Kratzer? Falls Du ein zweites DVD Laufwerk hast, oder Dir von einem Freund ein externes Laufwerk leihen kannst, würde ich das mal versuchen. Oder kopiere den gesamten Inhalt der DVD auf die Festplatte und installiere Black Shark von dort aus. Das mit der Maus ist auch komisch, wenn Du eine andere Maus hast, benutze die bitte mal statt der MX518, obwohl es daran eigentlich nicht liegen sollte, wenn die Installation vorher geklappt hat.

Hier ist noch ein Test: http://www.splashgames.de/php/rezensionen/rezension/9644/dcs_black_shark

Sometimes red-green-blindness pays off... :D ;) Welcome to the forum Itael, I hope you'll enjoy the Sim!

1. Welcome to the forums, Rjennings! 2. Of course you can ask all your questions here, but please note that you are also supposed to know the forum rules when registering. Rule 4.2 explicitly states that you should use the search function before starting a new thread. ;) 3. You may not like to hear it, but the truth is, if you are interested in mastering the simulation aspect of Black Shark beyond the game mode, you won't get very far with that attitude. I completely understand that you would like to spend your precious time with flying rather than reading, but unlike other genres, reading the manual is an integral part of playing (flight) simulations, especially in the learning phase. Ideally you should place the manual next to your PC and, after making yourself familar with the most important cockpit features, go through the training course step by step, as outlined in chapters 6 and 7 of the manual (+ view the training tracks). Such an organized training procedure will get you up to speed much quicker than by just trying things here and there and without maybe even reading the manual. This takes some time and patience, but it will pay off in the end. :) 4. And while I am at citing rules, may I also remind everybody of no 1.3: discussing moderator actions in public is off limits. If you think a mod made a mistake (although unlikely to happen ;)), please contact him directly via PM. So let's rest this case now, and Rjennings: enjoy your stay!

Peter, as I said in the other thread, please use only one topic to report one and the same problem, otherwise this forum gets cluttered and people are unable to track what others suggested to you, what you tried already to fix the problem etc. So please add your posts only to the thread below, which you created initially, and try the things people suggested there + answer their questions: http://forums.eagle.ru/showthread.php?t=40135 Closed.

Glad that you and your squad like it, that's what I created it for. :)