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

Pages: [1] 2 3 4
1
I purchased a power supply to plug into the XIM.  No issues after using this.  My devices are a Razer Tartarus rated at 400mA plus my G502 mouse at unlisted mA.

2
I have gone through 2 Xbox One X that keep having strange issues, won't turn on, random shutdowns, crashing games.
I have narrowed it down to only having issues while the Xim is plugged in.  I am using a logitech G500 and Razer Tartarus.  I have disabled their lights and they work fine with XIM Apex.  I am able to reproduce the crash issue within 30 minutes now.  I think it slowly wears down the PSU, somehow?  Used to never have issues, but now its without fail.
I just bought a https://www.amazon.com/gp/product/B01DPCPAQS/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1 and this should resolve my issues.  For now i have to play with a controller!!!!

3
Thanks, that makes me feel better.  I've played with the XIM for too long to ever go back to controller.  And playing on console versus PC just isn't fair because of inventory button mapping and more powerful hardware.

4
Right, the XIM outputs as a controller.  But would it be possible to detect "strange" behavior from users.  Such as having maxed out sensitivity in game, while still being able to finely move the cross-hairs.  Console controllers will have a minimum movement step caused by physical movement that could differ from what values are possible digitally.

I feel confident in the XIM developers being able to overcome this if Epic throws yet another curve ball.

5
Can they detect XIM with proposed Input-Based Matchmaking?  And how would we even know, besides seeing a PC streamer name in the kill feed.

https://www.epicgames.com/fortnite/en-US/news/state-of-development-august-2018
"Input-Based Matchmaking
We have an upgrade to our matchmaking logic that will allow for a more even playing field when enjoying Fortnite with your input device of choice. In an upcoming release we’ll be implementing input based matchmaking, which will pair you against players who are using the same peripherals (e.g. controller vs controller, KB+M vs KB+M)."

6
Example scenario: USB OTG cable from an android phone to power the XIM Apex.  XIM outputs mouse / keyboard / controller over bluetooth to phone.  Is this possible with the hardware of the XIM Apex?

Need to find my OTG adapter before I can try, but would it pass through the data over USB to the phone?  Anyone else try this?

7
Shameless self bump.  Updated for builder pro, minor control changes.

8
This is a game limitation that annoys me as well.  To run with controller or XIM you must be moving already OR double / triple tap the sprint button.  My sprint button finger is always stiff after long gaming sessions.
Possible 1 button press solutions are: 
1) You can get a mouse with onboard memory that support macros (not terribly useful for this case)
2) Find a keyboard with onboard memory (such as Koolertron Cherry MX Black Programmable Gaming Keypad, ~$80 USD)
3) Buy a Titantwo ($100 ish USD)
4) Buy a USB transfer cable and use a windows computer with W11cE's XIM LInk: https://community.xim.tech/index.php?board=96.0 (cheapest option, but requires windows computer always on nearby)

9
Game Support / Re: XIM apex dpi (fortnite)
« on: 09:55 AM - 04/13/18 »
** Setup **
Mousepad -- Large Hard Pad (Logitech G440)
** Firmware -- Beta Firmware 20180402 **
Xim Polling -- 500hz
Mouse DPI -- 3200
Mouse Polling -- 500hz (don't bother with 1000hz, its not always 1000hz from the mouse)

*** AIM SENSITIVITY ***
Hip -- 25.00
ADS -- 9.5
Smoothing -- 0
Synchronize -- Common

If you don't like this feel, look at: http://community.xim.tech/index.php?topic=60845.0

10
Game Support / Re: Destiny 2 help
« on: 09:53 AM - 04/13/18 »
My advice is switch to Fortnite Battle Royale.  The game is free with no pay to win, only cosmetic purchases.  I played Destiny 1 heavily and played Destiny 2 for about 2 weeks.  Fortnite is now the main game I play.  It will take time to learn about building and the huge map, but the game is so addicting and unique.

11
** USE COMMON SYNC WITH FORTNITE **
Feels soo much better.  Using AA and it actually works but isn't annoying (minus lobby).

** Setup **
Mousepad -- Large Hard Pad (Logitech G440)
** Firmware -- Beta Firmware 20180402 **
Xim Polling -- 500hz
Mouse DPI -- 3200 dpi
Mouse Polling -- 500hz (had minor issues with 1000hz, no human noticeable diff with 500hz)

*** AIM SENSITIVITY ***
Hip -- 25.00
ADS -- 9.5
Smoothing -- 0
Synchronize -- Common

If you don't like this feel, look at: http://community.xim.tech/index.php?topic=60845.0

12
Game Support / Re: Fortnite sens
« on: 09:39 AM - 04/13/18 »
Playstation might have a different sensitivity curve than Xbox.  My advice is to go into squads and drop somewhere very remote where you can adjust your sens on the app and just aim at objects around you until it feels good.

13
Game Support / Re: For Anyone Struggling with Fortnite AA
« on: 04:37 PM - 04/12/18 »
Firmware -- Beta 402
Mouse DPI -- 3200
Mouse Polling -- 500hz
Xim Apex -- 500hz polling

Hip -- 25.00
ADS -- 10.0
Smoothing -- 0
Synchronize -- Common
AA -- On

This feels amazing, short range is spot on, long range is spot on.  Use hip to line up, then ADS lock and tap your shots.  This is strong enough to pull out of AA.  I used to run 1000hz @12k dpi, higher is NOT better imo.

14
Updated after testing and forum research.
Most mouses don't hold a steady 1000hz, so that can introduce weird float randomly. 
Reduced to 500hz and reduced DPI to 3200.

15
Your logic seems sound.  But do you experience any latency while switching into AUX mode from weapon or from build mode.  Even a small latency in pulling up building could cause you to take extra damage or worst case fall off something.  I use my G502 with a similar macro but without using AUX mode.  I manually switch to flat or roof and use a macro to very quickly pull up stair piece. 
My delay timing are as follows:
Between Key Up Down: input value 22
Between Different Keys: input value 45
These values work very well and it feels instant.

Pages: [1] 2 3 4