#"Weapon" trigger preset fires before going over AT "bump"

31 messages · Page 1 of 1 (latest)

fast cargo
#

DSX Version: Latest beta
Controller: DualSense
Connection: Wired via USB
Emulation Type: Dualshock 4 / Native

Just a quick simple question for this one. If I set R2 to the "weapon" type AT setting, the controller/game tends to read the trigger pull as soon as the trigger starts to get any pressure applied to it - which is before it goes over the AT bump. Which sort of defeats the point of the whole thing. Is there any way to move that "bump" up higher, or (alternatively) get the controller to delay picking up on the trigger pull until after that bump?

tiny mauve
#

Edit profile, controller mappings, deadzones, triggers 😉
Best of luck figuring out your sweet spot

#

The alternative you clearly don't want imo (would be a mess to handle properly and efficiently)

#

As for your mod question in #💬┃general , mods usually come with install/usage instructions or have them on the page you download them from.
Usually clear enough to be easily applied by users.
If you've never enabled dsx mod system in 3.1 though, go to settings, networking then do the firewall exception step and enable incoming UDP. You'll be all set, provided the mods are properly set up with the relevant port number (dsx default is 6969 - which most mods use by default anyway)

fast cargo
fast cargo
tiny mauve
#

Hmm, @lost palm might have mentioned these not working properly in all cases recently on some other ticket but I can't recall exactly.
Or maybe it was just about the sensitivity/saturation options not being available for triggers.. really can't remember

tiny mauve
tiny mauve
fast cargo
tiny mauve
#

Only you can know whether that profile is the one you try to use 😅

fast cargo
#

Oh, I haven't even bothered making a new one yet

#

So any edits I've done have been to the default

tiny mauve
#

Got it, so no bother with "have you made sure you're not in just edit mode" 😊

#

I'll give it a try when I'm on my PC again if no one has by then

fast cargo
#

Appreciated, thanks!

tiny mauve
#

But in the meantime, try some different emu modes or some other stuff in conjunction just to maybe figure something out

fast cargo
#

Oh for sure. My background is actually originally in games QA, so I'm very used to the "try flipping all the switches, work out a consistent set of steps to repro" mindset

tiny mauve
#

And maybe actually make another profile, just to switch between two cause there was issues with some stuff not applying on the fly but did when switching profiles

tiny mauve
fast cargo
#

Alrighty, been messing with it some and I think the issue is DSX just not wanting to play nicely with Steam Input. If I toggle Steam Input off entirely, the trigger deadzone works. If I enable it, it ignores it entirely (and also seems to ignore controller emulation - I have it set to 360, which has no gyro input, but it still treats it as seeing my full gyro-to-mouse setup from my Dualsense profile)

tiny mauve
#

Sorry I should have asked you about SI...

#

I killed it a while back so it never messes with anything

#

Glad it's an easy solution though

#

(well that's mostly because both SI & DSX are in partial control of the DS.. F steam input)

fast cargo
#

The issue is that Steam Input is the primary method of getting any kind of gyro inserted, which is one of the prime use cases for when I'm doing controller for a shooter in the first place :(

If the two are just fundamentally incompatible, though, that's a shame

tiny mauve
#

Blame Valve

#

But better yet, wait for DSX gyro modes

#

Coming soon ™

fast cargo
#

Just a quick follow-up - found a threshold setting for triggers in Steam Input as well, so (while the in-DSX one won't work with it) it's still possible to adjust that threshold to below the trigger bump 👍