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

Pages: 1 2 [3] 4 5 ... 17
31
Thank you for sharing this. This is a big contribution. I'll try this today with destiny 2 (ps4). I have great expectations.

your welcome.

use SLOW sync.

Ballistic-free: start with a sensitivity around 52.5 or

if you want the highest possible boost to make aim-assist even less hindering just open the ballistic editor and tap the right arrow once then slide the vertical knob up to 100% and save. if you go this route you would start with a sens of 1.05 (52.5x.02=1.05)

32
Please, refrain from directly quoting this post in its entirety as it is rather lengthy. Thanks.

The focus of this topic is for building your configuration by the book (traditional) with recommended settings to get the most from your XIM device. This will provide your XIM with the highest mouse sensor accuracy & responsiveness which will result in a super-clean and accurate conversion. Taking a break from the extreme to produce a long overdue guide that is full of information that should appeal to a wider user-base. Retain and apply this information. As always, enjoy yourselves.

Most mice true native is nearly 800DPI (above 700DPI but below 800DPI). my mouse is equipped the PMW3366 sensor which uses a 40x40 array - 1x magnification = 800 Counts Per Inch (CPI). 800DPI is the true physical resolution of the sensor and therefore will track the absolute best (i determined this on my own using extensively thorough testing methodology the very first day that i acquired a device that was equipped with this sensor.. this was before i even learned the exact specifications of the sensor itself. so i am actually basing this statement off of those results. the specifications just so happen to confirm my findings to be correct and that's reassuring.)

We will be using true-native DPI of the mouse sensor (or as close as possible). This will ensure that the mouse will output user input as accurately as it is capable of tracking. DO NOT fall prey to the marketing that modern sensors are native across all DPI steps. This is false. Every sensor's true CPI (counts per inch) capability can be determined by its array which will always reflect the true-native DPI of the hardware. Anything above that means that the mouse firmware must add counts and estimate user-input. The mouse sensor is a camera that rapidly takes snapshots in order to track it's positioning.

Modern devices with 'flawless' sensors are being marketed as native across all steps due to the inaccuracies at extreme DPI levels being much lower than they once were. (say, for example 12kDPI tracking accuracy of 94%). This may not sound like much but there is a real-world performance difference that I am able to detect and you should be able to as well. I own a Logitech G Pro which is one of if not the snappiest mice at max DPI that is on the market and 800DPI still performs better each and every time I flip back to it. It's noticeably more responsive and much more accurate. It is enough to make a huge different while playing multiplayer shooters. Especially ones with longer time-to-kill and heavier aim-assist. In general it is simply more reliable overall.

Spend a moment to think about the way a digital camera photo looks when taken without zoom. It's clear and artifact-free. A zoomed photo will look slightly blurrier but not very noticeable if the zoom falls within the hardware's optical zoom range. Beyond that is the digital zoom area where photos will begin to look noticeably murky and pixelated. For the instant gratification aficionado, open an image using any photo viewer and zoom in slowly. Pay attention to how the photo loses detail as you scale it beyond its native size.

The same holds true for the technology that your mouse uses to track user-input. By comparison the optical range for the newer gaming mouse sensors typically would be above 800DPI up to 3200DPI and the digital would be 3200+. On top of that the increased counts add latency. Micromovements suffer greatly due to the additional latency and inaccuracy. This is the main cause of negative acceleration and by now I feel that most of us understand that negative acceleration makes aim-assist much tougher to deal with.


set your mouse for 800DPI and 1,000Hz. (best of both worlds)

800 is plenty of DPI if you are mindful of the way to use it properly with XIM. Frame-syncing makes this possible. Contrary to what others may believe, lower DPI will not make aim-assist more pronounced in fact it will make it easier to work with due to the fact that the mouse is translating with less haste and greater overall accuracy. Use 800DPI in order to feed your XIM with the cleanest possible user-input and let the XIM handle the multiplier, instead. It's better this way due to the XIM receiving a higher quality mouse output to work with and with less delay in between. Why raise the mouse multiplier when the XIM handles this anyway? All your doing is adding latency and degrading quality of the data from the mouse before XIM even receives it then the XIM also has to process delayed and degraded received data before it reaches the gaming platform. The XIM output can't be any more accurate than the data it has been provided with to work with and it can't output it any faster than how long it takes to receive it.  Think about that.. Personally, I would rather the XIM receive the cleanest possible data in shortest amount of time to work its magic on.

That about wraps up the great DPI debate.

Moving on..

1,000Hz is a must if your mouse is capable of properly updating at this rate. The higher the updates per second the greater the tracking resolution, the lower the latency and the less aim-assist will interfere with user input.

Connecting an external power adapter to your USB hub is also recommended. It will provide performance stabulity by ensuring that your devices are receiving a consistent flow of energy.


Vanilla Smart Translation (No Ballistic)
800 DPI (Mouse)
1,000Hz (Mouse & XIM)
Synchronize to framerate: 60FPS=COMMON // 30FPS=SLOW
Smoothing=0

(Smoothing should not be necessary while frame-syncing and utilizing a reasonable sensitivity multiplier)


Using the above settings I use COMMON Sync + a sensitivity multiplier of 52.5 for Halo 5.
(That would be COMMON Sync + a sensitivity multiplier of 3.5 @12kDPI if anyone would like to create and test two separate configs back-to-back)

So there you have it. The best setup for the purist in all of us. It honestly doesn't get much better than this unless you dare to venture into the Extreme. If you're up for that then smack the link below for a follow up read which will detail everything for you.

https://community.xim.tech/index.php?topic=65974.0




I could have sworn you recently started yet another thread on this very same subject where you recommended 800dpi @ 1000hz polling but with sync set to off, and both smoothing and sensitivity set to their maximums, using a ballistic curve to alter the sensitivity.

Whats it to be?  You seem to come up with something new on a daily basis, making grand promises that it's perfect, and yet you clearly aren't satisfied with it, otherwise why keep altering it.  I have no doubts that you spend a lot of time testing your theories, but they seem to change on a daily basis!



I sure did however I am making attempts to offer the best method with explanation for getting the most out of the standardized method so that there is an offering to suit a variety of user preferences. Not everyone is comfortable enough to venture into the extreme. I get that. I also believe that anyone who refuses to venture into the extreme is cheating themselves out of something pretty special.

My R&D period with XIM APEX began from the very first day of ownership. It lasted roughly 10wks and has been over with since a few days prior to sharing "Perfect Match". No new R&D went into the Purist offering because it is already being used to lay the foundation for the Extreme variant. (800DPI / 1,000Hz)

So additionally you have the Purist offering which clearly was an afterthought but I figured why not share the stripped down model for those who will remain configuring that way. If you're going to stick to the basics then you might as well have the information to help you get the most out of it.

Bits and pieces (precursors) were shared as progress was made in order to let everyone in on it but nothing new is on the horizon. These last two topics are final and these two setups are about as good as it gets for the Purist and for the Extremist. 

For what it's worth I only use 800DPI / 1000Hz for every game. I use the traditional method with my recommended Purist settings for very few titles and for most others I use the Extreme approach. And once I get around to playing those select games that are still using the basic version they will be converted to Extreme which imo is the superior method.

Either way you can't go wrong however the extreme model already matches up better before even beginning to tune the sensitivity via the ballistic editor. This means that it will provide a much greater threshold of refinement and while spending less time doing so.

33
I definitely can relate to the op. there is a difference for me especially with games such as Halo CE MCC. so I use an external psu with my XIM hub.

34
I still got connection problem after last post. Then I've found I turned "Location" off in the setting. Turn it on and I can connect to XIM APEX. Turn it off, connect failure. So I am sure "Location" needs to be on. Please notice the users at the connect screen.


the solution is typical to one that would work for burping radios after flashing phone with  unstable homebrew firmware

are you running a custom Rom on your phone?

if so which Rom and version number?

35
I understand what you mean but it won't feel floaty by configuring in this manner due to the 1,000 Hz and by properly adjusting the ballistic portion.

I'm not a fan of the higher latency floaty feeling either which is one of the reasons why this is not recommended at 500Hz or less.

you are also increasing tracking accuracy through the reduction of interpolation and latency from the mouse by running it at 800DPI.

There is also pixel shipping being masked by the smoothing which is negating latency.

I know that the pixel skipping and smoothing seems ridiculous because we don't want this natively on PC but it makes perfect sense for console gaming with aim assist. it's already there when playing with a controller natively and I have found it to be important to make attempts to replicate that behavior with the mouse for a more seamless experience without many of the common issues.

Now I'm not twisting anyone's arm but I'm sure that this is going to be of use for users who seek solutions to some of those negatives.

At the very least this is a very user-friendly method for handling the conversion.


yes i have shared some of the discoveries which were precursors to this however there's also much more to this than what has been shared by me previously. it took an incredible amount of research and discovery of many individual settings and the behavior to ultimately get it there. so this is basically a combination of many things used in a very specific formula creating a synergy that would not be possible otherwise. there is an exact science to this method with the only variable being the ballistic value.

that is the best way that I can describe it.  all I can say is that if you haven't tried this for yourself using these exact settings for your mouse and xim you should because I have a feeling that you might be pleasantly surprised by the outcome.


36
Could u take a screen shot of what u mean by slide up to 100 from the 50 notch. Am I editing the x or the y axis. Im confused. Ty

There is no X or Y axis. The line on the bottom is your X input and the line on the right ist the X output. Y Axis is configured as same as X or by multiplying it (which you can find right underneath the button where you can adjust the smoothness).

What he means with `go to 50 notch and turn it to 100 ` is, that you should write 50 in the bottom line and turn the line on  the right to 100. You will notice that the 50 will change to 100 which means that the sensitivity is doubled. You will also see that the graphic will change and the linear function will be a lot steeper.

As result what he want you to understand is that you should change your sensitivity by changing the linear function instead of the sensitivity (what he max out to 500).


wow what a great 1st post.  ;D thanks.

37
Post #2 has been updated with responses to everyone who has contributed to this topic.

38
Please, refrain from directly quoting this post in its entirety as it is rather lengthy. Thanks.

DPI : 800
Poling Rate : 1,000Hz
Sensitivity : 500 (MAX)
Smoothing : 20 (MAX)
Synchronize : OFF
Adjust Sensitivity via the Ballistic Editor


In order to help get you up and running I have provided a few of my personal Ballistic Values. You could also disable aim-assist in games that allow you to and targeting should still feel incredible. I will continue to update this section as I see fit.:


Halo 1 (MCC): Hip-60

Halo 2 (MCC): Hip-60

Halo 3 (MCC): Hip-60

Halo 4 (MCC): Hip-60

Halo 2 Anniversary: Hip-60

Halo 5: Hip-60

30FPS Halo titles (X360): Hip-30

PvZ GW2: Smooth=10 // AA 'HEAVY'=Hip-60 / ADS-60 | AA 'LIGHT'=Hip-62 / ADS-62 | AA 'OFF'=Hip-64 / ADS-64

WWII: Hip-60 / ADS-76

Fortnite BR: Hip-60 / ADS-76

BF1: 60 to 64 - Full sample config is available below in the Q&A section.


(this is how sensitivity adjustments must be addressed -via the Ballistic Editor. it's fairly quick and simple. it only takes a few minutes to figure out the correct value. even if your value is way off your aim will probably still feel way better than it did while using your old config simply due to the way this config utilizes your mouse input. the process of dialing in your config is tedious no longer and this should be an obvious indicator that there's something very special going on under the hood. there's a much more technical explanation of what exactly is going on and why it works the way that it does but there's no need to get into the specifics. what matters is that i completely understand it. if there's a way to improve upon it i will figure it out. if and when this happens you will be notified. i would never withhold that information from any of you.)




Take my money. Very good Setup

Glad that you are enjoying it.



Feels like a pc 😕
Man this is amazing!
My aim is completely accurate!
Headshots become more easier. I'm serious guys :)

I don't know if I'm lucky with my shots or it is true thats this settings are completely good.

I tried this settings with Fortnite and battlefield 4 both were 100% perfect 👌🏻

The only problem is that there is no aim assist, however, I'm ok with that 🤷🏻‍♂️

Thank you man

Deserve a sticky 👌🏻


Thanks for sharing your experience. The aim-assist is in fact helping and it is still completely tuneable by adjusting the ballistic sensitivity. what you have described is the resulting behavior of perfect matching value that allows the config to mimic analog behavior so well that the result is seamless. so it's buttery smooth all around now and with the superior control of a mouse and finally without the muscle-memory interruption which is what I have been working toward achieving for some time now -loooonnnnnnnng before XIM APEX ownership however XIM definitely helped to expedite the process due to its superiority and it will only get better when a future XIM product offers a 100-step Ballistic Editor. I'm ecstatic over this triumph and pleased to be able to share it with the world. Have fun out there.


jfame, are you saying to run your mouse dpi at 800 dpi?

Correct.  ;) Here's an excerpt containing my explanation taken from the the Purist thread. (basic-version)

We will be using true-native DPI of the mouse sensor (or as close as possible). This will ensure that the mouse will output user input as accurately as it is capable of tracking. DO NOT fall prey to the marketing that modern sensors are native across all DPI steps. This is false. Every sensor's true CPI (counts per inch) capability can be determined by its array which will always reflect the true-native DPI of the hardware. Anything above that means that the mouse firmware must add counts and estimate user-input. The mouse sensor is a camera that rapidly takes snapshots in order to track it's positioning.

Modern devices with 'flawless' sensors are being marketed as native across all steps due to the inaccuracies at extreme DPI levels being much lower than they once were. (say, for example 12kDPI tracking accuracy of 94%). This may not sound like much but there is a real-world performance difference that I am able to detect and you should be able to as well. I own a Logitech G Pro which is one of if not the snappiest mice at max DPI that is on the market and 800DPI still performs better each and every time I flip back to it. It's noticeably more responsive and much more accurate. It is enough to make a huge different while playing multiplayer shooters. Especially ones with longer time-to-kill and heavier aim-assist. In general it is simply more reliable overall.

Spend a moment to think about the way a digital camera photo looks when taken without zoom. It's clear and artifact-free. A zoomed photo will look slightly blurrier but not very noticeable if the zoom falls within the hardware's optical zoom range. Beyond that is the digital zoom area where photos will begin to look noticeably murky and pixelated. For the instant gratification aficionado, open an image using any photo viewer and zoom in slowly. Pay attention to how the photo loses detail as you scale it beyond its native size.

The same holds true for the technology that your mouse uses to track user-input. By comparison the optical range for the newer gaming mouse sensors typically would be above 800DPI up to 3200DPI and the digital would be 3200+. On top of that the increased counts add latency. Micromovements suffer greatly due to the additional latency and inaccuracy. This is the main cause of negative acceleration and by now I feel that most of us understand that negative acceleration makes aim-assist much tougher to deal with.


800 is plenty of DPI if you are mindful of the way to use it properly with XIM. Contrary to what others may believe, lower DPI will not make aim-assist more pronounced in fact it will make it easier to work with due to the fact that the mouse is translating with less haste and greater overall accuracy. Use 800DPI in order to feed your XIM with the cleanest possible user-input and let the XIM handle the multiplier, instead. It's better this way due to the XIM receiving a higher quality mouse output to work with and with less delay in between. Why raise the mouse multiplier when the XIM handles this anyway? All your doing is adding latency and degrading quality of the data from the mouse before XIM even receives it then the XIM also has to process delayed and degraded received data before it reaches the gaming platform. The XIM output can't be any more accurate than the data it has been provided with to work with and it can't output it any faster than how long it takes to receive it.  Think about that.. Personally, I would rather the XIM receive the cleanest possible data in shortest amount of time to work its magic on.


Could u take a screen shot of what u mean by slide up to 100 from the 50 notch. Am I editing the x or the y axis. Im confused. Ty

Updated thread with screenshots and a code for the recommended starting ballistic.


Also what polling rate do u recommend on this set up. Thanks

Eight Hundred (800) DPI  //  One Thousand (1,000) Hz


Tried this in bf1, not bad to be fair, and easy to get the sens matched with my other profiles. Can't really tell the difference between using the mouse at 12k vs 800dpi in relation to movement.  I ended up switching back to my 12k setup though as I was noticing the jitter (not that it was overly bad) more with these settings, but I'm sure with a bit of tweaking it could work very well.

there shouldn't be ANY noticeable jitter or negative acceleration at all if you configured exactly as specified. This isn't a simple sensitivity adjustment there's much more to it than that but you're entitled to do as you please. thanks for your feedback.

Update: Just tested the XB1 version BF1 and it felt amazing. Best that it has ever felt. Smooth / jitter-free, responsive and Aim-Assist worked perfectly as it would with an analog. BF1 aiming has always felt a bit gritty to me prior to using this new format but now it is buttery smooth and everything feels perfect under these settings. I never expected anything less. Analog behavior is quite jumpy under the thumb which means that there is also quite a bit of pixel skipping occuring natively with controller and being masked by smoothing. This config is more properly mimicking this on the XIM side but it is essential to use the exact same combination of DPI, Polling Rate with 500 sense & 20 smoothing. If anyone is using a mouse that can't output 1,000Hz and is say only capable of 500Hz then they won't be able to enjoy the full benefits of this config but will be able to modify it to work for them to some degree. I would assume that they could run 1,600DPI with 10 smoothing @500Hz but it won't perform as well so I recommend upgrading to one capable of 1,000Hz.. More specifically, The Logitech G-Pro.. I am using the new config method settings with FoV set to 90 , uniform Soldier Aiming Enabled and Coefficient set for 178 Take notice that If playing on the default FoV you should use the default coefficient of 133.






Here's a code with my original BF1 config with the sensitivity and recommended staring ballistic of 60. With a mouse, I have always played BF1 with Uniform Soldier Aiming enabled and with ADS translator disabled because it has always performed the best for me so that is the way that I left it but I did adjust the sens and applied the ballistic for ADS for anyone who prefers to enable it (it probably actually works properly under these settings but to me it makes more sense to use the config the way it has been used for mouse-play). I play XB1 elite controller with 2 paddles in left hand so you will likely need to reconfigure the button layout.

BF1 (XB1) - 800 DPI // 1,000Hz // Synchronize: DISABLED
ADS Disabled for use with Uniform Soldier Aiming Enabled // Default FoV = Default Coefficient (133) ; 90 FoV = 178 Coefficient.

Code: [Select]
>>> XIM APEX [Battlefield 1] START COPY >>>
X5C:AAAAGgA1AC4AMAAwAC4AMgAwADEAOAAwADQAMAAyAAAAGgBCAGEAdAB0AGwAZQBmAGkAZQBsAGQAIAAxAAAKAQEAAAAAAAAABgBIAGkAcAEAAAAAAAABAAAAAAAAAADDUABkAAAAAAAUAAAAAAABTQKbA+gFNQaDB9AJHQprC7gNBQ5TD6AQ7RI7E4gU1RYjF3AYvRoLG1gcpR3zH0AgjSHbIygkdSXDpxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQYwRgEGCAYkAAAAAAAAAAAAAAAAABAgQFAAAdTB1MFBRAAaABQAQgQCECIQEhEEACQAigBKAIIAJpAkAQIBAgICEEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAcAEEAaQBtACAARABvAHcAbgAgAFMAaQBnAGgAdAEBAAAAAAAAAAAAAAAAAADDUABkAAAAAAAUAAABAAABxwONBVQHGgjhCqcMbg40D/sRwROIFU8XFRjcGqIcaR4vH/YhvCODJUmnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQYwRgEGCAYkAAAAAAAAAAAAAAAAABAgQFAAAdTB1MFBRAAaABQBAAAEAIAAAAAEACoAigBGkIaUBpgGoBagRABAAAAAAAAAAAAAAAAAAAAAAAAAAAaQIAAAAAAAAAAAAAAAAAAAAAAAAAAAAOAFYAZQBoAGkAYwBsAGUAAQAAAAAAAQAAAAAAAAAAPoAAZAAAAAAAAAAAAAAAAMgBkAJYAyAD6ASwBXgGQAcIB9AImAlgCigK8Au4DIANSA4QDtgPoBBoETAR+BLAE4gUUBUYFeAWqBdwGDgZABnIGpAbWBwgHOgdsB54H0AgCCDQIZgiYCMoI/AkuCWAJkgnEGMEYBBggGJAAAAAAAAAAAAAAAAAAQIEBQAAHUwdTBQUQAFAAmEBfAJhBGIQZRBgQGIgY0BqBGoCaYBqAWkBZQhlAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFgBBAHUAeABpAGwAaQBhAHIAeQAgADIAAQAAAAAAAQAAAAAAAAAABdwAZAAAAAAAAAAAAAAAAMgBkAJYAyAD6ASwBXgGQAcIB9AImAlgCigK8Au4DIANSA4QDtgPoBBoETAR+BLAE4gUUBUYFeAWqBdwGDgZABnIGpAbWBwgHOgdsB54H0AgCCDQIZgiYCMoI/AkuCWAJkgnEGMEYBBggGJAAAAAAAAAAAAAAAAAAQIEBQAAHUwdTBQUQAFAAmEBfAJhBGIQZRBgQGIgY0BqBGoCaYBqAWkBZQhlAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFgBBAHUAeABpAGwAaQBhAHIAeQAgADMAAQAAAAAAAQAAAAAAAAAABdwAZAAAAAAAAAAAAAAAAMgBkAJYAyAD6ASwBXgGQAcIB9AImAlgCigK8Au4DIANSA4QDtgPoBBoETAR+BLAE4gUUBUYFeAWqBdwGDgZABnIGpAbWBwgHOgdsB54H0AgCCDQIZgiYCMoI/AkuCWAJkgnEGMEYBBggGJAAAAAAAAAAAAAAAAAAQIEBQAAHUwdTBQUQAFAAmEBfAJhBGIQZRBgQGIgY0BqBGoCaYBqAWkBZQhlAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFgBBAHUAeABpAGwAaQBhAHIAeQAgADQAAQAAAAAAAQAAAAAAAAAABdwAZAAAAAAAAAAAAAAAAMgBkAJYAyAD6ASwBXgGQAcIB9AImAlgCigK8Au4DIANSA4QDtgPoBBoETAR+BLAE4gUUBUYFeAWqBdwGDgZABnIGpAbWBwgHOgdsB54H0AgCCDQIZgiYCMoI/AkuCWAJkgnEGMEYBBggGJAAAAAAAAAAAAAAAAAAQIEBQAAHUwdTBQUQAFAAmEBfAJhBGIQZRBgQGIgY0BqBGoCaYBqAWkBZQhlAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA:X5C
<<< XIM APEX END COPY <<<





Thanks I actually really like this for shotguns in Fortnite was hitting crazy mid air shots. I do find the snipers very hard to use with it however

i believe that you were hitting those crazy shots. this config essentially gives you perfect analog-to-mouse conversion that is just as smooth & responsive resulting in seamless overall aiming and therefore should not disrupt muscle memory at all. the snipes probably feel off to you because of the responsiveness. i prefer a couple of extra ms delay for to add a trace of prediction to my snipe swipes as well. adjust your ads ballistic to a slightly higher value which will slow down your aim.

39
Please, refrain from directly quoting this post in its entirety as it is rather lengthy. Thanks.

2 very different methods for building a config with recommended settings and explanation. Purist focuses on the best setup to get the most out of your hardware by utilizing the standardized and widely accepted config building model. This method is the Extreme version which is essentially Purist + enhancements. Still uses the 800DPI / 1,000Hz from the to lay the foundation.

Recommendation for the Purist (if you simply aren't comfortable going all out then follow the link for the basics):
http://community.xim.tech/index.php?topic=66177.0

most mice true native is nearly 800DPI (above 700DPI but below 800DPI). my mouse is equipped the PMW3366 sensor which uses a 40x40 array. 800DPI is true native and will track the absolute best (i determined this on my own using extensively thorough testing methodology the very first day that i acquired a device that was equipped with this sensor.. this was before i even learned the exact specifications of the sensor itself. so i am actually basing this statement off of those results. the specifications just so happen to confirm my findings to be correct and that's reassuring.)

set your mouse for 800DPI and 1,000Hz.

but XIM with 800DPI @1,000hz is typically a no go right?

wrong.


So use 800DPI to receive the best possible sensor accuracy & responsiveness out of your mouse. Poll at 1,000Hz for high frequency tracking updates and the lowe-latency smoothing compatibility.
(Use 800DPI to provide your XIM with the clearest / highest quality sensor tracking data to work with and also for the shortest possible processing delay then let the XIM handle the scaling multipliers , interpolation etc. It is better this way. I have provided a detailed explanation as to why on the Purist thread topic.)

Set your sens to 500 (max) for HIP and for ADS.
(This is not a typo this should remain at maximum for all configs.)

Synchronize : OFF

At this point this is going to result in large amounts of pixel skipping at only 800DPI with 1,000Hz which is a good thing because it will ensure that we do not have a negative acceleration problem. 

now mask that pixel skipping with maximum smoothing of 20 for HIP and ADS.

(20 isn't the be all end all but this is the recommended starting value. In most cases the final value will be 10+ depending on built-in smoothing of game's aiming model.)

then use the Ballistic Editor to adjust sensitivity.
(Disabling Sync while outputting 1,000Hz plus the hidden pixel skipping will completely negate the added delay from the smoothing once the ballistic sensitivity is dialed in properly.)

Sample various ballistic values by testing slow, med and fast swipes and also swipe hard in one direction then immediately swipe the opposite direction. Take notice of how closely the mouse relates to your free-aim swipes and make every attempt to adjust the ballistic until you feel virtually zero delay from start and when abruptly halting your arm movements. There is indeed a ballistic value that will feel 1:1 without delay. Test your new value on a few opponents. If overshooting the aim-assist bubble then lower the sens by raising the ballistic value 1 notch at a time to the right or perform the opposite if you feel that targeting requires a slight boost into the bubble. When it's right you will undoubtedly know it.


For 60FPS Titles: begin with a 60% Ballistic Value (slide up to 100% at the 60% notch)
if you need faster then clear ballistic and use 58 or lower. if you need slower clear ballistic and use 62 or higher.

For 30FPS Titles: begin with a 30% Ballistic Value (slide up to 100% at the 30% notch)
if you need faster then clear ballistic and use 28 or lower. if you need slower clear ballistic and use 32 or higher.


The way that this config handles the translation is very different from the standard way. For this reason I recommend that everyone begins fresh with this exact setup and completely disregards conversion of sensitivity from older configs. Above avg sensitivities have proven to be optimal and they function properly (way better than they would using the standard method). Also, the ballistic sensitivity tuning process will be much quicker and easier than you are used to.


drastically improved overall aiming & player targeting should be immediately noticeable.
this is the cleanest player targeting i have ever experienced while using a mouse on console. negative side-effects are now a thing of the past. enjoy yourselves.



by the way.. i've noticed many users having issues with fortnite battle royal so i booted it up today for the very first time since purchasing a xim device and i had zero issues with player targeting from the very first engagement. i never expected any problems because configs built using this method completely eliminate common negative acceleration issues.



Summary:

DPI : 800
Poling Rate : 1,000Hz
Sensitivity : 500 (MAX)
Smoothing : 20 (MAX)
Synchronize : OFF
Adjust Sensitivity via the Ballistic Editor




60% Neutral Ballistic (for 60FPS titles)

Code: [Select]
>>> XIM APEX [Translate Ballistics] START COPY >>>
X5BC:AAABTQKbA+gFNQaDB9AJHQprC7gNBQ5TD6AQ7RI7E4gU1RYjF3AYvRoLG1gcpR3zH0AgjSHbIygkdSXDpxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQ:X5BC
<<< XIM APEX END COPY <<<


30% Neutral Ballistic (for 30FPS titles)

Code: [Select]
>>> XIM APEX [Translate Ballistics] START COPY >>>
X5BC:AAACmwU1B9AKaw0FD6ASOxTVF3AaCxylH0Ah2yR1pxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQ:X5BC
<<< XIM APEX END COPY <<<




Testing Equipment:

XIM APEX // BETA : 20180402

Xbox One X // BenQ RL2455HM // Logitech G Pro (modified with with CeeSA paracord & Hotline mouse feet) // Zowie Mouse Bungee // Cooler Master Swift-RX cloth pad.





I could have sworn you recently started yet another thread on this very same subject where you recommended 800dpi @ 1000hz polling but with sync set to off, and both smoothing and sensitivity set to their maximums, using a ballistic curve to alter the sensitivity.

Whats it to be?  You seem to come up with something new on a daily basis, making grand promises that it's perfect, and yet you clearly aren't satisfied with it, otherwise why keep altering it.  I have no doubts that you spend a lot of time testing your theories, but they seem to change on a daily basis!



I sure did however I am making attempts to offer the best method with explanation for getting the most out of the standardized method so that there is an offering to suit a variety of user preferences. Not everyone is comfortable enough to venture into the extreme. I get that. I also believe that anyone who refuses to venture into the extreme is cheating themselves out of something pretty special.

My R&D period with XIM APEX began from the very first day of ownership. It lasted roughly 10wks and has been over with since a few days prior to sharing "Perfect Match". No new R&D went into the Purist offering because it is already being used to lay the foundation for the Extreme variant. (800DPI / 1,000Hz)

So additionally you have the Purist offering which clearly was an afterthought but I figured why not share the stripped down model for those who will remain configuring that way. If you're going to stick to the basics then you might as well have the information to help you get the most out of it.

Bits and pieces (precursors) were shared as progress was made in order to let everyone in on it but nothing new is on the horizon. These last two topics are final and these two setups are about as good as it gets for the Purist and for the Extremist. 

For what it's worth I only use 800DPI / 1000Hz for every game. I use the traditional method with my recommended Purist settings for very few titles and for most others I use the Extreme approach. And once I get around to playing those select games that are still using the basic version they will be converted to Extreme which imo is the superior method.

Either way you can't go wrong however the extreme model already matches up better before even beginning to tune the sensitivity via the ballistic editor. This means that it will provide a much greater threshold of refinement and while spending less time doing so.

40
General Discussion / Re: monitor and tv question
« on: 12:32 AM - 05/08/18 »
hi ..i have normal HD tv and some friend told me to buy monitor espically for gaming so my question is  does the monitor for gaming is better than tv in fps games?

i only game on monitors. even casual single player games.

IBM ThinkVision C220p 22" (Diamondtron aperture grille)

Sony GDM-FW900 Widescreen 24" CRT (Trinitron aperture grille)

BenQ RL2455HM 24" 1080p LCD (original version - without the Zowie branding and its laggy firmware)
i have used my 1x with a 4k monitor but i didn't like it. i prefer the performance that super-sampled 1080p provides and it looks fine on a 24inch screen. tbh games such as Gears 4 look better 1080pSS than 4k also.

Still shopping around for a reasonably priced CRT Broadcast/Pro Video Monitor (BVM-D32E1WU, BVM-20F1U etc..) as well but knowing me once i do i will probably purchase a few more lol. I love CRT-tech and I hate that it is no longer in production.

I actually own  a Sony XBR960 that is in excellent condition which I have tuned the heck out.



here's a snapshot of the insanity that one must endure while calibrating the service menu.. but the end result is always worth the struggle.



I only use it for watching movies. It looks incredible.

41
General Discussion / Re: Logitech G-Pro CeeSA Paracord Mod
« on: 06:16 PM - 05/07/18 »
RESERVED

42





imgur Galleries


01 - Teardown

https://imgur.com/a/y3npAvn


02 - Completed

https://imgur.com/a/44A2AOh




Favorites

















43
XIM APEX Discussions / Re: Halo 5 help please!!!!!
« on: 02:09 AM - 05/06/18 »
Halo 5 is the game I play the most and despite the lower maximum turn speed, I feel it feels really great.

I use a 12000dpi mouse, Sensitivity=3.75, Synchronize=Common, Smoothing=5. Of course, in-game settings set to http://xim.tech/settings.

c'mon man hmu for some H5 then lol

44
XIM APEX Discussions / Re: Sync OFF or COMMON
« on: 02:07 AM - 05/06/18 »
As OBsIV already stated this will always boil down to personal preference but i would like contribute insight based on my own rigorous testing in order to broaden the spectrum.

having spent quite a bit of time running each for extended periods and also rapidly flipping between them all every min or 2.. for me 1,000Hz with sync set to SLOW for 60FPS does the best job of preventing muscle memory from becoming disrupted from aim assist slowdown.

in theory lower-latency seems more appealing (and it very well might be if playing without aim-assist slowdown) however from my testing lowest possible sync is the most balanced for transitioning into, through and out of slowdown without any noticeable additional force and without the need for smoothing in most cases. you should give it a try and play something with longer kill-times and strong aim-assist such as plants vs zombies garden warfare with assist set to heavy. flip between the choices and be sure to adjust the sens properly for each. if you know what to look out for it's fairly obvious. pay attention to the behavior while approaching the bubble, tracking in the bubble, aim correction around the bubble. pay attention to overall feel. you should notice that when set to slow the cursor vacuums into the bubble without any extra effort without breaking your momentum , tracks more efficiently , much lower under-aim / over-aim, easier to correct aim and break back into bubble if you bounce out prematurely. simply put it feels natural and stress-free.

i'm also hoping for a super-slow option to be able to half-sync 30FPS titles as well.

i've noticed that the higher the sync the more disruptive that slowdown becomes for me. the more likely i am to lose momentum into the bubble or overshoot my mark. it definitely takes longer to correct back into the bubble when losing my opponent with increased sync rates also. at times i feel like i'm walking on egg shells with higher Hz sync around the bubble,tbh. higher Hz processes faster but for me it seems to overcomplicate things and often results a longer and bumpy road to reach the same result that i do with low Hz.

Definitely still config your mouse and your XIM for 1000Hz while running low Hz sync with it. This will give you the best of both worlds without the negatives from 1,000Hz on its own. Also the slowest sync allows for the lowest multiplier to be used which is definitely a plus.

Others will tend to disagree with this next part but I should mention that I often also use the maximum ballistic by moving right to the first notch (2.00) then sliding up to 100% (it's basically boost but also ridiculously enhances micro-movements and responsiveness) with a Logitech G Pro on a cloth speedpad @12kDPI 1,000Hz SLOW sync and my sens is usually somewhere between .04 to .10 depending on the game being played. in garden warfare 2 for example i'm using .05 for both hip and ads.. in cod wwii i'm using hip .09 and ads .06. Halo titles i run .04 or .05.. you get the idea. The amount of perfect kills i get in Halo 5 using these settings in unrivaled by any other type of config combo i have tested and the snipe is always spot on.. I just wanted to throw this in so if you decide to test my settings you can get the full experience, if desired. and try aim-assist disabled on occasion. i switch it on or off depending on how mood and how i want to play at that moment in time on games that offer the choice. i'm a PC gamer also. for what it's worth disabled aim-assist is way easier and feels much closer to how it should natively on PC due to the level of control this sort of config provides. so well that sometimes when i pause to switch it off and then see that it was disabled already, lol.

realistically you'll achieve a better balance using a slightly less extreme ballistic beginning from the 10% mark rather than 2%.

one last word of advice.. I also own the Basilisk and it adds additional smoothing beyond 1800DPI. It always performed better for me at 1800DPI than 16,000 on XIM APEX. not exactly sure why but 1350DPI always felt incredible on it on my titan one, also. and with slow sync and a good ballistic 1800 is plenty because your multiple will be so low anyhow. furthermore, if you don't know this already the Basilisk can only run 1,000Hz from the white profile that is auto-saved from your last used settings in Synapse 3. the other 4 profiles ( red, blue, green, cyan) that are user-stored will only run 500Hz. The Xim Manager will start off  showing it running at 500Hz but then the mouse will eventually falsely report that it is running 1,000Hz and the manager will reflect this. Just be certain that you set your xim options such as DPI and polling rate on you synapse active profile then when you disconnect from PC and reconnect to XIM make sure the white profile is enabled.

The G Pro is by far the best performing mouse I have ever used on PC and on XIM @12kDPI, btw.

Pages: 1 2 [3] 4 5 ... 17