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 - TeslaDev

Pages: [1] 2 3 ... 21
1
Did you set it up yesterday for the first time?  Did you increase the polling rate?  Did you forget to unplug and replug after changing the polling rate?

If not, check your mouse DPI and in-game sensitivity settings.

2
Great post.  I think more people should see this.

3
I have one - it works.

4
I recently changed from a G502 to a Rival 310 as the sensor in this is optimised for 1-1 movement for DPIís up to 3500 which is good for XIM Iíve found.

The feeling is awesome, without a doubt one of the best mice for this Apex. It goes up to 12K like the G502 but the G502 only provides true 1-1 upto about 2200 DPI Iíve read.

Not that it will make a huge difference, just thought Iíd add that in here.

The g502 uses the 3366 sensor, which is 1-1 all the way to 12k.  No smoothing steps either, for full range.
I'm sure the 3366 range adds 2 frames of smoothing from 2100. The TM3 goes up to 3500 before adding smoothing.

There's no way it goes all the way up to 12K DPI with no smoothing or jitter reduction.

Regardless, whether it's placebo or not I have found my aim to be more accurate in micro-movements since changing to the Rival 310.

It adds 2 frames for full range. 2 frames is like...less than 0.5 ms, or less than the update rate....  There is no stepping in smoothing with the 3366. It's effectively raw input.

5
I recently changed from a G502 to a Rival 310 as the sensor in this is optimised for 1-1 movement for DPIís up to 3500 which is good for XIM Iíve found.

The feeling is awesome, without a doubt one of the best mice for this Apex. It goes up to 12K like the G502 but the G502 only provides true 1-1 upto about 2200 DPI Iíve read.

Not that it will make a huge difference, just thought Iíd add that in here.

The g502 uses the 3366 sensor, which is 1-1 all the way to 12k.  No smoothing steps either, for full range.

6
Also - make sure you're not using angle snapping. Some people like it - I don't, it feels "notchy" to me using angle snapping.

7
Also - posting what mouse you're using can help troubleshoot.

8
>>> XIM4 [Mouse Ballistics] START PASTE >>>
X4MB:AAAAGgA0AC4AMAAwAC4AMgAwADEANgAwADQAMAA1AA0aJzRBTlxreoyescjIyMjIyMjI:X4MB
<<< XIM4 END PASTE <<<

Still won't let me post it?

What the other poster was pointing out, is that you're trying to paste a XIM4 ballistic curve into a XIM APEX. XIM4 ballistics are not compatible with XIM APEX.

9
XIM APEX Discussions / Re: Can we have an update OBSiv?
« on: 09:42 PM - 02/28/18 »
Sorry everyone, the store provider is working on it. I will notify my "Thank You!" thread of when the store will reopen. Please sign up for notifications on that thread.

Thanks OBsiV. Will be checking!

10
XIM APEX Discussions / Re: XIM APEX MANAGER avaible on PC?
« on: 06:24 AM - 02/16/18 »
There is no more on-the-fly ("Online", i.e. in-game) configuration anymore for PC Manager.

Wasn't able to keep up with this thread. I just saw this. Is there any chance this could be added in the future? It was literally the most convenient change I made when using the xim 4 manager. The PC manager was way faster to configure and tweak on the fly. Also easier for me to snip settings and help people on the community discord with examples.

11
I could never go analog, personally, I think the response time is too slow and I rarely find situations that require partial stick deflection to make it worth dumping the benefits of WSAD.

12
XIM APEX Discussions / Re: Joycon vs nav?
« on: 02:36 PM - 01/22/18 »
Would love to see a usable controller take on the ergo of the oculus touch.  Much more comfortable than the nav.  I can only use the nav if I pop some ibuprofen and acetaminophen beforehand...   ;D



13
XIM APEX Discussions / Re: XIM APEX MANAGER avaible on PC?
« on: 02:18 PM - 01/22/18 »
To clarify, would a 4-port hub and transfer cable then be needed to run the Manager on a PC?

14
Mouse [1000hz output]  -> [1000hz input] APEX [1000hz output] -> [250hz input] PS4 USB.

When a USB device connects to a USB host (in this case, the console), it requests a polling rate. The host will then request input from the device at that rate.
So TeslaDev's example should be updated to read:
Mouse [1000Hz Output] -> [1000Hz Input] APEX [250Hz Output] -> [250Hz Input] PS4 USB ?

I think he meant:
Mouse [1000Hz Output] -> [1000Hz Input] APEX [1000Hz Output] -> [1000Hz Input] PS4 USB
Device connects to host, it requests 1000hz. The host then polls that device at 1000hz.

Thanks for the response OBsIV.

15
Basically, self-addressing from the APEX side. So it takes it at 1ms intervals. Not bad. Hopefully the PS4 pumps that into actual response and doesn't buffer the extra data.

Pages: [1] 2 3 ... 21