XIM360 Community » XIM 2 » XIM 2 Discussions » this thing is like, wow
« previous next »
Pages: [1]
Print
Author Topic: this thing is like, wow    (Read 294 times)
Threewheels
Member
*

Karma: +5/-2
Offline Offline

Posts: 91


View Profile
« on: 12:47 PM - 07/28/10 »

I just couldn't wait for Xim3, so I purchased a Xim 2 last week from ebay, seller claimed new and unused.  received it yesterday, and was happy to find that it did indeed appear to be a fresh unit.

got it installed on my win7 64bit machine (followed the guide) and got it working without a hitch.  I have a logitech G500 mouse, and I'm still running the setpoint drivers, without the cpl acceleration fix.  I basically just copied colb's MW2 config, which he said he copied from Toys I think, and made a few sensitivity adjustments.  I just can't believe how good this thing feels right out of the box with just a few tweeks.

It's quite amazing.  didn't really get to play much because I couldn't get sound to work when hooked up to the PC (that's another story all together).

So then I installed it on my netbook (winXP 32bit, SP3) so I could use it on the big TV, and it was having a problem not finding the proper XInput.dll file, so it wouldn't configure.  it kept asking for xinput1_9_0.dll or something like that, so I just renamed the Xinput1_3.dll in the xim directory to the Xinput1_9_0.dll, and it worked perfectly. 

Also, I didn't see anywhere that I needed to install the USBexpress drivers on XP, is this necessary?

Anyway, even without OC'ing the usb polling rate yet, the thing feels DAMN good.  I tested acceleration by slowly moving my mouse from one side of my mouse pad to the other (17 inches),  slow at first, then faster.  each time, the crosshairs ended up in nearly the same place as I started, regardless of speed.  So it appears the translation component is spot on for my setup.

Only issues I noticed was that if I was sprinting (holding 2 buttons down), I couldn't jump (win7 machine).  though this worked find on the XP netbook with a newer keyboard, so maybe it's a keyboard limitation.  hmm, now that I think about it, I think the win7 keyboard is connected via the PS/2 port, so maybe that has something to do with it.  I'll have to change them tonight.

And also, I couldn't rename the config file and save it.  I don't know if that's possible though (didn't receive any documentation with the xim).

I foresee very little sleep in my future for the next few nights Tongue
Logged
colb
Member
*

Karma: +7/-0
Offline Offline

Posts: 80


View Profile
« Reply #1 on: 01:33 PM - 07/28/10 »

Like you, I'm still fairly new to the XIM2. I've had it about a week now and I'm in love. The USB polling rate is really easy to change, and it makes a noticeable difference. I don't have the link on this computer, but I'm sure tonester has it saved somewhere. Combine that with a high DPI, and you'll be smoking people left and right.

Logged



mynameiscolb
d0nskii
Global Moderator
*

Karma: +63/-47
Offline Offline

Posts: 549


Northern California


View Profile
« Reply #2 on: 01:37 PM - 07/28/10 »

Mouse guide here: http://xim360.com/community/index.php?topic=3286.msg33303#msg33303
Logged

ryanolol
MVP
*

Karma: +8/-9
Online Online

Posts: 448



View Profile
« Reply #3 on: 02:15 PM - 07/28/10 »

lol when i saw the post name and the first words being with 'xim3' i thought it was a beta tester breaching his contract D:
Logged

"and cream lil kids" - JustMadMikeShad
ryanOLOLOL
Threewheels
Member
*

Karma: +5/-2
Offline Offline

Posts: 91


View Profile
« Reply #4 on: 02:24 PM - 07/28/10 »

 Grin Grin


thanks for the link d0nskii

edit:
just checked my config.. It looks like the G500 mouse and also the G3 (my backup) mouse run a 500hz polling rate natively.  No wonder the mouse felt so good right away.  checked on both the win7 64 machine and also on the netbook.

edit 2:
the logitech setpoint drivers (for the G500 at least) allow you to select up to 1000hz polling rate, so there is no need for the HIDusb tweek if you use setpoint.
« Last Edit: 11:01 AM - 07/29/10 by Threewheels » Logged
mist4fun
Global Moderator
*

Karma: +119/-60
Online Online

Posts: 3586


View Profile
« Reply #5 on: 04:33 AM - 07/29/10 »

Congrats threewheels, you're playing xbox on easy mode now Smiley
Logged

Have a problem with your XIM? Find a solution in the Support FAQ
ximhub.com
Rated Configs, Macros, and Scripts.. Go post!


How old are you? Click here
Threewheels
Member
*

Karma: +5/-2
Offline Offline

Posts: 91


View Profile
« Reply #6 on: 11:00 AM - 07/29/10 »

Yeah, it's great so far!  I played a few games last night, and it felt really nice.  Funny thing now, is I have to adjust to remembering which keys I've assigned to various functions like sprinting, crouching, 'nades, etc, lol.  But already, I've noticed my gameplay is a lot better.  I used to barely go positive on this game (K/D was 0.75), but last night I was went positive in every game, and finished in the top 3 except for once or twice.  

Only issue I have is when I try to slowly move the reticle in a vertical line (like tracing the side edge of a building), it jumps a little bit from side to side.  It's not bad, and isn't really noticeable in gameplay, but I'd like to figure out how to fix that.

I spent about an hour fooling around with each setting.  I noticed that increasing the deadzone made the mouse movement faster.  I'm guessing the deadzone moves the minimum analog input.  so a large deadzone circle just means your mouse movements will start at a higher analog value (I think).

I think I am starting to understand the DZ better, and am going to play with it some more.  

« Last Edit: 11:06 AM - 07/29/10 by Threewheels » Logged
wr194t
Member
*

Karma: +5/-2
Offline Offline

Posts: 42



View Profile
« Reply #7 on: 12:02 PM - 07/29/10 »

Only issue I have is when I try to slowly move the reticle in a vertical line (like tracing the side edge of a building), it jumps a little bit from side to side.  It's not bad, and isn't really noticeable in gameplay, but I'd like to figure out how to fix that.
What you're referring to is Zig-Zaging. I used to get it while playing Call of Duty. To fix it (if you haven't tried this already):

Open your config (.xim file) with Notepad
Find the line "AutoAnalogDisconnect=True" (located underneath "InputUpdateFrequency=Number Here")
Edit True to False
Save and close
« Last Edit: 12:22 PM - 07/29/10 by wr194t » Logged

wr194t
mist4fun
Global Moderator
*

Karma: +119/-60
Online Online

Posts: 3586


View Profile
« Reply #8 on: 07:16 AM - 08/02/10 »

^^ What he said. Threewheels, this fix and a whole lot more is in the support faq. Browse through it past the windows 7 stuff, there might be something in there you will need in the future.

Also when you apply the fix that wr194t mentioned it is only for that config your working on. It also disables your controllers physical analog sticks whenever you load that config. This may not be a problem in MW2, but in a game like BC2 where you want to pick up a controller to fly a chopper, or use a tank.. It can be a pain.
Logged

Have a problem with your XIM? Find a solution in the Support FAQ
ximhub.com
Rated Configs, Macros, and Scripts.. Go post!


How old are you? Click here
toysrme
13 National Championships
MVP
*

Karma: +69/-193
Offline Offline

Posts: 2082


FannyPAX, best avatar EVAAAR!


View Profile
« Reply #9 on: 09:47 AM - 08/02/10 »

disconnect the analog sticks & recalibrate.
Logged

Quote from: unknown
It feels like my hand is connected directly to the screen.
Threewheels
Member
*

Karma: +5/-2
Offline Offline

Posts: 91


View Profile
« Reply #10 on: 10:50 AM - 08/02/10 »

thanks guys, I read through the whole faq this weekend.  I had seen it before, but must have missed it last week when I first got everything setup.  I've pretty much decided to use it on my netbook and play in the Living room, since the input switch on my PC monitor is pretty flakey with the xbox for some reason.  Anyway, I got it fixed up really nice now, I just need to find some more time to myself so I can play more, haha.
Logged
 
Pages: [1]
Print
« previous next »
Jump to:  

Page created in 1.112 seconds with 17 queries.