[GCV/GPC] Apex Legends CV Anti-Recoil
Re: [GCV/GPC] Apex Legends CV Anti-Recoil
I'd love to see this in action too before I invest in a capture card :D
Cheers!
Cheers!
-
Jaxstevens83 - Private
- Posts: 1
- Joined: Wed May 27, 2020 4:51 pm
Re: [GCV/GPC] Apex Legends CV Anti-Recoil
Hello friends, I just tried this script in my T2 with stock controller in my ps4 and every thing works expect anti- recoil, please help
-
God of War - Corporal
- Posts: 4
- Joined: Thu May 28, 2020 6:07 pm
Re: [GCV/GPC] Apex Legends CV Anti-Recoil
God of War wrote:Hello friends, I just tried this script in my T2 with stock controller in my ps4 and every thing works expect anti- recoil, please help
DId you do the Computer Vision assisted Anti recoil? With capture card or ps remote / xbox stream?
-
dan_94 - Master Sergeant
- Posts: 28
- Joined: Sat Aug 11, 2018 6:07 am
Re: [GCV/GPC] Apex Legends CV Anti-Recoil
kevshen wrote:Awesome man. I think i will just hang on then. Been spending more time tinkering with it than actually playing lol. Appreciate the awesome work you guys do and the time it takes to do it . This GCV stuff is crazy. Its actually still really playable with the xim at medium to long range. But close quarters is near on impossible to track targets. Will use the game packs normal versatile AR for now and keep an eye on these forums
Thanks
Your problem with AR is that you are have to change the 1.00 values way lower. There i want J2kr mention this for the setup mouse and KB --- Titan 2 (native mouse) --- XIM --- Console. I am playing around in between 0.1 and 0.15. So i really dont know why but you can say you have to divide it by 10 when using this setup instead of a controller. Maybe caused by the mouse dpi? I a playing with 16000.
The problem with rapid fire is that for some reason the values in wait(24) and wait (16) dont work with Mulit interface output. You have to go to atleast 60ms so change the numbers both to 60 instead of 24 and 16 and it will work fine.
Greetings
-
dan_94 - Master Sergeant
- Posts: 28
- Joined: Sat Aug 11, 2018 6:07 am
Re: [GCV/GPC] Apex Legends CV Anti-Recoil
For the XIM to Titan to Console stiffness: I disabled the AR when your actual sens goes beyond the aim correction. Makes the aiming easier. Further added a y_sens multiplication for downwards movement.
- Code: Select all
bool rapidfire;
fix32 stick_1_x, stick_1_y;
fix32 y_sens = 1.3;
main {
if(gcv_ready()) {
switch(gcv_read(0)) {
case 0: {
rapidfire = gcv_read(1);
} break;
case 1: {
gcv_read(1, &stick_1_x);
gcv_read(5, &stick_1_y);
} break;
case 2: {
int16 hoffset, voffset;
gcv_read(1, &hoffset);
gcv_read(3, &voffset);
mxyconverter_hoffset(hoffset);
mxyconverter_voffset(voffset);
} break;
}
}
if(get_actual(BUTTON_5)) {
if (stick_1_y == 0.0 && get_actual(STICK_1_Y) > 0.0) {set_val(STICK_1_Y, clamp(get_val(STICK_1_Y) * y_sens, -100.0, 100.0));}
if (abs(get_actual(STICK_1_X)) > stick_1_x) {stick_1_x = 0.0;}
if (abs(get_actual(STICK_1_Y)) > stick_1_y) {stick_1_y = 0.0;}
if(stick_1_x || stick_1_y) {
set_val(STICK_1_X, clamp(get_val(STICK_1_X) + stick_1_x, -100.0, 100.0));
set_val(STICK_1_Y, clamp(get_val(STICK_1_Y) + stick_1_y, -100.0, 100.0));
}
if(rapidfire) {
combo_run(Rapidfire);
}
} else if(event_release(BUTTON_5)) {
stick_1_x = stick_1_y = 0.0;
mxyconverter_hoffset(0);
mxyconverter_voffset(0);
combo_stop(Rapidfire);
}
}
combo Rapidfire {
set_val(BUTTON_5, 100.0);
wait(24);
set_val(BUTTON_5, 0.0);
wait(16);
}
-
dan_94 - Master Sergeant
- Posts: 28
- Joined: Sat Aug 11, 2018 6:07 am
Re: [GCV/GPC] Apex Legends CV Anti-Recoil
dan_94 wrote:For the XIM to Titan to Console stiffness: I disabled the AR when your actual sens goes beyond the aim correction. Makes the aiming easier. Further added a y_sens multiplication for downwards movement.
- Code: Select all
bool rapidfire;
fix32 stick_1_x, stick_1_y;
fix32 y_sens = 1.3;
main {
if(gcv_ready()) {
switch(gcv_read(0)) {
case 0: {
rapidfire = gcv_read(1);
} break;
case 1: {
gcv_read(1, &stick_1_x);
gcv_read(5, &stick_1_y);
} break;
case 2: {
int16 hoffset, voffset;
gcv_read(1, &hoffset);
gcv_read(3, &voffset);
mxyconverter_hoffset(hoffset);
mxyconverter_voffset(voffset);
} break;
}
}
if(get_actual(BUTTON_5)) {
if (stick_1_y == 0.0 && get_actual(STICK_1_Y) > 0.0) {set_val(STICK_1_Y, clamp(get_val(STICK_1_Y) * y_sens, -100.0, 100.0));}
if (abs(get_actual(STICK_1_X)) > stick_1_x) {stick_1_x = 0.0;}
if (abs(get_actual(STICK_1_Y)) > stick_1_y) {stick_1_y = 0.0;}
if(stick_1_x || stick_1_y) {
set_val(STICK_1_X, clamp(get_val(STICK_1_X) + stick_1_x, -100.0, 100.0));
set_val(STICK_1_Y, clamp(get_val(STICK_1_Y) + stick_1_y, -100.0, 100.0));
}
if(rapidfire) {
combo_run(Rapidfire);
}
} else if(event_release(BUTTON_5)) {
stick_1_x = stick_1_y = 0.0;
mxyconverter_hoffset(0);
mxyconverter_voffset(0);
combo_stop(Rapidfire);
}
}
combo Rapidfire {
set_val(BUTTON_5, 100.0);
wait(24);
set_val(BUTTON_5, 0.0);
wait(16);
}
I’d like to give this a shot, at least until j2k comes out with his fix.
Where exactly am I dropping the code, though?
-
GGsUK - First Sergeant
- Posts: 52
- Joined: Wed Nov 20, 2019 5:50 pm
Re: [GCV/GPC] Apex Legends CV Anti-Recoil
Evening all, is it normal for the graphics to look kinda grainy in the computer vision feed? it sure doesn't look like 1080p quality either way, I have the GC311, ive tried various settings with no success in the quality aspect.
thanks!
thanks!
-
Benj91 - Staff Sergeant
- Posts: 11
- Joined: Thu Apr 30, 2020 8:40 pm
Re: [GCV/GPC] Apex Legends CV Anti-Recoil
attached is the configurable settings within the CV, would changing any of these make a difference?
- Attachments
-
- gcv.png (39.42 KiB) Viewed 3961 times
-
Benj91 - Staff Sergeant
- Posts: 11
- Joined: Thu Apr 30, 2020 8:40 pm
Re: [GCV/GPC] Apex Legends CV Anti-Recoil
dan_94 wrote:kevshen wrote:Awesome man. I think i will just hang on then. Been spending more time tinkering with it than actually playing lol. Appreciate the awesome work you guys do and the time it takes to do it . This GCV stuff is crazy. Its actually still really playable with the xim at medium to long range. But close quarters is near on impossible to track targets. Will use the game packs normal versatile AR for now and keep an eye on these forums
Thanks
Your problem with AR is that you are have to change the 1.00 values way lower. There i want J2kr mention this for the setup mouse and KB --- Titan 2 (native mouse) --- XIM --- Console. I am playing around in between 0.1 and 0.15. So i really dont know why but you can say you have to divide it by 10 when using this setup instead of a controller. Maybe caused by the mouse dpi? I a playing with 16000.
The problem with rapid fire is that for some reason the values in wait(24) and wait (16) dont work with Mulit interface output. You have to go to atleast 60ms so change the numbers both to 60 instead of 24 and 16 and it will work fine.
Greetings
I actually found this as well with the H_SCALE values after I was last on. Same as yourself only I'm using 4000 DPI but 0.08 - 0.1 felt best. Never knew about the rapidfire timings. Will give the code you posted a try next time I'm on
Thanks
-
kevshen - Corporal
- Posts: 4
- Joined: Mon May 25, 2020 5:10 pm
Re: [GCV/GPC] Apex Legends CV Anti-Recoil
RobEngle93 wrote:dan_94 wrote:For the XIM to Titan to Console stiffness: I disabled the AR when your actual sens goes beyond the aim correction. Makes the aiming easier. Further added a y_sens multiplication for downwards movement.
- Code: Select all
bool rapidfire;
fix32 stick_1_x, stick_1_y;
fix32 y_sens = 1.3;
main {
if(gcv_ready()) {
switch(gcv_read(0)) {
case 0: {
rapidfire = gcv_read(1);
} break;
case 1: {
gcv_read(1, &stick_1_x);
gcv_read(5, &stick_1_y);
} break;
case 2: {
int16 hoffset, voffset;
gcv_read(1, &hoffset);
gcv_read(3, &voffset);
mxyconverter_hoffset(hoffset);
mxyconverter_voffset(voffset);
} break;
}
}
if(get_actual(BUTTON_5)) {
if (stick_1_y == 0.0 && get_actual(STICK_1_Y) > 0.0) {set_val(STICK_1_Y, clamp(get_val(STICK_1_Y) * y_sens, -100.0, 100.0));}
if (abs(get_actual(STICK_1_X)) > stick_1_x) {stick_1_x = 0.0;}
if (abs(get_actual(STICK_1_Y)) > stick_1_y) {stick_1_y = 0.0;}
if(stick_1_x || stick_1_y) {
set_val(STICK_1_X, clamp(get_val(STICK_1_X) + stick_1_x, -100.0, 100.0));
set_val(STICK_1_Y, clamp(get_val(STICK_1_Y) + stick_1_y, -100.0, 100.0));
}
if(rapidfire) {
combo_run(Rapidfire);
}
} else if(event_release(BUTTON_5)) {
stick_1_x = stick_1_y = 0.0;
mxyconverter_hoffset(0);
mxyconverter_voffset(0);
combo_stop(Rapidfire);
}
}
combo Rapidfire {
set_val(BUTTON_5, 100.0);
wait(24);
set_val(BUTTON_5, 0.0);
wait(16);
}
I’d like to give this a shot, at least until j2k comes out with his fix.
Where exactly am I dropping the code, though?
Its just the gpc to run instead of the gamepack. Run this script and the computer vision one and it will work with AR und rapidfire for Xim connected to TItan 2 (with PS4 output). Its far away from perfect but it helps a little.
-
dan_94 - Master Sergeant
- Posts: 28
- Joined: Sat Aug 11, 2018 6:07 am
Return to Gtuner Computer Vision
Who is online
Users browsing this forum: No registered users and 103 guests