Guys, would you help me test my new anti-recoil script?

[Syaoran]

I don't have the ability to record video's unfortunately, but the issue has been noted by Antithesis on his Antithesis Antirecoil script dated the 2nd of May 2018, "The advantage of using this antirecoil script is the reticle doesn't drop to the floor on intentional downwards movements. This happens because antirecoil stacks with movement. I added checks to the scripts to prevent that from happening".

This issue has also been address in Bonefiser latest bf5 script by adding the "minimum percentage of anti recoil to apply during aim stick movements." and by JSkbr on his BF5 script by adding the "Anti-recoil deadzone compensation" check box.

Both of there scripts work great, but I find yours seems to create more of a laser when using the M1A1. I'm also finding I can't use melee attacks with your script but for using an M1A1 like a laser, it's a small price to pay.

[Gjin Yuko]

How can i find out the Deadzones for other Games?

and melee attacks doesnt work..

[Mad]

How can i find out the Deadzones for other Games?

Code: Select all

#pragma METAINFO("X/Y Dz Test", 1, 0, "Mad")
/*
Use the Dpad (Tap or Hold) to adjust the value until the camera only slightly moves on its own.
 
Left++ or Right-- for testing X
 
Up++   or Down--  for testing Y
 
Tap Y or Triangle to print out the value in Gtuner once you are done.
*/
 
// Set a base value for either X or Y to start with
fix32 DZ_X = 0.0;
fix32 DZ_Y = 12.00;
 
main {
  block();
 
  set_val(21, DZ_X);
  set_val(22, DZ_Y);
 
  if (is_active(9) || is_active(10)) inc_dec(&DZ_Y);
  if (is_active(11) || is_active(12)) inc_dec(&DZ_X);
 
  if (event_active(13)) printf("X: <b>%.2f</b> Y: <b>%.2f", DZ_X, DZ_Y);
}
 
void block() {
  int8 i = 9;
  for(;i < 13; ++i) inhibit(i, -1);
}
 
void inc_dec(fix32* i){
  if (!(system_time()%160)) {
    *i += ((is_active(9) || is_active(11)) ? 0.01 : -0.01);
  }
  return;
}

[Gjin Yuko]

How can i find out the Deadzones for other Games?

Code: Select all

#pragma METAINFO("X/Y Dz Test", 1, 0, "Mad")
/*
Use the Dpad (Tap or Hold) to adjust the value until the camera only slightly moves on its own.
 
Left++ or Right-- for testing X
 
Up++   or Down--  for testing Y
 
Tap Y or Triangle to print out the value in Gtuner once you are done.
*/
 
// Set a base value for either X or Y to start with
fix32 DZ_X = 0.0;
fix32 DZ_Y = 12.00;
 
main {
  block();
 
  set_val(21, DZ_X);
  set_val(22, DZ_Y);
 
  if (is_active(9) || is_active(10)) inc_dec(&DZ_Y);
  if (is_active(11) || is_active(12)) inc_dec(&DZ_X);
 
  if (event_active(13)) printf("X: <b>%.2f</b> Y: <b>%.2f", DZ_X, DZ_Y);
}
 
void block() {
  int8 i = 9;
  for(;i < 13; ++i) inhibit(i, -1);
}
 
void inc_dec(fix32* i){
  if (!(system_time()%160)) {
    *i += ((is_active(9) || is_active(11)) ? 0.01 : -0.01);
  }
  return;
}

Thanks! But when i press Dpad nothing moves..

[Mad]

That means you're still inside the deadzone.

It previously increased/decreased at a rate of 0.01 so it was pretty slow, I've changed it to 0.25 to make it easier and you can adjust that at the top of the script.

Code: Select all

#pragma METAINFO("X/Y Dz Test", 1, 0, "Mad")
/*
Use the Dpad (Tap or Hold) to adjust the value until the camera only slightly moves on its own.
 
Left++ or Right-- for testing X
 
Up++   or Down--  for testing Y
 
Tap Y or Triangle to print out the value in Gtuner once you are done.
*/
#define RATE 0.25
 
fix32 DZ_X = 0.0;
fix32 DZ_Y = 12.00;
 
main {
  block();
 
  set_val(21, DZ_X);
  set_val(22, DZ_Y);
 
  if (is_active(9) || is_active(10)) inc_dec(&DZ_Y);
  if (is_active(11) || is_active(12)) inc_dec(&DZ_X);
 
  if (event_active(13)) printf("X: <b>%.2f</b> Y: <b>%.2f", DZ_X, DZ_Y);
}
 
void block() {
  int8 i = 9;
  for(;i < 13; ++i) inhibit(i, -1);
}
 
void inc_dec(fix32* i){
  if (!(system_time()%160)) {
    *i += ((is_active(9) || is_active(11)) ? RATE : -RATE);
  }
  return;
}

[Gjin Yuko]

That means you're still inside the deadzone.

It previously increased/decreased at a rate of 0.01 so it was pretty slow, I've changed it to 0.25 to make it easier and you can adjust that at the top of the script.

Code: Select all

#pragma METAINFO("X/Y Dz Test", 1, 0, "Mad")
/*
Use the Dpad (Tap or Hold) to adjust the value until the camera only slightly moves on its own.
 
Left++ or Right-- for testing X
 
Up++   or Down--  for testing Y
 
Tap Y or Triangle to print out the value in Gtuner once you are done.
*/
#define RATE 0.25
 
fix32 DZ_X = 0.0;
fix32 DZ_Y = 12.00;
 
main {
  block();
 
  set_val(21, DZ_X);
  set_val(22, DZ_Y);
 
  if (is_active(9) || is_active(10)) inc_dec(&DZ_Y);
  if (is_active(11) || is_active(12)) inc_dec(&DZ_X);
 
  if (event_active(13)) printf("X: <b>%.2f</b> Y: <b>%.2f", DZ_X, DZ_Y);
}
 
void block() {
  int8 i = 9;
  for(;i < 13; ++i) inhibit(i, -1);
}
 
void inc_dec(fix32* i){
  if (!(system_time()%160)) {
    *i += ((is_active(9) || is_active(11)) ? RATE : -RATE);
  }
  return;
}

Thanks it works now! But how can i see the value in Gtuner after i pressed Y?

[Mad]

Thanks it works now! But how can i see the value in Gtuner after i pressed Y?

Make sure the T2 is connected to the PC via the prog port.

output.png (5.12 KiB) Viewed 2466 times

If you cant see the output panel; Gtuner>View>Output Panel

[ycksy]

Thanks it works now! But how can i see the value in Gtuner after i pressed Y?

Make sure the T2 is connected to the PC via the prog port.
If you cant see the output panel; Gtuner>View>Output Panel

For XIM apex users; our in app default "deadzones" are "7500" for left stick and right stick. Should we still use the deadzone script to find the appropriate number? I've noticed scripts cap deadzone at "25" before, so 7500 seemed like a ludicrous number to translate. I haven't tried your script yet, but should XIM users also use the script to find the deadzone and ignore the XIM app's deadzone? Thank you.

[DrNefario]

Thanks it works now! But how can i see the value in Gtuner after i pressed Y?

Make sure the T2 is connected to the PC via the prog port.
If you cant see the output panel; Gtuner>View>Output Panel

For XIM apex users; our in app default "deadzones" are "7500" for left stick and right stick. Should we still use the deadzone script to find the appropriate number? I've noticed scripts cap deadzone at "25" before, so 7500 seemed like a ludicrous number to translate. I haven't tried your script yet, but should XIM users also use the script to find the deadzone and ignore the XIM app's deadzone? Thank you.

Are you sure we can adjust deadzones in our xim apex app? I cant find any deadzone settings in my app.

[Gjin Yuko]

Thanks it works now! But how can i see the value in Gtuner after i pressed Y?

Make sure the T2 is connected to the PC via the prog port.
If you cant see the output panel; Gtuner>View>Output Panel

For XIM apex users; our in app default "deadzones" are "7500" for left stick and right stick. Should we still use the deadzone script to find the appropriate number? I've noticed scripts cap deadzone at "25" before, so 7500 seemed like a ludicrous number to translate. I haven't tried your script yet, but should XIM users also use the script to find the deadzone and ignore the XIM app's deadzone? Thank you.

Yeah you should because the Xim just acts like a controller