XIM Community

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - r0ger

Pages: 1 2 [3]
31
XIM APEX Discussions / Re: Sony NAV Alternatives?
« on: 11:16 AM - 01/14/21 »
Yes there is, the Wii Chuck, i use a ADAP-1X-WUSBMOTE_V3, its adapter allows 1ms polling rate and its wired, faster than Navigation controller but doesnt have the directional pad.

32
What mouse do you use? Is there any way you could go to the mouse software and disable the DPI change buttons? Does your mouse have onboard memory? like Razor or Logitech?

33
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)

34
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.

35
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.

36
Shared Configs / Re: Urizuku's Destiny 2 Config
« on: 12:15 PM - 01/13/21 »
I have the perfect config. I will be posting here soon. But Apex Xim Beta needs a feature that allows the mouse x and y movements to be individually capped at at a percentage. this Input Translator is good but Apex Xim is missing an advanced feature that would benefit Destiny 2.

37
The main problem is Input Translators, I want to cap the analog sticks at 75% x and 75% y. But because all input translators are based on 0% to 100%, I get inaccurate mouse movement because it always wants to go past 100%, in terms of your sensitivity. Capping the x or y axis at percentages could be a breakthrough for some game like Destiny 2, because the Apex Xim translator is broken for that game because making the X axis perfect makes the Y axis go way to fast.

the X/Y ratio does nothing because the ballistics curve X and Y are still the same and you can only cap both at once.

Another reason I suggest this feature is because fast mouse movement is ever so inconsistent, a maximum threshold would simulate analog movement at the capped speed, in FPS games, you could predict the hit rather than rely on the slowdown of the mouse which might not work in all games.

38
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!

Pages: 1 2 [3]
Admin