Case

It shouldn't be too hard to change my Mountain Divide mission for your purposes. It's in rotation on the 51st server. Dooom and Falcon know it already, ask them about it. I think Moby has been asking me about this.

Congratulations! :drink::holiday::drunk::beer::cheer3nc::yay::clap:

If you are flying with wingmen it is easier to be very disciplined in flying combat formations, which makes calling out bandits extremely simple, as with a simple 10km wide spread the BRAA of a bandit will be the same for both pilots. It does not require a waypoint, it does not require switching back to nav mode and it does not require you to do any math during flight. Instead you can just read the BRAA and relay it to your wingman who can apply it instantly, while both can keep focused on the thing that really matters; killing the bandit. The hard part in using this is getting the discipline to fly a combat formation, but once you have this mastered, you'll be loving it.

Congrats!

Congratulations! Have a great day! :holiday::drink::drunk::beer::yay:

Certainly, I couldn't agree with you more. I am just saying that assuming you know the intrinsic strength of sound signals can have significant uncertainties. That is why I am sure real submarines use various methods to get range, the most obvious one would be some sort of triangulation.

As the uncertainties are relative, this is obviously true.

You have to realize that making or maintaining a stats page requires knowledge of programming languages. Even if were to hand over the 51st stats software, you would have to have intimate knowledge of LUA, C, MySQL and PHP to get it running, and be willing to spend time maintaining it. Simply making a stand alone version for clients would not be possible, as they would not have the information necessary to reconstruct what happened in game. This is unfortunately a drawback of the FC2/DCS logging system, as all that information was available in FC1.12. If you want that changed, I suggest you get ED give this a higher priority.

That doesn't matter. The relative uncertainties are the same size...

As with astrophysics, all the uncertainty is in calibrating point 3. Getting absolute sound strengths is probably very hard an may be very dependent on the aspect of the target sub with respect to you. Add in the fact that range goes quadratically and any uncertainty in the absolute strength will dramatically increase the uncertainty in the range. So yes, in principle this is possible, but in practice there will be very many caveats.

Things can certainly be hidden when reviewing the track. I do not know if Lottu makes all the units visible, but my one click replay scripts certainly do. Check them out.

Su-27

Great! Do you have any idea which file was the culprit? The server is usually quiet during European mornings, but people typically start to join around 1500Z and it tends to get busy near 2100Z. I hope to see you there soon. What name are you flying under?

No, not really. If you are unsure if ModMan is installing the right files, I suggest you manually replace your files with the files from the 51st forums. Each file in this thread specifies where it is located. I still suggest you back up your files before replacing them.

Okay, that means another file got changed somehow. The easiest thing to do is to download the modpack from the 51st forums and use ModMan to install it. Since ModMan should keep backups of your original files, you should be able to revert to your previous configuration. With the modpack installed you should technically be able to join the 51st server and some of the other servers.

Indeed. The easiest thing would be to back up config/export/export.lua and replace it by the one in the attachment. If that solves the problem you can use the batch scripts from this post to switch between a Tacview enabled and a Tacview disabled configuration. Export.rar

Uninstalling Tacview may work, but since the export.lua file must be absolutely identical to the one we have on the server. So if after uninstall Tacview it still does not work, grab the export.lua from the 51st forums and place that in config/export.

Did you install Tacview? Having that installed will fail the integrity check. Check this thread on our forums for the modman compatible pack of files that should allow you to join the server. You may want to back up the files and folders listed in that thread.

The miz file is actually a zip file. In it are the mission file (mission), the options file (options) and optional other files. You have to unzip the miz file and then edit the mission. Alternatively, you can open the zip file and set the zip editor to notepad++.

They even work on DCS:BS.

I just want to remind everyone that getting upset over getting teamkilled won't do you or anyone any good. You have to realize that teamkills will happen, be it by accident or intentional, and that they can never be abolished. Only in a very small minority of cases are people teamkilling intentionally, and in those cases they very quickly fall victim to the ServMan autokick feature. Furthermore, all actions in our server are logged on the 51st stats page, so repeat offenders will stand out. I regularly make a mental note of possible repeat offenders and when I catch them doing it again they receive a nice cozy ban. My advice to those that got teamkilled is the following; use game chat to ask the offender if he is aware of what he did, and if not, try to explain to him what he did. Usually you will find that it was indeed a mistake. If they do not respond, then contact a server admin to keep an eye on them, but don't be surprised to find out the offender couldn't understand you because he didn't speak your language. Also realize that it could have happened to anyone else besides you. If you find that someone is firing on you which you know is a friendly, inform them in chat. However, do not feel superior and teamkill him instead. I have no sympathy for seasoned pilots that come and complain to me that they were fired at by a friendly player and thought that the only way to teach him was to teamkill him. You should know better! Instead, my advice is to inform him in chat, BFM him into the ground (to quote Sven), or just let him teamkill you so that his actions are recorded on the stats for everyone to see.

Wow, this is very impressive, especially since the exponent seems to vary so distinctly after certain events happen. This seems to be a cool way to describe progress in a conflict.

Hi Ronin, Friendly fire incidents will always happen. Either because people haven't read the chapter in the manual that discusses IFF or it happens as an accident. Looking at the 11000 air-to-air kills in our server, about 5% of them are teamkills. However, in this specific case you had just taken off from your FARP, so you were still inside your SAM defenses (not sure if you were aware of this). So based on this you could have deduced the fighter could not have been enemy, as otherwise the SAMs would have fired on him. Hence, it was not a good idea to try to gun down this fighter with your cannon, as if you had hit him, you would've gotten the teamkill. Anyway, thanks for flying on the server and for reporting this individual.

Are you not mistaken with a Tor (SA15)?

This does not matter. the SOUND action works regardless if you are in or outside the cockpit. The COALITION SND action obviously only works if you are on that coalition. Crunch is right here. For some reason you can't play a sound from the MISSION START trigger. Instead you have to use something like: ONCE(Play Anthem) // TIME MORE(1) // SOUND(SovNatlAnthem.wav) I tested this and it works flawlessly. I would advise you though to convert the wav file to ogg format, as that is compressed and makes the size of the mission smaller.