X-man

In that sense, yes. But if you have such a bad connection, you shouldnt be flying on public servers ;) But lets say you have ACMIs of 2 or 3 different instances with same chaff behavior, it is most likely not a connection issue. EDIT: Re-read your post. In the way you are describing it, the server is receiving false data from the offender. That has nothing to do with ACMI, and will in fact give the chaff/flare behavior in game. So track, ACMI and live play will see the excessive chaff/flares. So 'gameplay' will be affected. Intentional or not, excessive chaff/flares will still destroy the fun for other players, and hence the guy in question should not fly on public servers... But enough with this, flare/chaff hacks are quite easy to discover if you can record the same behavior during multiple, independent sessions...

No, the server does not have to record ACMI. The clients gets data from the exports. So there is no 'main' data which can corrupt on the server side. If a client have a bad connection, he will not receive the exported data correctly and he will then get a faulty ACMI (or at least COULD get). Exported data is different from the track data, which is why you can always get a track, but not ACMI, as the server export function must be on then. Basically, try to have different sources when going to some server host and asking for a ban or warning on the offender. Witness, screenshot, logs, ACMI, track etc... edit: And by witness, I dont mean 'the guy evaded 5 missiles head on flying straight' but more like the amount of flares he was popping or similar...

Correct. If there was an inconsistency, it would be just as likely for any variable. However, the more ACMI with the same consistency, the less likely it is to be a bad connection issue.

Let me be clear. Tacviews do not always portray what actually happen. But that does not mean ALL tacviews show errors. Most of the time, tacviews are accurate. So if you can show several tacviews with same behavior/suspicion, it is more likely to be true.

No, the track uses different data so they can be different...

Thats right, ACMI are not always correct. This can be due to connection issues or packet loss where the clients does not receive all the correct data. For example, in large scale events like LOCERF or BSS, it's not uncommon to see player names switch with eachother, even between coalitions. Missile data can also be missed. ACMIs can be used a little like lie-detectors, it can be used along tracks logs and eye witnesses, but not on it's own :)

Yes, we are... As this is the only example we can speak for... ;)

Im not a programmer, so I would not no :) Case or Yoda can maybe answer that. (I would bet no, otherwise they would probably have done it :) )

Cant argue with that, if your point of view is that the server hosts are leaving loopholes in their LRM so that they can cheat for them selfs, then there is not much one can do. I have yet to see any proof of that, or that of any other cheats for that matter. There are a lot of claims of cheating but very little stuff to back it up. Show us some tracks/tacviews of it before screaming foul play... Ive had my fair share of flying on HL through the years and I have not seen many cheats, extremely few actually. I can understand that it's very easy to get those thoughts in the heat of battle when you loose SA and someone gets you from nowhere. But after reviewing ACMIs, 99.99% of the time, you'll find that it was simply some great flying or pure luck from the other guy. There was this one time where a guy popped 60+ flares in a MiG-29A on our server and that is clearly not doable without some kind of alterations to the game, but that is pretty much the only cheat (except LOPE) I can recall seeing.

I think you're missing the point Case is trying to make here, LRM prevents people from running their on programmed LUA-scripts locally as LRM FORCES the export.lua on to the client. There no way around this. You can have all the scripts you want on your end, they will not be used... However, on the topic of general cheating, yes no one can prevent print screening and such, but then again, how would you prove it as opposed to lag?

51st is actually running the good old Dead-mac software, not AMRACT :)

Checking in! :D

It can never get caught for speeding, the Police just cant get a lock on it :)

Correct, your turn! :D

Sorry Im late! :P To what aircraft does this landing gear belong to?

Nice shots, Vex! :)

Myasishchev M-17/55? Correct ;)

You're good, Sniffer :) Your turn

This should be a tough one (not military though). What is this plane:

Is that the YMC-130H?

Very nice shots! :thumbup:

Congratulations! :thumbup:

Impressive flying! :thumbup:

Briefings are now posted for everyone signed up! Head over to the 159th forums to check it out: http://www.159thgar.com/forums/index.php

Here are the following teams for LOCERF 09-2 RED: 24 Fighters / 7 Strikers 159th: 4 x Su-33 =4c=: 6 x Su-33 / 4 x MiG-29S / 3 x Su-25T 104th: 4 x F-15C SVK: 5 x Su-33 / 2 x Su-25T Russians: 2 x Su-25T DarkWanderer: 1 x F-15C BLUE: 23 Fighters / 6 Strikers =2IAE=: 6 x MiG-29S 51st: 3 x Su-27 169th: 3 x F-15C / 4 x MiG-29S =SE=: 6 x Su-27 / 2 x Su-25T JaBoG32: 4 x A-10A Maddogg: 1 x Su-27 If anyone feels unhappy about their slots/aircraft, please contact me. I cannot guarantee any switch!