Topics

1

Feedback / Fix for weird Input Translator behavior at high sensitivities

« on: 08:12 PM - 01/16/21 »

I found a solution to the behaviors of Input Translators. Go through all the games and find one with an Axis that is the same for X and Y. Otherwise, you are going to have problems when you flick your wrist because the input translators will keep going in the other axis when one reaches its hardware cap. I must warn you to test your ballistics curves at 50, if you get disportions, you won't notice problems unless you are at the high hill of the ballistics curves. This is an easy fix if you could just cap the other analog X/Y axis when one gets to maximum analog acis throttle, instead of slowing both, you get erratic aim. I had to use the Gotham City: Imposters Input Translators. Unless Apex Xim supports abnormal X and Y translators a little better and adds features for them, you will continue to see problems at 120fps games and near the peak of ballistics curves. Good luck guys.

2

Support / Xim needs X and Y capping feature

« on: 05:27 PM - 01/16/21 »

I am currently using a Titan Two Tuner with Apex Xim because Apex Xim doesnt have a feature to throttle X and Y axis to a minimum percentage. Why isn't there a single feature that helps with the outer threshold of analog sticks and input translators? A feature that helps keep an axis low when the other x/y axis reaches maximum? lets say the Y percentage goes maximum and the X is still at 83%, why on earth should the 83% allowed to keep going higher? it causes aim inconsistencies. Please fix your product as it doesn't work accurately with all input translators. Don't blame the input translator when I see hardware limitations are being reached.

3

Support / [Q/A] X and Y values causing problems

« on: 03:45 PM - 01/15/21 »

I am having problem with the Destiny 2 input translator. The X axis is too slow. When you correct it, it has problems maximum sensitivity. It seems like the input translator is the problem itself because a ballistics curve at 50% high has non-equal X and Y values when reaching peak sensivity. That is where the Y value goes maximum speed and the X doesnt want to. I feel the Xim Feature to cap ADS at an Axis like X or Y would fix problems in not just Destiny 2, but many input translators. No one has gotten back to me. Are you guys too busy or do you just not care or understand the logic here. I've seen significant improvements in your beta firmware and I am just trying to help. Thank you.

4

Feedback / Need ADS analog Axis Percentage Cap in Beta (repost) (put in the firmware beta?)

« on: 03:37 PM - 01/13/21 »

Input Translators have issues when reaching maximum sensivity. Once one Axis goes 100%, the other Axis keeps going up. Come on, can anyone reach out to me about implementing this in a beta? I want  a "Max X analog Percentage" and "Max Y Percentage" Give me this and I'll release good shared input translators for Apex Legends, Destiny 2, COD. I'll prove how viable this is. Can someone contact the firmware programmers?? Axis percentage need a cap like to never go past 75% on the Y Axis for example on ADS or Auxiliary. I can't fix Destiny 2's Horizonal Axis without ruining the vertical Axis. This would fix that game's translator, as you can see posts all over the place about problems with turn speed in Destiny 2. (this is my repost here)

5

Beta / Need ADS analog Axis Percentage Cap in Beta

« on: 03:33 PM - 01/13/21 »

Input Translators have issues when reaching maximum sensivity. Once one Axis goes 100%, the other Axis keeps going up. Come on, can anyone reach out to me about implementing this in a beta? I want  a "Max X analog Percentage" and "Max Y Percentage" Give me this and I'll release good shared input translators for Apex Legends, Destiny 2, COD. I'll prove how viable this is. Can someone contact the firmware programmers?? Axis percentage need a cap like to never go past 75% on the Y Axis for example on ADS or Auxiliary. I can't fix Destiny 2's Horizonal Axis without ruining the vertical Axis. This would fix that game's translator, as you can see posts all over the place about problems with turn speed in Destiny 2.

6

Beta / Apex Xim Feature: Maximum Threshold on X and Y Axis

« on: 12:27 PM - 01/13/21 »

Input Translators don't work well with ballistic curves cut off at the end, because one Axis reaches 100% and will continue percentage on the other axis.

Apex Xim needs a way to cap the maximum percentage of X or Y axis on the controller, because once the Input Translator goes between 80 and 100, there are inconsistency issues at high speeds, because the input translator wants to continue on one axis while the other reaches 100. Also not all games have detectable X and Y axis, brings the 2nd problem (the way game developers add acceleration or nullify maximum threshold. This creates a floating feeling once you are above 97% threshold of analog stick movement.

This is something that would benefit some games. This is as important as Call of Duty's ADS Deactivation Beta feature. It is a beta, it can be removed at anytime right? Could I get a closed beta to work with? If it works, I'll ask for the release.

7

Feedback / Apex Xim Feature: "Maximum Outer Threshold X" and "Maximum Outer Threshold Y %"

« on: 11:20 AM - 01/13/21 »

I would like to point out that this is a very important feature to consider. Because it would completely defeat aim acceleration in some games and would allow you to move in the opposite direction quicker, because you'd be closer to the opposite axis. bonus, you could increase some sensitivities in some games to the actual maximum and still feel the crosshairs are slower, and the aim acceleration reduced. these settings of course would just cut the threshold at the current ballistics curve position. Please consider!