Forum

I've not had any issues with sound or shadows. I'm not quite sure what's being discussed. Seems like a bulk amount of complaining. Does anyone actually have screenshots or video of the problem?

Haha, don't worry, Spanky. I'm definitely not complaining. I just want to prevent folks like me from having such a BS advantage by masking my own sound via the game's deficiencies. This is quite BS, to be honest. It definitely feels that way, and I get accused of hacking daily, and I honestly don't blame folks for accusing. You wouldn't believe how often and easy it is for me to sneak up on people. As for those shadows:





And don't be silly enough to think I play with these shadows and this is the reason I can "sneak up" on people. Don't make me video record you!!! I've been doing that lately. ;-)

There are lots of things you can already hear; there are just anomalies that I think we should address and make it better for everyone. Like I said -- if you want players like me to have an advantage like that over others because they're not as experienced and/or in-the-know, fine. lol

So I've long noticed that the sound in 2.5 is a lot worse than 2.8.5 and, in many respects, simply inferior. The doors and footsteps are literally, completely silent if you take advantage of certain peculiarities in the game. For example, a popular glitch we all used to use in Invite-level competition was on Pipeline. When, on assault, rushing Primary (or to Main Pump basement) from Oil, if you keep running without stopping, the sound you actually make won't render for the other team until a moment AFTER you are directly in the FOV of the other team. This occurs even if an OpFor is on Basement floor crouching down and looking at Primary. For OpFor, the enemies will simply 'appear' there like a ghost, or like the theoretical result of a teleportation device, with no precursor indication.

Another example is carpet sound, which changed in 285 and became not only, subjectively, better-sounding, but also better for people to hear it correctly. I believe 285 also changed the internal rolloff filters. The gun clicks and nade-pin sounds in 285 were crisp, sharp, and could be heard nearly anywhere on the map, which also balanced out some of the game's peculiarities in its sound production. And they probably did this because they had to remove/disable shadows altogether, as a result of a graphical anomaly (which still exists in 2.5 today) that allows big, black, boxy "shadows" to appear through walls, floors, etc.

I submit, basically, that we should try addressing the sound glitches of which folks who are in-the-know can take advantage, and simply allow everyone to hear more. I don't know if this encompasses modifying the internal roll-off filters or whatever, but I do know that even someone without an X-Fi (or any 3D-surround audio interfaces) will benefit from being able to hear more and get an idea of where people are when they are near -- rather than sounds randomly going straight to 'mute' when you were JUST able to hear them. Instead, I think the sound should gradually decrease with distance, which is more realistic. So if this is possible to implement, it would be amazing, and it would stop me from being able to sneak up on people all the time who, realistically, should have been able to hear me.

Lastly, the big, black box "shadows" are still here, and I think it's time we either disabled the "Full" option for the Shadows (which is the only way to promulgate the shadow glitch), or we figure out why it happens at all and fix it. I'd go with the former, seeing as though the AA devs didn't even really figure it out; instead, they simply disabled being able to put shadows to "Full," but they allowed "Blob" because you can't do the glitch with the Blob setting.

Agreed. And SUP, Utroda!!!!!!!

Don't worry, I don't have installed... 

Anyways, Assist 'license' is not valid under the law - and thus, this button might as well not be there.

Why do you believe it's not valid? If you want to play, you have to accept these rules. It's pretty simple. The purpose of the screenshots is to ensure that users of Assist are playing fairly, as all other people on Assist are legit and expecting others to be the same.

You mean to tell me that you believe it's OK for players to be able to load up hacks that modify assist and dismantle the leveled playing field? And we should clarify this notion that it's only for suspicious/dirty players. Rather, Assist can take screenshots of ALL players. If you install software that informs you that it will do this, it's up to you to decide whether you are OK with admins seeing you play the game, to ensure that you're playing fairly.

In this regard, essentially, Assist works just like any AC Client we've seen in the past. When we used AC Clients in competitions, it was connected to AA's files and loaded up AA, just like Assist does. Some of these clients were not only able to take screenshots, but were also keylogging players while on the client, a la CEVO's CMN3, and players agreed to this prior to engaging in matches while running the client/s. There were no 'legal' issues then, so why would there be legal issues now?

If you're coming from the angle about AA, itself, being copyrighted, modified by Assist, etc, then I guess I'll say that, as an American tax payer -- who, along with other American taxpayers, contributed to the development of this free game -- I'm OK with Assist keeping the game alive. I'm glad my tax dollars didn't go to complete waste and that I'm still able to play. More importantly, though, is how that angle has nothing to do with the "I Agree" button being illegal. Consider Teamviewer (http://www.teamviewer.com). With Teamviewer, two (or even more) people can consent to accessing the others' computers in many disparate fashions, even to the point of full control. If a person maliciously, and without consent, accessed a person's computer with Teamviewer, this person is breaking the law. Teamviewer, however, is not illegal. The same would apply in the case of Assist and its prerequisite agreement conditions.

Why not just explore ways to prevent, or simply catch, cheating? Before the ball dropped about Assist (when we possibly almost lost it forever), I had a long discussion with one of the admins/devs on xfire about some of the ways to deal with things like this. I've played this thing a long, long time -- at the very apex of competition we've been blessed to have in this game. Over a span of 10 years, I've been intimately familiarized with nearly every aspect of being an AA Player -- a "scrub," a "pubscrub," a "cheater," a "starter" on top teams, a "head admin" of a league, all the way to an "Anticheat" guy who infiltrated the hacking underworld, along with Reaper ACI.

When playing in these leagues and competitions -- Cal Invites, HTGN, TWL, AGC, Cevo Professional, etc -- there were similarities and differences in the way they handled matters like this. We can examine some of their successes and failures to determine effective ways to stop, underscore, and deter cheating.

But firstly, let's address some pivotal info about hacks. Hacks are pretty useless if you don't have the visuals (i.e. wallhacks, radars/esp, etc), especially if the cheater is attempting to be discrete about their cheating. If a cheater wants to 'aimbot,' they have to 'know' where the enemies are, so that they are not in the peculiar situation of multiple enemies being in their field of view, because this would make the player spin around everywhere like the Exorcist, constantly 'locking on' to heads (and the cheater better not EVER go idle, hahahah). This, of course, is a huge indicator of aimbot usage. Similarly, playing with no recoil is not a great idea for cheaters looking to hide their artificial "skills," as first-person spectating and bullet-spread decals will quickly highlight their digital malice. Without the visuals, fundamentally, all a hacker is really left with is "no-flash" (if their hack even has something like that). And no-flash is not enough to give them that great of an edge anyway, as they would have to "fake the funk" to prevent detection, so the point would be vacuous. So, with this info, let's examine the leagues and find some interesting information, which can EASILY help us in these modern days of Assist:

TWL -- it had an interesting run over the years, but after the first couple of major seasons, its significance and popularity began to wane, and slowly continued to do so, on up till the end, because of its insecure, yet stringent AC practices. TWL's AC could be easily bypassed. It did the basic stuff -- checked processes, scanned for extraneous things and general AA-centric system anomalies, but it barely ever caught "good" hacks. What made a hack "good" was not only its ability to bypass initial detection of a league's AC client and Punkbuster with its proprietary, constantly-updated hooking methods, but also its ability to discern the algorithm with which Punkbuster, and a league's AC client, use to capture players' screenshots (this is VERY important). Well, I don't think TWL ever got around to making its AC client take screenshots at all; and if it did, it captured them in a similar, "set," "static" fashion like PB's capturing method.

If an AC client is coded to only capture screenshots in a "set" fashion -- say, every 96 seconds -- then this is blatant predictability. What I believe I was told about PB was that its "updates" incorporated different static "set" capturing methods, which then prompted hack developers to update their visuals-bypass functions to correspond with the modifications within the updates for PB (and whatever else they were attempting to circumvent). So, with no implemented method of capturing "good" hacks, what TWL resorted to -- which contributed, greatly, to its lack of relevance -- was ban people for all sorts of stuff, like linked accounts (even loosely linked), pub bans, forum bans/disruptions, and all manners of things that weren't even pertinent to playing in TWL itself and on its client. This, in itself, was a huge indicator that it had no trust in its AC client. Top, well-respected players in AA who have never touched a cheat, or even been accused of a cheat, have been permanently banned from TWL, but those players didn't even care, because no one really trusted TWL in the first place, EVEN WITH their strange, paranoid, anti-cheat measures.

In CAL, early on, it was scientifically proven that their AC client was a complete and literal joke; meaning, essentially, it did n o t h i n g at all. It did, however, probably scare some people into not hacking in CAL, but the client itself was a bluff. Later on, though, they did get it to do something. It did an interesting job at catching hooking/injecting methods, but it still wasn't good enough, as its screenshotting method was static. The Cal "ACS" was updated a lot, though, because of people like me and Reaper. At that time, I had many connections in the hacking underworld. Hackers shared with me their forum accounts, and so I had access to these hacks whenever they were updated, and so Reaper and I would grab them and send them to Punkbuster and the leagues' AC depts (particularly CAL, as it was the biggest, most important league at the time). Ehhh, this operation we had going had to remain kinda hush, which means many people don't even know this was going on, as my hacking connections would've fucked me up (some of those dudes were seriously mentally ill/psycho). In fact, it had already happened once before when a well-known hacker got pissed at me and screwed with my computer for a few weeks. lol, I think Jonny from audigy/IoG remembers this time. But I've digressed. So the only reason some people's visuals were detected on CAL ACS was because we were sending the updated versions of the hacks directly to the leagues' AC (oftentimes before a lot of the cheaters even got a chance to download them, lol). This allowed CAL ACS to update its SS-capturing intervals, and so folks who tried to cheat on the ACS got banned because they had hacks that weren't updated to bypass its visuals on the right intervals. But doing this week after week was an annoying thing, and doing something similar today is not feasible; plus, I have no clue who's manufacturing AA2 hacks these days, and I'm sure the folks who DO know are not willing to do what I used to do.

Then, among others, we have the CEVO league. CEVO's AC client -- named "CMN3" at the time -- was probably the most feared AC client in the history of America's Army. We had to pay to play in this league, so the AC had to be trustworthy, and it was. Because of the secrecy surrounding all that it did, I'm not entirely certain about everything regarding this client. HOWEVER, I did find out something quite profound regarding why hack developers gave up on it. Turns out that CEVO took random, unpredictable screenshots. Now this is something I talked to Possessed about on Xfire during the recent, ephemeral death of Assist. This type of capturing method is beautiful; and with Assist being our very own AC Client, I think that there are substantive ways of catching hackers and leaving the ones we don't catch heavily debilitated (and 'catchable' if they become tempted to 'get good'). As I said earlier, without their visuals, it becomes a daunting proposition if they want to go unnoticed. A cheater without the visuals is either going to be a bizarre, spinning, Exorcist-like Blatant-Bobby, or he's going to be pretty bad, like everyone else. haha --

As of right now, although many don't realize this because they didn't read the new Assist agreement, Assist can take screenshots, but I'm not entirely certain if it takes the screenshots automatically and randomly. If we could incorporate this ability into Assist (if it's not already there yet, as I suggested to Possessed), then couldn't we just shoot for this? The screenshots could be automatically uploaded to a server, or servers, old PB style, where they can be viewed on an webpage that simply lists links to images of players' screenshots. This would use up some bandwidth, but it shouldn't be that bad at all. Perhaps we could do an auto-purging thing for these SS images after, say, 48 hours or whatever. This would help free up server-capacity space.

In closing, after all my years of AA, the most effective AC method I've seen was the client (CMN3) that took random screenshots, and not the set, predictable screenshots of everything else, including PB. And as for banning policy, I say if they cheat on Assist, charge them $300 to play again. Assist, at its core, is already a second-chance thing, and cheating in a game that only has a handful of players is really messed up. But a perma-ban would just mean 1 less player. Make them pay; this could help with the development.

SORRY FOR THE WALL OF TEXT!!!

I'm not sure why it's doing this, but Assist takes FOREVER to load up fully. This is all occurring, suddenly, within the last two-three weeks. Assist (and the pertinent AA folder) is installed/located on my secondary Internal Drive (WD 1TB, 7200rpm). As it's loading, I notice that I cannot access the drive's directory and files. Eventually, it does load, but the worst part is -- it makes that particular drive disappear afterwards; or, if it doesn't disappear after the first Assist/AA session, it will completely lock up the drive the next time I try to run Assist (when I have not turned off the PC since the previous AA session). Then, after it finally decides to unlock itself, the Drive is no longer accessible, unless I Shut Down. Importantly, I use this drive for recording large audio files (.wav, 32-bit, 96khz audio). I can easily undergo full-fledged audio recording, mixing, and mastering sessions with this drive, with no problems, hitches, hiccups, or anything. But as soon as I open Assist, the drive begins going down the proverbial drain.

I don't understand why it's doing this, though. It wasn't doing this before. I remember when Assist used to give that weird, random, "firewall" error; after this was fixed -- via an Assist update maybe -- I think this is when these problems began.

Any help would be awesome! I've been researching my ARSE off trying to figure out what's wrong. I've already checked the Power Management stuff -- disabled sleep/hybrid mode, disabled idle-disk turn-offs, and all that good stuff. Something tells me it's a Windows problem, but since Assist seems like the primary agitator, I'm wondering if someone can tell me 'what' Assist is doing when it says "Checking AA." Maybe that can help me fix this. Like, what could Assist be doing/accessing/writing that could affect the hard drive in this manner?

Thx!!!

Negative Impulse

xfire: namelessmadman