Common Stats Project

[Fudd]

I dont know if I would want to prevent people from flying low.

How would this be exported btw ?

 

I'm not sure how it would be exported. We could always run it and see what it says in the logs. I imagine it would just show up as a crash.

 

If you want to be able to fly low but want to still use this trigger you could put the altitude at 5m and then give another rule for "time more" and put 10 seconds. Its not perfect obviously, but we work with what we have.

 

Maybe we can get an Landed trigger rule for 2.0?

 

EDIT

 

It doesnt work very well with the trigger at 5m. If they land at a road with an elevation above 5m it wont work. We need a landed trigger.

Edited February 24, 2010 by Fudd

[Grimes]

Fudd, we can always crank up the probability of bird-strikes to combat low alt flying.

 

With regard to "learning" the mission to best destroy the ground targets. It will always happen to an extent. The fun part about triggers is you can pretty effectively randomize threat location, thus preventing the player from figuring it out easily. I have a test mission that currently chooses between 4 possible locations for EACH layer of sams and ground targets. It is different everytime and players will never know which layout is being used when they enter.

 

The thing about a2g scores is that its not exactly similar to pvp kills against air targets. The ground units SAM sites are predictable in location and in combat tactics, it is just a matter of finding the threats and destroying them. Furthermore many consider it to way to easy to rack up kills in an empty server. Yet it is still unfair if there a fighter joins a server that has only a2g people playing in it. Without teamwork of any kind you can't expect for a a2g aircraft to combat a fighter efficiently. Even if you have 2+ squadmates flying a 25t and you get into an engagement with a fighter, you might get an a2a kill but chances are at least one wingman will get shot down. The only plausible solution then would be to have fighter escort to be a needed asset to the strikers. Perhaps keep the basic layout 3sqn and 51st run with out missions where the A2G target areas are just outside of the main a2a combat area, but change it so the safe A2G targets are always worth less points and the valuable targets require teamwork. Thus we have something for the lonewolf A2G guys to do safely and we have a real challenge for the core mission.

[RvEYoda]

I'm not sure how it would be exported. We could always run it and see what it says in the logs. I imagine it would just show up as a crash.

 

If you want to be able to fly low but want to still use this trigger you could put the altitude at 5m and then give another rule for "time more" and put 10 seconds. Its not perfect obviously, but we work with what we have.

 

Maybe we can get an Landed trigger rule for 2.0?

 

EDIT

 

It doesnt work very well with the trigger at 5m. If they land at a road with an elevation above 5m it wont work. We need a landed trigger.

 

 

1. Parse mplog.txt realtime, if "PlayerX landed", goto 2 ( or with a landed trigger )

2. Use lua exports on server side with either LoGetObjectById or LoGetWorldObjects. check the position of PlayerX. If PlayerX landed within allowed areas, give score.

 

Players using others callsigns:

I'm worried that when stats really kick off, there will be trouble with people faking names.

To prevent this we could write a short login-sript where each player needs to log into the server

if he has registered on its stats page. Basically what each registered player ( you dont need to register

to get stats, but it will be helpful for some people ) just fills in callsign and password in a login file.

Edited February 25, 2010 by =RvE=Yoda

[Case]

In FC1.12 landing on roads is not really such a big problem, because with the airbase scripts in LRM they can land but can not take off. I agree it might be good to have a fix for this for FC2.0, and the landing trigger is indeed a good way of doing it.

[RvEYoda]

In FC1.12 landing on roads is not really such a big problem' date=' because with the airbase scripts in LRM they can land but can not take off. I agree it might be good to have a fix for this for FC2.0, and the landing trigger is indeed a good way of doing it.[/quote']

 

I put in a request for landing trigger, but since there are thousands of requests in that thread,

I don't know how they will filter out the requests... I would not hope for too much

[Grimes]

but since there are thousands of requests in that thread,

I don't know how they will filter out the requests... I would not hope for too much

 

Send flowers?:idea:

[RvEYoda]

So lets say we get a landing trigger, what trigger response to we set to it ?

[Case]

So lets say we get a landing trigger, what trigger response to we set to it ?

Well, we have been pushing a 'write to log' trigger action, which could be used here. So if the trigger is tripped and the player is within a zone around an airbase, he landed on the airbase and you can write that to a log. If he landed on a round outside the zone then you can write out that he landed on a road and don't give him the bonus points (perhaps even give him a penalty for losing an AC, or even explode him upon landing).

[Grimes]

Or write a flag status log. With enough flags you could make a virtual ATC. Not that it would be useful, just saying it is theoretically possible. More practically however you could use triggers that fire flags as a status update of sorts on the mission. Thus making any higher stats program work from basic mission log files and not extra LUA data that might use valuable CPU cycles.

[RvEYoda]

Much of DCS is already using LUA to produce the game itself.

LUA is a very fast language, and trigger-logging will likely produce much more overhead

than a simple LUA export of position, and landing events are already written by default to mplog afaik.

( No need to do it twice )

 

The solution with least risk for stuttering should be to export this data not as files, but through sockets to a

receiving program. Eliminate as much fileIO as possible imo, which has many orders of magnitude worse

latency than a simple lua call ( which is already used by the game itself all the time )

 

You could even use your already present tacview scripts and grab the data on units from those, and you wont

even need to call any extra LoGet-functions. ( Since tacview already does that )

Edited February 25, 2010 by =RvE=Yoda

[Case]

The solution with least risk for stuttering should be to export this data not as files, but through sockets to a receiving program. Eliminate as much fileIO as possible imo, which has many orders of magnitude worse latency than a simple lua call ( which is already used by the game itself all the time )

Would that socket talk to a program running on the game server, or would the data be exported over a network to a program running on a different machine?

[RvEYoda]

Would that socket talk to a program running on the game server' date=' or would the data be exported over a network to a program running on a different machine?[/quote']

 

Well, that is up to you, choose what suits your situation best :).

I made this kind of setup for LEAVU2 where an arbitrary number of clients

can connect to the game machine to receive data updates for display rendering.

 

You could do the same for stats, I could send you my code if you want me to

[Case]

You could do the same for stats, I could send you my code if you want me to

Right now the stats page is working solely with the mp_log, but for FC2.0 I would be very interested in using more data for stats and other projects. I might look into the LEAVU code at some point.

[herig2]

Being a A-10 pilot and reading about the common stats project, my view about

Point stats / Ace stats

Point stats are good, but not a good indication of the pilot's skill. Even with negative points for crashing. Kill enough targets and you will climb up in the points standings. Using a ratio such as the 51st, a pilot has to survive to be included the Ace ranks. Such as I did last week. My story.

Knowing that with my ratio one more crash I would be out of the ace stats ( there are only five spots ). I got hit, Right engine out, hydraulics, among others, I was out of control, at 11000 feet. I was going to eject and so would my ace status. Calming down, I tried to get out of the spin, slowly leveling out with hard left stick and full left rudder. now at 5000ft, flying straight, at least I'm over friendly territory, no worries about SAMs and no Red fighters on the scoreboard. But now I see the fuel gage is going down quick, right tank hit. Time to check out the controls. Have to keep full left rudder with the left engine running or I would yaw, As soon as I start to bring the stick over toward the right, the plane started to roll. Pitch was somewhat ok, flaps, air brakes were out.

Airbase was 17miles out. But the runway is at 040 degrees, my heading was 290 degrees. I could make a very slow wide turn, but with the fuel leak, it would be flame out before I even got close to 040. Ok I'll try it, but may have to punch out. Nine miles out, I spotted a somewhat straight road at my one o clock. With small yaws I lined with it, Cut the throttle, ease up on the rudder. Thank God the gear drop down. Came in fast but steady, hit the ground than went for a wild ride though the countryside. MADE IT.

If I was going for points, it would have been eject, than respawn.

To stay a ace I had to work for it.

[Case]

If I was going for points, it would have been eject, than respawn. To stay a ace I had to work for it.

This is exactly one of the things a stats page can do for pilots, making them think about how they fly and what they want to achieve.

[59th_Streightholo]

The socket version would be great. With the socket version it can be updated instantly. Editing the export script maybe the takeoffs could be shown too.

[Case]

The stats page has reset to March. The results from February can be selected from the drop down box.

[Grimes]

Figured this thread needed a good bump... but also...

 

3Sqn Dedicated Server is now automatically uploading statistics information at intervals to the common stats project. :D

[RvEYoda]

Being a A-10 pilot and reading about the common stats project, my view about

Point stats / Ace stats

Point stats are good, but not a good indication of the pilot's skill. Even with negative points for crashing. Kill enough targets and you will climb up in the points standings. Using a ratio such as the 51st, a pilot has to survive to be included the Ace ranks. Such as I did last week. My story.

Knowing that with my ratio one more crash I would be out of the ace stats ( there are only five spots ). I got hit, Right engine out, hydraulics, among others, I was out of control, at 11000 feet. I was going to eject and so would my ace status. Calming down, I tried to get out of the spin, slowly leveling out with hard left stick and full left rudder. now at 5000ft, flying straight, at least I'm over friendly territory, no worries about SAMs and no Red fighters on the scoreboard. But now I see the fuel gage is going down quick, right tank hit. Time to check out the controls. Have to keep full left rudder with the left engine running or I would yaw, As soon as I start to bring the stick over toward the right, the plane started to roll. Pitch was somewhat ok, flaps, air brakes were out.

Airbase was 17miles out. But the runway is at 040 degrees, my heading was 290 degrees. I could make a very slow wide turn, but with the fuel leak, it would be flame out before I even got close to 040. Ok I'll try it, but may have to punch out. Nine miles out, I spotted a somewhat straight road at my one o clock. With small yaws I lined with it, Cut the throttle, ease up on the rudder. Thank God the gear drop down. Came in fast but steady, hit the ground than went for a wild ride though the countryside. MADE IT.

If I was going for points, it would have been eject, than respawn.

To stay a ace I had to work for it.

 

 

Sounds like one of those ace moments. Good job!

[Case]

Data from the 3Sqn, 4c and 51st servers is know automatically loaded into the database every 15 minutes.

 

The 104th still manually uploaded at a rate of about once per day.

Edited March 15, 2010 by Case
changed 'no' into 'know' as I intended... I hate Mondays!

[Case]

Good news!

 

From now on the logs from the 104th is also automatically uploaded to the stats!

 

Thanks to the 104th for arranging this!

[Pilotasso]

good one :)

[MoGas]

:thumbup:

[Case]

Anyone who is interested in contributing to the common stats board, let me know. I can provide you with a dump of the MySQL database and the PHP scripts for the A2A, A2G, Overall and Squadron pages so you can play with it.

[*Rage*]

fantastic project;)