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.0most 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)>>> XIM APEX [Translate Ballistics] START COPY >>>
X5BC:AAABTQKbA+gFNQaDB9AJHQprC7gNBQ5TD6AQ7RI7E4gU1RYjF3AYvRoLG1gcpR3zH0AgjSHbIygkdSXDpxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQJxAnECcQ:X5BC
<<< XIM APEX END COPY <<<
30% Neutral Ballistic (for 30FPS titles)>>> 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.