Announcement

Collapse
No announcement yet.

Can you use Shift-layers on controller RT and LT both separately and simultaneously?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Darkvulpine
    replied
    Originally Posted by Support Agent View Post
    Remove [Shortcuts] from layer 3 and 4 do disable that behavior.
    Well yes, I did try that too, but that leads up back to the original problem.

    also tried having it set as "Hold" and having the modes more directly swap to 1/2 and 3/4, and back on release. The main issue is there is no way ensure if trigger is NOT held, it goes back. It seems to merely read the moment it is released.

    Ihave tried to toy with the delays as well, not sure what the difference between a "delay" and a "postpone" but I tried various options.

    -----

    For now I went back to using Steam profiler, since I can have a mode shift that I can allocate to the opposite trigger, while held, a round-about way, but works well enough..

    I still miss Padstarr, Shame it got taken over by the internet and riddled with malware. But it also had a great feature of effectively having ways of programing buttons do different things each time they're pressed. "Cycles. Even allows other buttons to affect which part of the cycle it's on.

    Great for GW2, Elementalist Tempest, where no matter which element I'm on, I can press a specific button to activate the tempest's special (which normally would need you to press the element's skill, 1-4, instead I just press 5, essentially.)

    Would be nice to have these features in reWASD, but for now I'd settle with having the Triggers be fixed. Right now there's no profiler out there (that's not malwared) that can give it.

    Leave a comment:


  • Support Agent
    replied
    Originally Posted by Darkvulpine View Post
    One problem fixed! But now on release it'll always go back to main, even if still holding LT xor RT after releasing the LT+RT state
    Remove [Shortcuts] from layer 3 and 4 do disable that behavior.

    Leave a comment:


  • Darkvulpine
    replied
    Originally Posted by 1ncorrect View Post
    Please send me the config you are using. Your configs are stored here: C:\Users\Public\Documents\reWASD\Profiles
    I need the correspondent *.rewasd file.​
    One problem fixed! But now on release it'll always go back to main, even if still holding LT xor RT after releasing the LT+RT state

    Leave a comment:


  • Geowulf
    replied
    This is the config with the shortcuts included but atm Im running it without (which gives me the original problem that releasing both triggers at the same time doesnt go back to main layer)
    Attached Files

    Leave a comment:


  • 1ncorrect
    replied
    Please send me the config you are using. Your configs are stored here: C:\Users\Public\Documents\reWASD\Profiles
    I need the correspondent *.rewasd file.​

    Leave a comment:


  • Geowulf
    replied
    Now I have the issue that the shortcut activates when it should not. It activates a lot of the time when releasing RT or LT and not just when both are released.

    When I release LT but keep RT held down I want it to drop 1 layer but if I release both I need it to go to the main layer without getting stuck. I think the fact that this shortcut runs when it shouldnt is due to the buttons being released on layer change maybe?

    Leave a comment:


  • 1ncorrect
    replied
    We are always glad to help

    Leave a comment:


  • Geowulf
    replied
    Thank you, this looks to be what I need. I have added this shortcut to all layers (except main) and from what I can tell it is working perfectly.

    Leave a comment:


  • 1ncorrect
    replied
    Originally Posted by Geowulf View Post
    I have the same issue with a very similar setup (Also for FFXIV). Releasing RT and LT at the same time causes the layer to get stuck somewhere instead of being brought back to the main layer.

    Is there any work around to reliably return to the main layer if RT = 0 and LT =0?
    You can achieve this result by making a special shortcut and assigning a return to the main layer to the Release Press activator.
    Click image for larger version

Name:	image.png
Views:	205
Size:	132.3 KB
ID:	242122

    Leave a comment:


  • Geowulf
    replied
    I have the same issue with a very similar setup (Also for FFXIV). Releasing RT and LT at the same time causes the layer to get stuck somewhere instead of being brought back to the main layer.

    Is there any work around to reliably return to the main layer if RT = 0 and LT =0?

    Leave a comment:


  • Support Agent
    replied
    This is a known issue, and we are already working on a fix. However, we can't guarantee that the fix will be included in the next update.

    Leave a comment:


  • Darkvulpine
    replied
    Originally Posted by 1ncorrect View Post
    Could you clarify the steps to reproduce these stuck?
    the steps are simple, it's not super common, but pressing both LT and RT, and letting go of both around the same time can cause it to get stuck on either SL 1 or SL 2, pressing LT and RT can fix this, but it's unreliable when in the heat of action, and suddenly what you're wanting to do with the default bindings is using up your skills instead of selecting a target at the moment you need.

    if you want to really test just keep pressing both LT and RT together a few times, with the notification of Shift Layers changing turned on, so you can see which one you're on.

    Leave a comment:


  • 1ncorrect
    replied
    Could you clarify the steps to reproduce these stuck?

    Leave a comment:


  • Darkvulpine
    replied
    Originally Posted by Miron4ik42 View Post
    I didn't notice any stucks too. Could you let me know how you recognize this stuck? Are you able to show it in the tester?
    I have the option to show a notice when the layer changes, so I can easily see which layer it's currently on
    Gear icon top right -> Overlay
    Normal Shift is Enabled
    Toggle Shift is Enabled

    Leave a comment:


  • Miron4ik42
    replied
    I didn't notice any stucks too. Could you let me know how you recognize this stuck? Are you able to show it in the tester?

    Leave a comment:

Working...
X