Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Apex Isnt Working #914

Open
1 task done
sophisticttv opened this issue Feb 1, 2024 · 3 comments
Open
1 task done

Apex Isnt Working #914

sophisticttv opened this issue Feb 1, 2024 · 3 comments
Labels
blocked Finishing this issue is blocked by something (propably by another issue) bug Something isn't working Windows Windows-only issues

Comments

@sophisticttv
Copy link

Is there an existing issue for this?

  • I searched the existing issues and did not find anything similar.

Current Behavior

I have my Anti Micro setup in apex so that I can Neo and tap strafe. All that is is turboed input of the wasd and in game momentum. How this looks is my Set 1 is : Left shoulder is turbo jump/SET 2 (While Held) and set 2: is an 8 way Joystick that is mapped to wasd ,aw, wd etc and on full turbo. The turbo-ing of the buttons on the joystick are not functioning, they are correctly bound to wasd but they do not rapidly input.

Expected Behavior

I expected turbo input of the wasd keys on the joystick of my controller and they are not

Steps To Reproduce

No response

Environment

Program Version 3.3.4
Compiled from packaging: GitHub Windows Release
Built Against SDL 2.26.5
Running With SDL 2.26.5
Using Qt 5.15.2
Using Event Handler: SendInput
Host OS: windows Version: 10 Architecture: x86_64

Anything else?

No response

@sophisticttv sophisticttv added the bug Something isn't working label Feb 1, 2024
@sophisticttv
Copy link
Author

This was all working properly today and the app has stayed closed and running. i have reinstalled and redone my bindings but it will not work

@pktiuk pktiuk added the Windows Windows-only issues label Feb 1, 2024
@pktiuk
Copy link
Member

pktiuk commented Feb 1, 2024

I guess this may be similar case to Valorant. #406

It is possible that this issue could be fixed with: #232

@pktiuk pktiuk added the blocked Finishing this issue is blocked by something (propably by another issue) label Feb 1, 2024
@mihawk90
Copy link

mihawk90 commented Mar 10, 2024

This was an intentional change by Respawn:

https://twitter.com/Respawn/status/1752851828130341315

Heads up, legends. We've been rolling out some changes to @PlayApex to better protect the game's competitive integrity.

We are making changes to remove automated strafing on controller and will also be making changes to prevent the chaining of cfg files via the +exec command during game time. In other words, we are disabling the ability to use some configs that would allow for a greater range of movement than is usually possible within the game.

We want to be clear: the use of third-party tools, hardware, firmware, or software that automates game mechanics for a competitive edge over other Apex players is considered cheating and is unacceptable. As such, we will continue to evaluate potential exploits and take further action as needed.

Basically when the game detects a change in input (i.e. from detecting your analogue sticks moving to keyboard inputs), it disables lurch mechanics for roughly half a second which kills tap strafing:

https://twitter.com/MagicStrafes/status/1752826430243700804

Lurch is apparently disabled for around .5 seconds after user input switches from controller to mnk.

Which means the only possible workaround is if you switch to digital inputs well before jumping and don't touch any other controller key (including your right stick)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Finishing this issue is blocked by something (propably by another issue) bug Something isn't working Windows Windows-only issues
Projects
None yet
Development

No branches or pull requests

3 participants