Jitter with 1.01 drivers but not with 1.0

[OoGhiJMIQtxxXA]

Anyone else having this problem? With the original drivers the cursor in games is rock steady but with the 1.01 driver I have bad jittering in game. I saw the post about lowering latency and I think it may help but I'm not clear on what values make it higher or lower. I rolled back to 1.0 for now but I would really like to get the 1.01 drivers working better because these some neat stuff in the new motion creator I'd like to use that doesn't apply to the older version.

[Dan]

Hello,

Can you download the Sixense Beta App from the Beta Release Thread and let us know if you still have the jitter?

[OoGhiJMIQtxxXA]

Sorry a reply took so long. (Almost a year) Ran into some pc problems and haven't had time to do much. Anyways, I have no idea how to use any of the apps for the Hydra. I haven't even ever used the Motion Creator in any of it's releases. I thought that the drivers you can get from the Razer website was the Motion Creator but I guess the Motion Creator is a separate app from the drivers. I just always used the 1.0 drivers that were released with the Hydra and created mce's and xml's by opening existing files in wordpad and rewriting them for the games I want to use them on. I've since just stuck with the 1.0 drivers that bring up the icon in the toolbar and open the window with the games list and sensitivity settings since I can't seem to get the jittering to stop with any of the newer drivers. I'm satisfied with that though because I don't really like the integrated profiles for games like Team Fortress 2 were the look on the right joystick moves slow with slight angles and fast for larger ones. It feels too much like using a joystick in fps's and since that's what I primarily use the Hydra for I just stick with using straight mouse emulation with the ratchet button. I seem to be alot more accurate this way and using the Hydra in this way, am very satisfied with the results. Since it's what I've grown use to now because I've been using the Hydra this way for so long I think I'll just stick to this method. No reason to fix what isn't broken, right? lol

[Danny]

You definitely want to ditch the Razer app and use the latest MotionCreator. They are the same product, but the Razer version is over a year old. Grab the latest MotionCreator and be pleasantly surprised.

[OoGhiJMIQtxxXA]

A couple quick questions. Can I use profiles I've made (mce's) with the latest MotionCreator? Also, does the end result amount to the same functions and responsiveness in game? Because I ran into a lot of jitter with the 1.01 drivers and the responsiveness seemed kind of sluggish compared to what I seem to get with the 1.0 drivers. I would also like to know if there is a tutorial anywhere for the MotionCreator because after the first response I got I downloaded the Sixense beta app but had no idea how to run it. If I remember correctly I didn't see any type pf install or exe file. I'll give the latest version a try and see how it works for me. I made a few mce's for quite a few games and doing it through wordpad making changes to mce and xml files was kind of a pain. If it's easier to create profiles in MotionCreator it would definitely be a plus. Also, should I uninstall the old drivers before I install the MotionCreator?

[OoGhiJMIQtxxXA]

Ok, tried the MotionCreator and I prefer the drivers I have been using. The jitter I had with 1.01 drivers is gone but only if I don't breath and hold the controller perfectly still. With the 1.0 drivers when I look right or left the plain the view moves on stays more or less level unless I make a conscience movement up or down. With the MotionCreator the view floats around a lot for me when I look side to side and makes the control feel sluggish and unresponsive. The GUI for the MotionCreator didn't show key bindings for the mce's I added to the user documents folder though they still worked but I like the picture I get with the 1.0 drivers. I play a lot of games with the Hydra and have either made my own or made changes to about 36 mce's and it's sometimes hard to remember what I put where in the profile for every game. The picture of the controller in the old drivers worked a lot better for me at a glance to remind me of my bindings. Unfortunately in uninstalling the Razer drivers and installing MotionCreator I forgot to back up the xml files I used to show the profiles I made and the ones I made changes to and lost them all. So I have to go through the arduous process of rewriting them since the copies of them I posted here on the forums got removed I suppose because the new versions of MotionCreator doesn't use them.

[Danny]

You would be the very first person to prefer the Razer application. I am not sure what you are trying to tell me is different for you in the beta app compared to the Razer app. What game are you playing with that causes the cursor to feel sluggish? It almost sounds like you are using wand mode with no acceleration and have the dynamic filter enabled.

Also:
- All mces from Razer's app will work with the MotionCreator Beta.
- There is an editor included in the beta application also.
- You can view your layout by rigth clicking on the game and selecting view bindings -> layout
- Put your mce's in your My Documents/Sixense Entertainment/MotionCreator 2/configs folder for the beta app. This way you will never lose work because of uninstalling or reinstalling.

One thing that comes to mind with the 1.01 version changes that you might be feeling is that we keep track of fractional pixels in 1.01 and add them to the next mouse move call. This gives you much more precision. Without that feature you could move the controller very very slowly and not have any moves registered because the amount of pixels you are trying to move is less than 1. Now I am beginning to think your Hydra is suffering from some interference or that it just a bit more noisy than other Hydra's


Can you try this test and report your score:
http://sixense.com/motioncreator2/SixenseQuickTest.zip

[OoGhiJMIQtxxXA]

I ran the SixenseQuickTest and with the controllers laying like they are in the photo I get 94 percent and 98 score. With the controllers resting the distance I normally use them at I get 103/109. When I run the QuickTest with the MotionCreator2 open the mouse cursor moves all over the place. I'm not sure if I'm using the test correctly but those were my results. I do like the MotionCreator2 a lot better as far as creating profiles go and looking at the newer format that the mce files save as gave me some insight on how to write them better. Although with the old mce files the names of bindings weren't used because the xml file is what showed the bindings in the layout so I had to put them all in for 63 mce's that I had either made or changed the layouts for, which took several hours. As far as the Hydra not registering when movement is very slow, I never noticed it till you mentioned it, I guess I never moved that slow in game. I still prefer the feel of the old drivers better though. I tried different sensitivity and filter options in Counter Strike GO and Battlefield 3 so far and in both instances I feel like the cross hair floats across the screen and I find it much harder than it was before to keep my view level without it drifting up or down. Also when I look in the opposite direction quickly it seems to not respond as fast as the old drivers did. I was really trying to like the MotionCreator2 because there ARE a lot of features I really like about it (and I was trying to avoid having to rewrite 63 xml files) but in the end the feel in game to me is whats important and the 1.0 Razer driver feels more solid and responsive for me and my situation, be it I have a lot of interference in the area or just a noisy Hydra.

[Danny]

That is about what I would expect. Since you are playing close to your base station (reported from the other theread) I really think what you are feeling is:

One thing that comes to mind with the 1.01 version changes that you might be feeling is that we keep track of fractional pixels in 1.01 and add them to the next mouse move call. This gives you much more precision. Without that feature you could move the controller very very slowly and not have any moves registered because the amount of pixels you are trying to move is less than 1.

The 1.0 driver is losing a lot of mouse movement data which you have grown accustomed to or rely on. There are some dynamic filter settings you could try to adjust. The dynamic filter's main purpose was to remove jitter as your hand is being held still. In MotionCreator2 preferences, hold down left ctrl and click the dynamic filter checkbox. Other than that I don't think I could recommend anything further for you. Disabling the dynamic filter should feel like the 1.01 Razer app

[Kiwii]

Danny, would it be a big deal to implement an option to disable the tracking of fractional pixels? That way, he (and other who may prefer the 1.0 driver) could use MotionCreator and have the exact feeling that he had with the old driver.