philstyle

Server updated. - Sl-MoD auto-kick and auto-return to spectator disabled - New mission June 12th Afternoon added - Severe stats links added to server description

Thank for the report. I thought SL-MoD was only doing this for people who sat in cockpit for a long time on the ground without starting etc. Maybe not. I will disable that function.

Thanks ED. It works in multiplayer properly now. Finally industrial areas and ports can be hotted up a bit!

Folks, if your entire DCS is crashing whilst on the server, please post here. Also if it is ONLY happening on SoW server, please also let me know.

SoW is now collecting and displaying player and squadron-based stats. This is still in BETA: Pilot stats are here: http://www.stormofwar.org/?Page=dcs/stats/overview Squadron-based stats accumulation is here: http://www.stormofwar.org/?Page=dcs/stats/squadrons .

This might be possible, and is one of the things we are already looking into.

Yup, that is the solution. The trigger for "searchlight on" needs to reference each searchlight unit so it turns them all on, if there are more than one.

I have the same problem. Has ED or anyone else documented how to use them?

The short answer is no, because the messages are removed deliberately. There are two main reasons for this: 1. It is not realistic in any way for pilots to get in-cockpit notifications when they "score" a victory. There should be an element of fog-of-war about this. The not-knowing if you have destroyed and opponent or not is part of what makes situational awareness important. Furthermore, as the damage model improves there will hopefully be more ways in which pilots can deploy deception when damage in order to convince an enemy that they are done for, when in fact they might be trying to escape from a fight. The "kill messages wold nullify this. If I had my way, I would also disable the in-game score table too. 2. Other players have asked to remove as many messages as possible. I have opted for this approach. As for "X target us being engaged" - SoW also steers away from this. There are simply too many targets and potential targets in our missions to be able to provide the triggers and messages necessary to cater for all of them. Also, SoW encourages ground attack play. Ground attackers, in general, like to be able to get to a target and back undetected. We don't want some artificial game-play generator to destroy their good work. Sneaky, well planned ground attack missions would be nullified if the server announced the arrival/ location of all GA aircraft to everyone. We are, however, looking at implementing a type of automated Radar-Fighter-Direction system for both allies (late war CH) and axis (Freya). This will provide some rough information about possible enemy air activity, but will attempt to emulate the limited accuracy that existed at the time.

Missions updated to v40 - Mission run time extended to 5 hours 45 (to reduce AI load and allow completion of AI missions before new ones begin) - Re-arranged a number of allied spawns in order to increase aircraft availability and to preserve the distinction between USAAF and RAF bases - Re-sorted spawns to correct for new spawn layouts from 2.5.6 patch, and to pre-empt resale of the P47 - Resorted LW spawns and aircraft radios to fix SRS connectivity - Player stats code implemented in all missions and released in BETA (http://www.stormofwar.org/?Page=dcs/stats/overview) - Corrected some aircraft ID codes - Added 602 RAF to Needs Oar Point - Fixed MW50 errors and added more variety to LW aircraft availability - Reworked the de-spawn locations of all AI bombers. These will no longer land (clogging up bases) but will fly to map edge, then de-spawn - SRS to v 1.7.7

Did this get fixed in the end? I am still seeing it

Cheers Grimes, We'll take a look at this over the weeeknd.

SoW server updated and stable. Missions rotation limited to two missions in order to test stability etc.

I would prefer that SL-MoD simply allocated % of a kill to the various actors involved. Based on number of hits, if there isn't a better way. For example: John_Doe was destroyed by AcePilot99 0.65 MrHotShot 0.25 AA_Gun 0.1 Then, we could take those percentages and convert them into our own credit system, assuming each individual victory was recorded, because summing half-scores up makes no sense (i.e. 0.65 + 0.65 does not make sense as 1.3 kills) Alternatively I can give you details on how we’ve done something similar for another sim in the past on SoW (stats table here: http://stormofwar.org/?Page=publicstats) Those stats are based on 3 credit categories as follows: 1. An Aerial Victory – this is when a player/ actor is largely, or solely responsible for a victory 2. Shared victory – this is when two actors split a victory in a relatively even manner 3. Assist - this is when an actor, or a number of actors get minor contributions to a victory Aerial Victory = if the player succeeds in personally taking more than 75% of an enemy aircraft's destruction Shared Victory = if the player succeeds in personally taking at from 40% to 75% of an enemy aircraft's destruction Assist = if the player succeeds in personally taking less than 40% of an enemy aircraft's destruction It is therefore not possible for 2 Aerial victories to be awarded from the same kill It is also no possible for 2 players to be credited with a "share" if someone else is credited with the aerial victory It is not possible for 3 players to be all credited with a "share" for the same kill The math behind how we calculated this still relies on a % breakdown of contributions for each kill though. In the example I gave above both "AcePilot 99" and "Mr HotShot" would be credited with shared victories, whilst "AA_Gun" would be given an assist. So like I said above, it is probably easier to simply provide the raw % contributions to any kill, and then to let the mission maker/ server operator assign credit categories.

OK, so this same issue was reported by the jet crowd three days later and ED responded to it. I guess there's no point posting bugs here. . .

Hi Grimes, My preference would be to go for option 0. As you say, specific users can then tailor the stats to their needs. For SoW we would prefer for Sl-MoD to simply record ALL kills without any scaling or PvE v PvP corrections. Then we can use our own parsing to work out which ones we show, and how we show them.

This is a bug, introduced with patch 2.5.6 This is a bug, introduced with patch 2.5.6 That's exactly what we are going for. An MP environment that also suits people who normally prefer single-player.

Yes, this is correct. Given that this will likely be fixed in an upcoming hotfix/ patch, we are leaving them as cold start. The amount of effort required to switch them all to hot start, only to switch them all back again isn't worth it.

hi Sockeye, we are using a post-SL-MoD work around for this right now. Basically, each time we update the stats table on the website (hourly) we check each kill score for obviously erroneous counts (i.e. scores over 20 or so). If such a score shows, we just adjust it down to a 1. Naturally, it would be better if DCS was pumping the correct scores to Sl-MoD in the first place, but this is a bit of jiggery pokery that does the trick in the meantime.

True, some of the brightness is a bit striking in 2.5.6 when compared to previous. I've dragged my gamma slider back a couple of decimals since the patch. I note that Normandy is lookging rather pale/ bright again, and that aircraft were disappearing against the sky in that 1000 to 2000m ranage again. I ahdn't seen this for a while, and I thought that maybe aircraft spotting at close-mid range had been fixed. I'm convinced this is a shadows issue though. As long as there are shadows on the aircraft, spotting the, at medium range always tends to be OK. When the shadows do not generate, they disappear more readily.

Dark & Mat painted props still reflect glare. Sure, not as much as a glossy or pale-painted prop, but you still get edge and surface glre off them if the angle to the sun is right.

In the middle of a tailchase with an FW190 last night, I twice caught the full-blast of sun-glare off the prop disk from the fleeing enemy. It's so beautifully done, the entire disk flashed up for half a second. And it wasn't some kind of cheap white-texture just overlaid on top of the prop disk either. It really looked like the glare was being reflected off the spinning blades. Despite some of the obvious 2.5.6 bugs and what not, there are some truly nice touches being added to DCS at the momennt. Also, heavy calivber flak is working consistently in Multiplayer now too. I finally got the full force of the AA batteries at Caen over the weekend :)

Hi, no, we're not getting specific data about who-shot/ killed- who. Personally I'd love also to be able to attribute shared-kills, but that isn't possible as yet. We can do this for another Battle of Britian period sim, which is really nice becasue it stops kill-stealing to a degree.

Awesome! thanks Grimes. I'll keep an eye on updates. Let me know if you need any help with WW2-related stuff/ testing etc.

If ED could add a tool which can be used to customise and generate misison stats (into some kind of simple database or .lua file) that would be a real help for multi-player server hosts. Currently, all sorts of third party tools and work arounds are being used to generate the most simple of mission/ player statistics. Ideally, I'd love a little mini-app that sat alongside mission hosting. This would have a set of stats options thatv the host could toggle on or off. Thos ewhich were set to "on" would then be gathered from the missino whilst in progrss and puiblished to a mission log file, or (even better) and continuously updated server stats file. The format of the file being optimized for tabulated website stats publishing. Hell, I'd even pay a monthly subscription to have such an app as a DLC for me as a server host.