Page 1 of 1

Questions / requests for the Input Translator

PostPosted: Wed Nov 27, 2019 10:35 am
by bt1740
1) Is it possible to add some sort of delay for the mouse section becore the 'Alternate' config activates? For example, like on a xim device there is the HIP and then the ADS with delay. Just a thought on if this was possible, it would lead to more customization.
2) Also wondering if it were possible to add multiple mouse configs every button? Why stop at 2? For example, there is the 'Default' config and you can set an 'Alternate' config. But what if I want a third config acting as a sniper button on my mouse, or a second config for when I'm in vehicles and need a higher sens, or maybe someone would want one alternate config for ADS and another alternate config for when they actually start shooting (and in this scenario default is non ads).
3) Is there a tutorial anywhere going over the mouse section in particular? I know there is a crash course on the Input Translator in general, but are there any posts detailing an explanation on the deadzone values, what they do, how DD works, etc?

Thanks! Appreciate the help in advance.

Re: Questions / requests for the Input Translator

PostPosted: Thu Nov 28, 2019 9:38 am
by J2Kbr
bt1740 wrote:1) Is it possible to add some sort of delay for the mouse section becore the 'Alternate' config activates? For example, like on a xim device there is the HIP and then the ADS with delay. Just a thought on if this was possible, it would lead to more customization.

This would be possible via scripting using the mxyconverter() GPC function, example:
Code: Select all
const uint8 mouse_hip[] = {
    0xFF, 0x01, 0x66, 0x01, 0x9C, 0x00, 0x33, 0x0B, 0x5E, 0x0B, 0x5E, 0x00,
    0xAA, 0x00, 0x00, 0x17, 0x87, 0x20, 0x28, 0x26, 0x6E, 0x2B, 0xEB, 0x30,
    0xA1, 0x33, 0xC2, 0x37, 0xAE, 0x3A, 0xD1, 0x3D, 0xF5, 0x40, 0x4F, 0x43,
    0x73, 0x45, 0xCC, 0x48, 0xF0, 0x4B, 0x4A, 0x4D, 0xA3, 0x50, 0x00, 0x52,
    0x59, 0x54, 0xB3, 0x56, 0x45, 0x58, 0xA1
};
 
const uint8 mouse_ads[] = {
    0xFF, 0x01, 0x66, 0x01, 0x9C, 0x00, 0x33, 0x0B, 0x5E, 0x0B, 0x5E, 0x00,
    0xAA, 0x00, 0x00, 0x17, 0x87, 0x20, 0x28, 0x26, 0x6E, 0x2B, 0xEB, 0x30,
    0xA1, 0x33, 0xC2, 0x37, 0xAE, 0x3A, 0xD1, 0x3D, 0xF5, 0x40, 0x4F, 0x43,
    0x73, 0x45, 0xCC, 0x48, 0xF0, 0x4B, 0x4A, 0x4D, 0xA3, 0x50, 0x00, 0x52,
    0x59, 0x54, 0xB3, 0x56, 0x45, 0x58, 0xA1
};
 
bool ads_flag;
 
main {
    if(event_release(BUTTON_8)) {
        if(ads_flag) {
            mxyconverter(mouse_hip);
            ads_flag = FALSE;
        }
    } else if(check_active(BUTTON_8, 250)) {
        if(!ads_flag) {
            mxyconverter(mouse_ads);
            ads_flag = TRUE;
        }
    }
}
 


bt1740 wrote:2) Also wondering if it were possible to add multiple mouse configs every button? Why stop at 2? For example, there is the 'Default' config and you can set an 'Alternate' config. But what if I want a third config acting as a sniper button on my mouse, or a second config for when I'm in vehicles and need a higher sens, or maybe someone would want one alternate config for ADS and another alternate config for when they actually start shooting (and in this scenario default is non ads).

The above example could be extended to have as many mouse configs as you need. :smile0517:

bt1740 wrote:3) Is there a tutorial anywhere going over the mouse section in particular? I know there is a crash course on the Input Translator in general, but are there any posts detailing an explanation on the deadzone values, what they do, how DD works, etc?

We don't have tutorials for mouse configuration. I have this in my to do list, but unfortunately didn't find time yet to make it.

Re: Questions / requests for the Input Translator

PostPosted: Thu Nov 28, 2019 4:24 pm
by bt1740
Thanks! That clears a lot up. I guess this isn't the right sub for this question, but:

Do you know of any antirecoil script (preferably just code so I can tinker with it and add it to my script and not a gamepack) that doesn't restrict your vertical axis aim? I've tried a couple, but the problem I have with them is that if you snap down with your aim (for example if the enemy is laying on the ground) itll pull wayy too down, and if you try to snap up it wont let you. Micro movements on the Y axis are hard to do also.

I am connecting my mouse directly to the T2 if that helps. Thanks!

Re: Questions / requests for the Input Translator

PostPosted: Thu Nov 28, 2019 4:32 pm
by bt1740
J2Kbr wrote:
bt1740 wrote:1) Is it possible to add some sort of delay for the mouse section becore the 'Alternate' config activates? For example, like on a xim device there is the HIP and then the ADS with delay. Just a thought on if this was possible, it would lead to more customization.

This would be possible via scripting using the mxyconverter() GPC function, example:
Code: Select all
const uint8 mouse_hip[] = {
    0xFF, 0x01, 0x66, 0x01, 0x9C, 0x00, 0x33, 0x0B, 0x5E, 0x0B, 0x5E, 0x00,
    0xAA, 0x00, 0x00, 0x17, 0x87, 0x20, 0x28, 0x26, 0x6E, 0x2B, 0xEB, 0x30,
    0xA1, 0x33, 0xC2, 0x37, 0xAE, 0x3A, 0xD1, 0x3D, 0xF5, 0x40, 0x4F, 0x43,
    0x73, 0x45, 0xCC, 0x48, 0xF0, 0x4B, 0x4A, 0x4D, 0xA3, 0x50, 0x00, 0x52,
    0x59, 0x54, 0xB3, 0x56, 0x45, 0x58, 0xA1
};
 
const uint8 mouse_ads[] = {
    0xFF, 0x01, 0x66, 0x01, 0x9C, 0x00, 0x33, 0x0B, 0x5E, 0x0B, 0x5E, 0x00,
    0xAA, 0x00, 0x00, 0x17, 0x87, 0x20, 0x28, 0x26, 0x6E, 0x2B, 0xEB, 0x30,
    0xA1, 0x33, 0xC2, 0x37, 0xAE, 0x3A, 0xD1, 0x3D, 0xF5, 0x40, 0x4F, 0x43,
    0x73, 0x45, 0xCC, 0x48, 0xF0, 0x4B, 0x4A, 0x4D, 0xA3, 0x50, 0x00, 0x52,
    0x59, 0x54, 0xB3, 0x56, 0x45, 0x58, 0xA1
};
 
bool ads_flag;
 
main {
    if(event_release(BUTTON_8)) {
        if(ads_flag) {
            mxyconverter(mouse_hip);
            ads_flag = FALSE;
        }
    } else if(check_active(BUTTON_8, 250)) {
        if(!ads_flag) {
            mxyconverter(mouse_ads);
            ads_flag = TRUE;
        }
    }
}
 





Also just to clarify,
Would I need to run an input translator file on the slot if I am doing it this way?
And, lets say 1 config for HIP and one for ADS (right click) and one for when I start shooting.. so instead of having a config for mouse_HIP and mouse_ADS like in the code provided,

can I just set a HIP sens in the input translator, set an ADS sens in the input translator, and then in code I could include the left click(or PS4_R2 not sure which button # it is atm) config? And change the code for it to activate when I press R2?

Re: Questions / requests for the Input Translator

PostPosted: Fri Nov 29, 2019 9:14 am
by J2Kbr
bt1740 wrote:I am connecting my mouse directly to the T2 if that helps. Thanks!

In this case the best way (really) is use the GPC functions:
mxyconverter_voffset()
mxyconverter_hoffset()

Re: Questions / requests for the Input Translator

PostPosted: Fri Nov 29, 2019 9:18 am
by J2Kbr
bt1740 wrote:Would I need to run an input translator file on the slot if I am doing it this way? And, lets say 1 config for HIP and one for ADS (right click) and one for when I start shooting.. so instead of having a config for mouse_HIP and mouse_ADS like in the code provided,

No need for GIT file, in this case the Input Translator data is embedded in the script.

bt1740 wrote:can I just set a HIP sens in the input translator, set an ADS sens in the input translator, and then in code I could include the left click(or PS4_R2 not sure which button # it is atm) config? And change the code for it to activate when I press R2?

All input translators variants needs to be in the script. If you load an external git file, the script will not be able to load any input translator and the GPC function mxyconverter() will return FALSE.