![]() ![]() ![]() it's just a small issue in your controller setup. This is a very annoying issue and I saw a lot of question about how to pass this mini-game and thoughts that this mini game is simply broken on PC port of the game. In this moment signal about default position of analog stick can be recognized with minimal value and it's already considering as movement, so you will fail. You moving Mae's paw with left stick and when dog start looking at you, you need to release the stick. It can cause situation when signal about default position of triggers with values near zero can be recognized as minimal movement and leads you to failure in some mini games where you need to hold steel.Įxample: In beautiful game called "Night in the Woods" you have mini-game where you are trying to steel delicious pretzels. I have 30 years of muscle memory to try to overwrite but I am firmly of the opinion that long term, this is the way.One thing that I recommend you to do is to set analog sticks "Dead Zone" at least to 0.09 to prevent analog input jitter on them.īy default DS4Windows tool endlessly gathering signal about position of analog sticks and triggers even if they are in the default position and you do not even moving them. So far I felled many side bosses and progressed through the second main story boss and I can honestly say to myself when I die now it's mostly due to a mistake on my part and not the change in controller and getting better. Dodge sprint is bound to pulling my index (pointer) finger back because that seems to be the finger I have the most dexterity and speed with. So when you press the button it actually sends the release command to the game giving a dodge on button down as opposed to waiting for you to physically release.įYI, I did try both of those and I did achieve the desired result but ultimately I decided to spend time focusing on trying to build muscle memory and learn timings using the default set up. Use one to hold exclusively for sprint and the second mapping could be set as an "on press" do "release". Map the dodge/sprint action to 2 separate Azeron buttons. Projects 1 Wiki Security Releases Tags last week Ryochan7 v3.2.13 37c0701 Compare Version 3.2.13 Latest First Launch. Your finger has to travel a bit further to activate the sprint/dodge button.Īdding dodge to a mouse button (short travel should provide a very similar feel to controller) The big difference is the throw between Azeron and Controller with regard to the button. Because the same button is used (when held) as sprint, dodge is not executed until the input is released (as long as it was not held long enough to initiate a sprint). I thought I had a dodge input lag issue as well but in reality the dodge button is performi exactly the same as on controller. ![]() You may have a different scenario than me. For those controllers I'd set the left stick to be a B button and set the touch pad or share button as left stick. Dual Shock and Dualsense will have more options since they essentially have 4 buttons in the center of the controller. Bring your DualSense Controller to life Use 20 different Adaptive Trigger modes, enable Haptic Feedback(USB), Emulate Xbox 360 or DualShock 4 through USB. For example, holding the left stick button for a short period of time to trigger the B button. Basically you'll need to change other mappings to allow B button's use elsewhere. If you don't have paddles/back buttons on your controller there are alternatives, but they aren't great. I found that reWASD blocks Xbox Elite controller's (Series 1 and 2) native set mappings for paddles, so you'll need have the B button mapped there as well (along with any other paddle mappings you want). The more time this takes, the more input lag there will be. When you press a button, the controller has to send a message to the console via Bluetooth. When a PS4 controller is on and not plugged into the console, it’s running off battery power. You'll also need to mark it as "unmapped", so that regular B button input is ignored. Plugging in your PS4 controller will reduce input lag. ReWASD specific directions: The B button macro is done via a "Key Combo". I did this by setting up the paddle button (back button) as a regular B button. Next you'll need to find a way to use the run function. You can try less than 15ms, but I've found it becomes inconsistent. There are many programs that can do this (I'm sure Steam's remapping feature can), but I use reWASD.īy setting up the B button so that it triggers B down, waits 15ms, and then B up, the the input lag is essentially removed. To work around this, you can macro the the input so that pressing down on the button triggers both button down and button up. This means dodge only occurs on button up and not button down. You can obviously use a similar solution with KB/Mouse.Īs many have pointed out, the dodge lag is caused by having both run and dodge on the same button. The best version of my fix requires paddles (back buttons), though I point out further down that inferior options are possible w/out them. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |