KrossX's Magical Tools™

Any plans on adding editable trigger ranges for pokopom and duranzo?

Why it's needed:

Without Wedge Helper:
http://imageshack.us/a/img197/7808/su8d.jpg

With Wedge Helper:
http://imageshack.us/a/img29/4929/7xwd.jpg


See how this would help with the vast amount of games that don't deal with trigger ranges?

If so, an editable range while pressing down (activation) and a 2nd editable range for releasing (deactivation) would be nice for those who don't want to use a wedge. And both buttons would share the same editable ranges.

This is desired for games that require rapid presses without the huge angle of the triggers. When pressing a button, I find myself not fully releasing the trigger and then when I need to come back to press it, the move never comes out because I'm still slightly holding the trigger. So the input doesn't register because I never fully released the trigger.

Untouched it is 0. Pressed fully it is 255.

I mentioned 2 values because if someone doesn't want to use the wedges, they may want a different value when pressed and a different one to tell the controller to release. I myself am disputing between just 1 notch for press or half of 255 for press and just half of 255 going back up when releasing (without wedges). I don't know if there is a way to detect when you are pressing and when you are releasing or not. If not, just ignore this paragraph.

It is not a problem with your tools at all, it is triggers in general. I hate them lol. I get that problem by default and I mentioned this to see if I can get a remedy. It's messing up my online play on PC games with fighters and it gives me a hard time in action oriented emulation. And I don't like playing with fight sticks.

But my comfort resting position with the wedges are 235 (when I line it up with the L1R1 buttons physically). That way I won't have far to go to actually press it in full (like a button). Going above 235 in squeeze for me should activate the button if you were to make this a configurable number option inside of the .ini only. But of course different ppl may want different values for themselves hence the user inputting their own value.
(^I think I answered your question correctly here lol. Pardon me if I didn't. Also, sorry for the wait. I had to head off to work earlier.)

Wedges = pic 2, post 42. Keeps the trigger held down low (makes it into a button instead of a trigger like a ps2 controller). If I have the ability to change the press of the initiation, then I can make that wedge work. Going below 235 will do nothing. Going above 235 would initiate the button press. Yeah, I don't want the 235 to become the standard, I just want it to become adjustable.



If not using the wedges like pic 1 post 42, I'm asking that a customizable press for pressing down and a separate customizable number for releasing the trigger. Say like if a person is okay with the button being activated at pressure 1 on press but don't like the button to say it is not pressed at pressure 1 but at pressure 125 instead. That means when they release the trigger, they want the trigger to say it is not pressed early, getting rid of the problem I mentioned earlier (if not using the wedges).

For example (inside .ini only):

triggerpressure=10
triggerrelease=128

This would mean for both of the triggers, the action performed on the game will initiate when your press is 10 or greater. But when you release the trigger, the trigger press will be over half way before you fully release the trigger.
*These 2 lines would apply to both triggers - no need for 4 lines to do both triggers individually*

triggerpressure=128
triggerrelease=128

Would mean that the press is activated when the trigger is held half way down and above, and when you release the trigger half way up, the press is deactivated.

triggerpressure=15
triggerrelease=130

In these 2 lines, on press ~ 0-14 would be 'the deadzone' so to speak. On release ~ 0-129 would be 'the deadzone'.


So is that even possible to detect when trigger is pressed/released separately like that in order to create those 2 options?





If that is not possible, then I request (inside .ini only):

triggerpressure=

In order to tell the game that the trigger(s) are considered pressed at a certain pressure.

For pic 2 post 42, 'triggerpressure=' would be 'triggerpressure=236'. That's where I got that number 235 from.



Get me now?

Hey, Kross.
I've been using this program called Autohidmousecursor and it looks like this:



It is a small program without the need of an installation. The only downside to it is that it doesn't have the ability to look at a whitelist in order to only make the mouse cursor disappear only on certain programs.

Can you put hiding the cursor in insomnia to consolidate these features?

HideMouseCursor= 'removes cursor completely (can still use mousewheel if used'

HideCursorWhitelist= 'makes hiding the cursor only happen during items in current whitelist'

HideCursorTimer= 'idle time before mouse cursor hides'

Whether you want to make it show in the gui is up to you, but can you put this in the .ini?

Sorry to bug you Kross, but I was playing SSF4 again online and my logitech controller is kinda losing its grip with the analog triggers. The L2 trigger keeps pressing by itself because it has gotten loose from gameplay. It's also affecting every game I play for PC as well. So if you aren't that busy or are taking a break in between what you are working on now, how 'bout those deadzone trigger settings for durazno (puts up firaga shield)?