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

Pages: [1] 2 3 ... 34
1
OBsIV,

Other than the post that you made in the Qt forums, there really doesn't seem to be any mention of this issue. Although this post (http://qt-project.org/forums/viewthread/48273/) seems to relate to older versions of Android (so it may be irrelevant),  the comment saying that Qt 5.4 fixes the issue might apply to you. Who knows :)

Best of luck!

2
XIM 4 Discussions / Re: XIMCommander vs XIMBridge SDK
« on: 05:09 PM - 07/28/14 »
Hi guys!

I found the source for my apps (XIMCommander.NET and DeadZoner), and while I don't have the time to do big changes to the apps right now, I'm willing to port them to the new SDK if it's not too different from the old one.

I'd also love to release all the source in the future (once I do some cleanup!). We'll see...

3
Release Candidates / Re: Halo 4 Translator
« on: 01:17 AM - 11/08/12 »
Feels pretty close to Reach.

4
Release Candidates / Halo 4 Translator Feedback
« on: 01:12 AM - 11/08/12 »
It feels great! Good job once again! :)

Compared  to the Reach translator, it has the same feel to it, but it allows for much smoother movements, especially when moving the crosshair very small distances.

5
XIM 3 Discussions / Re: New XIM Sensitivity Calculator!
« on: 11:06 PM - 07/28/12 »
I have used the DPI calculator to convert the values from 2000DPI to 3200DPI and just found a minor error. I think the calculator assumes linearity between sensitivity and DPI values, whereas the values found using the square law gives more accurate result (since DPI is spread across the total area). I checked it and the results feel alot closer that way.

So lets say 14.45 @ 2000DPI does not feel that close to 9.03 @ 3200DPI (according to the calculator)

Its more close to 11.4 @ 3200DPI using the square in the equation

 == > DPI is inversely proportional to the Square to Sensitivity Value.


Before I reply, everyone, this thread is more than a year old. Let's keep information about the Sensitivity Calculator in the stickied thread under the Configs subforum :-) I don't want this thread to keep getting bumped.

Regarding the DPI relationship:


I have to disagree here. DPI is dots per inch, not dots per square inch. A dot is a movement unit that is reported to the host, and the mouse's DPI is how many dots (or counts) the mouse reports when it's being moved by an inch. I'm not too sure why those values feel better for you. How exactly did you measure it? I definitely wouldn't trust just feeling on this one, considering how small the margin of error is.

Thanks for the heads up, though.

6
XIM Apps / Re: XIMCommander.NET
« on: 03:36 PM - 04/28/12 »
Unless someone can reproduce this consistently, I don't think it's the USB poll rate. I have my mouse set to 1 khz and I haven't had any issues with the XIM update rate recently.

My app is clocked with the XIM, so USB poll rates cannot directly affect it. If there is an actual issue with poll rates, then it's because a device is making the transfer cable malfunction (which doesn't seem very likely to happen).

7
Just wanted to mention that this used to happen to me all the time with the original XIMCommander, and it was part of the reason why I ported it. Turns out my version did it too, which is why I added a simple logger to keep track of these errors. I used this to try to troubleshoot my setup, but never found out what did it. It hasn't happened in a while now.

It seems to be a common issue for my users, though, so I would love to find out what's causing it.

8
XIM 3 Discussions / Re: mouse ,what one do you use ?
« on: 12:32 AM - 04/22/12 »
I went from a G5 to a G500 to a G700. I'm LOVING having wireless for the mouse, as the cord always gets stuck in something, or it drags across the mouse pad.

I love the G700, but I already had two mice with problems where one of the buttons wears out in less than 6 months. I thought about jumping ship to Razer, but I heard their mice also have that problem every now and then -- I'm guessing they use the same button manufacturer or manufacturing process. Another big reason why I haven't switched yet is because Logitech has incredible tech support. They will replace your hardware very quickly if you're having issues.

If anyone knows of a great XIM3 wireless mouse that's up there with the G700, please let me know :)

9
Feedback / Re: Alternate to 'Black Dot': Dot Debt?
« on: 01:10 PM - 04/07/12 »
Regarding your questions, mouse movements did not feel at all laggy while inside the black dot zone. It's once you're outside the zone that the mouse felt laggy as one would have screen movement for a long length of time after the user stopped moving the mouse.

I implemented the control loop the way you described it, by having a black dot buffer, and removing from it until the max mouse speed wasn't exceeded. This made it feel  1:1 in the angle domain, but very unpredictable in the velocity domain. Overshooting and then correcting took too long, making it impossible to quickly turn around and aim at a target behind you. After this, I also tried removing the feedback when the user is attempting to correct from overshooting: I simply made the app ignore the buffer if the user suddenly changes directions, which allowed one to turn around in one quick motion, and then cancel out of it to regain control over the aiming system. What I noticed was that even then, turning around didn't feel at all natural, still feeling laggy as the system responds to past-time input, and the cancelling feature was easily triggered by accident, removing any apparent advantage.

By the way, the SDK sends raw mouse, keyboard, and joystick data to the XIM. This is then interpreted as if a physical device was sending the data directly to the XIM. All user settings, including smart translator settings, are used to process the input. The XIM requires an extra processing cycle for the SDK, so it halves the processing frequency from 125 Hz to 62.5 Hz. Input is still fast enough for most games.

Let me know if you have any other questions!

10
XIM Apps / Re: XIMCommander.NET
« on: 10:18 PM - 04/04/12 »
I don't know much about it all, but since the Xim3 usually uses a usb port each for the keyboard and mouse could it be struggling to send the data down one usb cable? I use the    
"F5U279EA Belkin Easy Transfer Cable for Windows 7" http://www.itinwales.co.uk/images/3539221-8239.jpg I'll try lowering the polling rate later.

Haha, no. There's plenty of bandwidth for both! Also, the XIM doesn't allow for the host to send data faster than it can process it, which means that even if the polling rate is higher than the XIM supports, the computer will have to wait until the XIM is ready to send its information. Not quite sure what causes the issue, but please let me know if lowering the polling rate makes it go away.

11
XIM Apps / Re: XIMCommander.NET
« on: 10:42 AM - 04/04/12 »
If I just use this app to connect my mouse/keyboard via pc will it affect my sensitivity if i don't change anything?

If thats all you want, i would take a look at this: http://www.xim3.com/community/index.php?topic=18921.0

Thats what i use for mouse/keyboard passthru, you can tick "Xim3 Mouse" in the app, that sends all mouse activity directly to the Xim3, so you still use your Xim3 mouse settings and STs :)

And you can passthru Right Mouse Click too, for ADS STs :)

XIMCommander.NET does just that by default! :)

I tried it but it changes my sensitivity randomly when playing it starts off okay then it goes slow. I have my polling rate at 1000hz is this not supported?


This is not the app. It's the XIM SDK. I'm still not quite sure why it happens, but it happens even with the XIMCommander OBsIV made. :/
Try lowering the polling rate and let me know if that fixes things. The Xbox can't take advantage of anything higher than 125 Hz anyway.

12
XIM Apps / Re: XIMCommander.NET
« on: 07:41 PM - 04/03/12 »
Thank you very much!

I just tested it out and its working perfectly.  I just played and entire match wirelessly with the nav and g700 and there seems to be no hicupps.   To get around the secondary sensitivity issue I used xpadder to send a keystroke every time I hit the trigger on the nav.  I bound that same keystroke to my secondary sensitivity trigger and it seems to be doing the job exactly how it should.  Its kind of a weird fix but it works!

Dunno if binding a keystroke to a joystick button would be possible from within xim commander, but it definitely works with xpadder running.

Thanks a lot I really appreciate the work!   I'm off to rock some matches with no wires in the way!

Glad to hear it works well!

You may think your setup is convoluted, but it is probably the best way of doing things. If I were to add some kind of remapping ability to the app, it would increase the difficulty of use of the app by quite a bit. It would be very similar in complexity to your setup, but with the only advantage of having it all in one app. It's just too much work for something that's not very elegant.

By the way, sorry I took so long! School is keeping me busy, and I ended up delaying this until spring break. It didn't take me long to implement the feature, but I had to re-install Windows a few weeks ago, and I hadn't gotten around to installing Visual Studio until now :P

13
If I just use this app to connect my mouse/keyboard via pc will it affect my sensitivity if i don't change anything?

If thats all you want, i would take a look at this: http://www.xim3.com/community/index.php?topic=18921.0

Thats what i use for mouse/keyboard passthru, you can tick "Xim3 Mouse" in the app, that sends all mouse activity directly to the Xim3, so you still use your Xim3 mouse settings and STs :)

And you can passthru Right Mouse Click too, for ADS STs :)

XIMCommander.NET does just that by default! :)

Ok awesome, Thanks for the reply.  Is a secondary sensitivity triggered through the enabled joystick a possibility, or would that not work through XIMCommander?

Updated it! Give it a try and let me know if I added any bugs :)

14
Ok awesome, Thanks for the reply.  Is a secondary sensitivity triggered through the enabled joystick a possibility, or would that not work through XIMCommander?

I don't think that's possible. Sorry.

15
Feedback / Re: Alternate to 'Black Dot': Dot Debt?
« on: 02:58 PM - 04/03/12 »
So I just added this feature to my XIMCommander app, and it didn't really do too well. It just felt unpredictable and laggy, whereas having a black dot feels more like having negative acceleration (which can be accounted for).

It's too bad, though. I was hoping this would be really awesome :/

Pages: [1] 2 3 ... 34