Acedy

Genau genommen GMT+2, wegen der Sommerzeit ;). Ihr habt den gesamten Mittwoch noch Zeit.

OT: make sure that you also read the "Low Level Hell" book, it has been written from the perspective of an OH-6 pilot, i.e. the complementary part in the "hunter-killer" team. http://www.amazon.co.uk/Low-Level-Hell-Scout-Pilot/dp/0891417192/

German speaking squadrons: http://forums.eagle.ru/showthread.php?t=40641 Also check our squadron roster: http://forums.eagle.ru/showthread.php?t=34062

I have already asked c0ff some time ago about adding on_hit() and on_collision() hooks to the networking scripts, see: http://forums.eagle.ru/showpost.php?p=678378&postcount=31 I will also bring this thread to his attention. Regarding the votekick: I don't think there is a way to tell via scripts if a votekick is justified or not. If there was a criterion then the votekick feature would be superfluous, because the server could just kick the player in question automatically. Votes are a means of "player self-organisation", and the idea behind votekicking is that human players should be able to judge all the complex situations/behaviour that cannot be handled easily by automatic scripts. However, votes just enforce the will of the majority of players, so unfortunately they can be abused by a group of people who want to hijack a server. What I could do is to limit the number of votekicks that one can start within a given time period, although this has the sideeffect that players may be unable to initiate a justified votekick. And it will only work against individual players abusing the votekick feature, not against groups. Anyway, if you play alot on Quirk's server maybe you should ask him if he appoints you as subadmin? This feature only works when autokicking for AI and human teamkills is disabled.

Yeah, kicking for high ping is indeed a delicate problem, that's actually the reason why this feature didn't make it into the first version of ServMan. I have been thinking about various algorithms to determine when a player should be kicked, but I am unsure what would be a good solution. As you say it is not a good idea to kick for single high ping events, so you have to measure and evaluate latency over time. And I don't know if it would be helpful to kick a player directly after connecting. The reason is that the scripts receive ping events as soon as the player connected, and the increased network traffic caused by the mission download may negatively affect his ping. I have not tested this, but it is possible that a player's ping is generally higher after connecting than when the mission download is complete and the player starts flying normally. If so it will also affect the ping of all players when the mission is rotated. However, one could easily remedy this problem by measuring ping only when a player is not spectating. I don't know though if an idling specator also affects server performance, but at least a spectator does not have a problem with warping, and you could simply kick a spectator that has been idling too long. Regarding ping measurement over time I have been thinking about two basic approaches: 1. Accumulate ping values over time and calculate some kind of average. There would be an initialization phase where the first values are collected, and after that the average should be continuously compared with the limit. The simplest way would be to sum up all values and divide by the number of measurements, which is easy to do and efficient, but that is not a feasible solution because the more measurements you accumulate, the less influence one value will have on the average. So you want to take only newer values into account, or weigh newer values higher than older ones. 2. The 2nd approach does not calculate an average, it counts high ping events and kicks the player if he exceeded the limit too many times. The algorithm could work like this: on new mission do ping_warning = 0 if X ping values > limit during the last Y seconds then ping_warning++ if ping_warning > Z then kick player The problem will be to find good values for X, Y, and Z. :)

C2D E6850. Yes, it is a factor, but not a sufficient explanation in the cases where performance actually decreased.

Black Shark supports only direct data export via Lua, not C or VB, so the easiest thing would be to create a socket using the Lua Socket library, which sends data to your application via TCP or UDP. It should be no problem to write the application in another language, as long as it interprets the byte-stream/-segments it receives from the socket correctly. There is a tutorial about Lua exporting here, which also includes an example of how to communicate via sockets: http://www.digitalcombatsimulator.com/index.php?end_pos=567&scr=default&lang=en However this contains more or less the same information as the Export.lua file itself. Note that both the file and the tutorial above are not completely up to date anymore, so it's a bit of a trial and error process. For example some of the LoXYZ() exporting functions don't work in Black Shark, and there are a lot more new arguments for the LoSetCommand() function to control the Black Shark and the environment. And here you can find the Lua Socket reference: http://www.tecgraf.puc-rio.br/~diego/professional/luasocket/ What exactly are you trying to do?

A recent quote from c0ff on the subject: http://forums.eagle.ru/showpost.php?p=692054&postcount=10

Systemsteuerung -> Benutzerkonten -> Benutzerkontensteuerung ein- oder ausschalten -> das Häkchen bei "Benutzerkonstensteuerung verwenden ..." rausnehmen und OK drücken -> neustarten. Falls die Installation klappt, solltest Du UAC danach wieder einschalten können.

Versuch bitte mal UAC abzuschalten. Und startest Du den Installer wirklich über das Kontextmenü als Admin? Es genügt nicht, dass Du in Vista als Admin angemeldet bist.

Hi, willkommen im Forum! D.h. der Installer bricht einfach ab bzw. hängt sich auf, ohne Fehlermeldung? An welchem Punkt geschieht das denn genau? Werden schon Daten auf die Festplatte kopiert? Versuch mal den gesamten Inhalt der DVD auf die Festplatte zu kopieren und dann von dort zu installieren. Oder falls Du Zugang zu einem anderen Rechner hast, installiere BS mal dort, nur um zu sehen, ob die DVD in Ordnung ist.

I have made some Fraps benchmarks when I moved from my 7950GT 512MB to the HD4870 1GB. In LOFC the average FPS increased by 18%. The HD is a powerful card for general gaming, but I cannot recommend it if you're mainly into flight sims. In fact LOFC was the only sim I tested where I saw improvements, FSX showed the same FPS like my old card, IL-2 and Falcon even less, and EECH doesn't run at all anymore. Although I didn't it try again yet with newer drivers. :mad:

Did you select AFAC as mission task?

And what data do you base this statement on if I may ask? The general consensus seems to be that Black Shark is one of the most bug free games that has been released lately. Sure there are some issues, like with any other software product, and it's unfortunate for the people who have them, but the team is working on fixing them. The best thing you can do if you have problems is to write a detailed bug report. Running fine here: Intel C2D E6850 3.0 GHz- Gigabyte P35C-DS3R - Palit HD4870 Sonic Dual Ed. 1GB (8.12 drivers) - 4x1GB A-Data Vitesta Extreme 800Mhz - WD Caviar SE16 640GB - 2x Seagate 160GB - BeQuiet Straight Power 550W - Creative SB Audigy 2 ZS - Logitech G11 - Saitek X52 - TrackIR4 + TrackClip - Vista Home Premium SP1 32Bit - WinXP Home SP3 32Bit

There is also: - Lead Pursuit's next project - Third Wire products - X-Plane - Flight Gear (free ware / open source) Besides that don't forget the various modding groups that continue to develop and improve older sims (Lomac, Falcon 4, EECH, BoB2:WoV, IL-2, YAP2 for Wings over Vietnam, Over Flanders Fields for CFS3...). :)

Please read the stickies and file a proper bug report. Without further information it is impossible to help you.

If you or anyone else knows how he managed to get working A2A missiles it would be nice if you could send me an explanation via PM. Maybe there is something I can do for the next ServMan version. What can be done via scripts is to ban somebody as soon as he killed a player with a non-standard weapon.

You can readout client ping from within the scripts, so it is no problem to kick somebody for high ping.

http://forums.eagle.ru/showpost.php?p=620282&postcount=52 ;)

Great work Yoda and team!! :thumbup:

No, but the patch will add S-8OM illumination rockets to the Ka-50's arsenal.

The aircraft has to be tasked as AFAC and (on the Russian side) loaded with SAB-100 canisters. You can then set up normal target zones for "attack" runs.

Then I would guess that the problem is some kind of hardware failure, although it is very weird that you can play single player missions just fine and it only restarts in MP. Judging from your PC specs you either upgraded your PC recently or built a new one from scratch, right? Are you sure that the PSU is strong enough for your configuration? I would estimate that you need at least a good 600W power supply to run your PC under full load. And if you reused an older PSU you have to keep in mind that their power output decreases over time. Did you try other games or graphics/CPU intensive applications? If I were you I would get some stress testing software for your CPU, memory and video card and run each for a while, maybe you can locate and isolate a faulty device.

Sad news, hope they will find the bastard(s) and get the site back up quickly. AVSIM is a great site. :mad:

Hi, welcome to the forums! You probably get a stop error with a blue screen that doesn't show up because Windows is set to reboot once a system crash occurs. Please browse to and change: Start -> Control Panel -> System -> Advanced System Settings -> click "Settings" in the Startup and recovery section -> in the System Failure section remove the tick mark from the "Automatically Restart" option -> click OK Now when the error occurs the next time you will see a blue screen with an error code, the meaning of which you can look up here: http://msdn.microsoft.com/en-us/library/ms789516.aspx