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.


Topics - mjfame

Pages: [1] 2 3
1
Snagged a free DELL CRT. handles 240p output as well as HD with zero motion blur and obviously the display latency is virtually zero.

https://imgur.com/gallery/JcPHM18


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

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

6





imgur Galleries


01 - Teardown

https://imgur.com/a/y3npAvn


02 - Completed

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




Favorites

















7
I was a fan of polling native 125Hz on XB1 long before purchasing a XIM. The added burst that lower Hz provides deals with aim-assist better, imo and it more than makes up for the higher latency.

I love the synchronization functionality that APEX provides because it allows me to poll my mouse at 1kHz without the negatives. The XIM receives the highest possible resolution while simultaneously utilizing a lower synchronization value for the game's input loop.

Best of all, I am able to 30Hz synchronize while running 60Hz titles. 1kHz mouse & XIM polling plus half-sync is fantastic. This is my preferred combo.

It's even more fluid than 1kHz without sync and almost as responsive. My favorite reason for half-synchronizing is because it is a wonderful timing mechanism. The lowest possible sync gives the highest possible burst which makes tracking through aim-assist super easy. It always ensures that I likely will not underaim when approaching the aim-assist bubble and it's also a great overaim governor.

I love the fact that I can just relax let my mouse flow without overthinking the bubble.

I have requested that a super-slow 15Hz synchronization option be supported in the future in order to allow for half-sync while running 30Hz titles and I am still hopeful for this to be acknowledged and implemented.

9
i realize that i'm late to the party but i still want to say that..

Logitech G Pro is an excellent gaming mouse. Low profile design and agile. top-sensor without any artificial smoothing or acceleration. doesn't get much better than this. Handles like an exotic sports car. I can whip that little f*cker around the pad without fail.. The quest for the perfect mouse is over.

It's 40x40 array which is 800DPI hardware native, btw and that's how I'm running it.. 800DPI @250Hz (double native polling) No frame-sync. and it's fantastic. (couldn't care less about max dpi and polling YES 40x40=800 so 800DPI is true native and anything above that is a multiple which is NOT FOR ME)

Went 23-1 with a rampage in my first Halo 3 BR match on standoff.


10
TEAM XIM probably never considered this but there are scenarios in which other users and I prefer to run 30Hz SLOW Sync preset in order to half-sync for 60FPS titles but there's currently no way to do so for 30FPS titles. If you wouldn't mind adding this with a future update that would be excellent.

Also, perhaps at some point providing full-control over this value at the user-level with the option to adjust this in increments of 1 via either Expert mode or an additional tier above expert.

You have already unlocked and provided the frame-sync feature so might as well allow it to be utilized to its fullest potential.


At the very least the additional 15Hz sync preset would suffice by providing uniformity of the offerings at either framerate.

Thanks.

12
Ridiculous.

I did used to play the game in the 80s on my IBM PS2 Computer so I got nostalgic and searched the gameplay on YT.

This comment made it totally worth it for me.
The sarcasm is real. Love it.


15
General Discussion / "My Little Homie"
« on: 05:30 PM - 04/18/18 »
Love that lil' f*cker

Pages: [1] 2 3