As a pc player ive been seriously contemplating doing a “controller only” comp season
Because im a troll like that
Guess I’m out of the loop. I remember the original news cycle was just talking about how mimic invisible these were.
I’m looking it up now, though, and I guess they really have found better ways of detecting and now implementing punishments for it. Fantastic.
Who is going to weep? Cheaters? Oh no, I am so sad on their behalf. How ever will they maintain their ranks now? ༼;´༎ຶ ༎ຶ༽
4 Likes
but thats not what is at stake. its the internal AA they have for console. theres also the fact OW doesnt need a top end graphics card, and a higher refresh rate monitor isnt that expensive anymore. Im rocking gtx 980ti and play on low graphic settings because OW is about the game play, but i will say that the upgrade from 60hz to 144hz was the best thing i did, and i support everyone making that jump.
when you play in qp, i personally find its rare that there is not at least 1 console player in the match - and the sad fact is, they get singled out asap and usually get deleted
the grouping of pc and console in qp is fine, but for comp its a recipe for disaster
I dont think you understand what’s happening here. The platform knows the type of device that is connected because the devices themselves report device IDs and types. In the case of XIM, it’s just lying.
There’s a difference between a M+K, and a M+K attached to an adapter that reports itself as a controller. XIM is a middle man that hides the fact that the M+K exists at all, and lies to the OS claiming it is a controller.
3 Likes
If it works flawlessly for other games then there is zero reason why it doesnt for OW other that Blizz not it coding into the console version to actually turn off aim assist when it detects XBM.
The console detects it, always. But it cant do anything to turn off features from games, its up to the game to be coded so it does changes based on the info the console is giving it.
Completely different things and the comparison alone showcases how ignorant and/or obstinate you are.
1 Like
I was referring to the person who thought I was just saying it out of cope. I don’t even play console.
I saw the article, and thought it was interesting to the peeps here.
Cant wait to see a “i got banned for ximming and wasnt” post… because a bunch of pc players who are unhappy about being forced into cross play… report console players falsely…
Inb4 that happens
2 Likes
Well even for just that… what prevented Blizzard from giving the controller players a false sense of security years ago? It just seems arbitrary to suddenly decide to that now if that’s all they’re really doing.
Ximming was made a ToS violation some time ago… and the screamers were silent for quite a while…
So it clearly works
Yes, and now they are about to do the detection for it. You know like everyone else has been doing. Likely it has just been turned into a library call for them.
Yea, im glad. Maybe i can start utilizing its enforcement to purge comsoles from my lobbys
It is funny because they are finally going to fix this issue exclusively because of PC players. With crossplay, they did not want console cheaters rolling and smoking PC players. I, personally, believe it would have been funny to finally bring merit to their aim assist argument. But I guess the good times never last long.
4 Likes
It is more likely just pushing people who ximm into your lobby and out of the console lobby (with aim assist off).
But without details that is only a guess.
Either way I am sure a bunch of accounts are going to have some serious readjustments.
Lol… nah im going to be xim reporting every console i see…
And im sure i wont be the only one… see how long it takes for somone to get falsely banned
Dont want that risk? Stay out of pc lobbys
Its not personal…
2 Likes
Actual words of wisdom. I am relatively certain reporting is broken on console. I am testing it currently using the Mr. Whipple, Mr. Nae Nae method. The PC version actually bans people. So watch out my console brethren.
1 Like
non-factor. non-issue. considering consoles are kbam ready. so any such unverified rumor regarding xim is redundant. besides, xim uses controller aim with mouse as artificial endpoint. so, whats the actual issue? sony allowed astro to exist on its platform, only so that sony could copy the c40 controller and call it the edge, in which edge doesn’t ship with console. instead, a 30 year old controller ships with all PS consoles.
allowing an elite controller, astro c40, on your platform, so you can copy it, then revoke compatibility, and not ship the controller that you attempted to copy, astro c40, which birthed the PS edge, yet instead, sony ships ancient outdated controller layout with all PS5’s. all PS5 controllers are obsolete af. which is why sony used astro for creative inspiration then blocked astro from PS5 in-game compatibility.
which is the very reason sony revoked/renege astro c40 PS5 in-game compatibility. once you touch a c40 you can’t touch a dual senseless remote. sony, ship PS5 pro with edge controllers. and reinstate astro gaming c40 controller compatibility. artificially disabling astro from PS5 games after copying their research and development, AND after all they’ve contributed to the gaming industry is excessive bitterness.
Well tbh, i have low expectations when it comes to “detection” and bet its likely going to end up much like how abusive chat reports work…
So even if your legit, if enough reports are made youll get flagged…
Furthermore it just starts the cat and mouse game… developers and cheat developers have been playing since the dawn of time…
Basically it just encourages them to build a better xim that can circumvent alleged detection…
Some of you really need to learn how to write. Failures of the educational system.
Bro, you can literally just look at your post prior to this one and I could count multiple spelling and grammatical errors. Chill, you ain’t all that.
6 Likes