Overclock.net banner
21 - 40 of 123 Posts

·
Registered
Joined
·
625 Posts
Quote:
Originally Posted by dobragab View Post

Thanks for feedback.

Did you install THIS update?
What operating system are you using?
Win 7 x64. All .NET 4.x: Full 4.0 standalone, and then 4.5x, 4.6x - from Windows Update. Nothing else.

Win7 x32 - without 4.6 work fine.
Quote:
Originally Posted by dobragab View Post

Then you should try installing .NET 4.0 Full.
After 4.5 and 4.6 installed??? It's bad advice.
 

·
Registered
Joined
·
1,653 Posts
error log:
Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.

************** Ausnahmetext **************
System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
bei MouseTester.MousePlot.MousePlot_Resize(Object sender, EventArgs e)
bei System.Windows.Forms.Control.OnResize(EventArgs e)
bei System.Windows.Forms.Form.OnResize(EventArgs e)
bei System.Windows.Forms.Control.OnSizeChanged(EventArgs e)
bei System.Windows.Forms.Control.UpdateBounds(Int32 x, Int32 y, Int32 width, Int32 height, Int32 clientWidth, Int32 clientHeight)
bei System.Windows.Forms.Control.UpdateBounds(Int32 x, Int32 y, Int32 width, Int32 height)
bei System.Windows.Forms.Control.SetBoundsCore(Int32 x, Int32 y, Int32 width, Int32 height, BoundsSpecified specified)
bei System.Windows.Forms.Form.SetBoundsCore(Int32 x, Int32 y, Int32 width, Int32 height, BoundsSpecified specified)
bei System.Windows.Forms.Control.ScaleControl(SizeF factor, BoundsSpecified specified)
bei System.Windows.Forms.ScrollableControl.ScaleControl(SizeF factor, BoundsSpecified specified)
bei System.Windows.Forms.Form.ScaleControl(SizeF factor, BoundsSpecified specified)
bei System.Windows.Forms.Control.ScaleControl(SizeF includedFactor, SizeF excludedFactor, Control requestingControl)
bei System.Windows.Forms.ContainerControl.Scale(SizeF includedFactor, SizeF excludedFactor, Control requestingControl)
bei System.Windows.Forms.ContainerControl.PerformAutoScale(Boolean includedBounds, Boolean excludedBounds)
bei System.Windows.Forms.ContainerControl.PerformNeededAutoScaleOnLayout()
bei System.Windows.Forms.ContainerControl.OnLayoutResuming(Boolean performLayout)
bei System.Windows.Forms.Control.ResumeLayout(Boolean performLayout)
bei MouseTester.MousePlot.InitializeComponent()
bei MouseTester.MousePlot..ctor(MouseLog Mlog, MouseLog Mlog2, Settings settings)
bei MouseTester.Form1.buttonPlot_Click(Object sender, EventArgs e)
bei System.Windows.Forms.Control.OnClick(EventArgs e)
bei System.Windows.Forms.Button.OnClick(EventArgs e)
bei System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.ButtonBase.WndProc(Message& m)
bei System.Windows.Forms.Button.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Geladene Assemblys **************
mscorlib
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.1055.0 built by: NETFXREL2.
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll.

MouseTester
Assembly-Version: 1.5.0.0.
Win32-Version: 1.5.0.0.
CodeBase: file:///C:/Users/XXX/Desktop/MouseTester_v1.5/MouseTester.exe.

System.Windows.Forms
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.1055.0 built by: NETFXREL2.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.

System
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.1055.0 built by: NETFXREL2.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll.

System.Drawing
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.1068.2 built by: NETFXREL3STAGE.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.

System.Configuration
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.1055.0 built by: NETFXREL2.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll.

System.Core
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.1055.0 built by: NETFXREL2.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll.

System.Xml
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.1064.2 built by: NETFXREL3STAGE.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll.

OxyPlot.WindowsForms
Assembly-Version: 2013.1.52.1.
Win32-Version: 2013.1.52.1.
CodeBase: file:///C:/Users/XXX/Desktop/MouseTester_v1.5/OxyPlot.WindowsForms.DLL.

OxyPlot
Assembly-Version: 2013.1.52.1.
Win32-Version: 2013.1.52.1.
CodeBase: file:///C:/Users/XXX/Desktop/MouseTester_v1.5/OxyPlot.DLL.

mscorlib.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.1055.0 built by: NETFXREL2.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_de_b77a5c561934e089/mscorlib.resources.dll.

System.Windows.Forms.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.1055.0 built by: NETFXREL2.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.

************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.

Zum Beispiel:

Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.
 

·
Registered
Joined
·
68 Posts
Discussion Starter · #23 ·
Nice bugreport, thanks!

The NullReferenceException is in MousePlot_Resize function, which is 4 lines long
kookoo.gif

I can think of only one possible problem, try if this version helps. Not sure though, really hard to debug if I can't reproduce it.
mad.gif

Please try this version, but I'm not sure this will fix it...

MouseTester_v1.5.1.zip 153k .zip file
 

Attachments

·
Registered
Joined
·
1,653 Posts
Quote:
Originally Posted by dobragab View Post

Nice bugreport, thanks!

The NullReferenceException is in MousePlot_Resize function, which is 4 lines long
kookoo.gif

I can think of only one possible problem, try if this version helps. Not sure though, really hard to debug if I can't reproduce it.
mad.gif

Please try this version, but I'm not sure this will fix it...

MouseTester_v1.5.1.zip 153k .zip file
no, unfortunately still the same.
frown.gif
 

·
Registered
Joined
·
625 Posts
Quote:
Originally Posted by thuNDa View Post

no, unfortunately still the same.
frown.gif
It always be the same!

public MousePlot(MouseLog Mlog, MouseLog Mlog2, Settings settings)
{
InitializeComponent(); //implicit call of MousePlot_Resize

this.settings = settings;
......................................

private void MousePlot_Resize(object sender, EventArgs e)
{
if (this.WindowState == FormWindowState.Normal)
settings.maximized = false; // !!! use of uninitialized object
else if (this.WindowState == FormWindowState.Maximized)
settings.maximized = true;
}

dobragab, simply swap InitializeComponent(); and this.settings = settings; lines
 

·
Registered
Joined
·
68 Posts
Discussion Starter · #26 ·
Thanks SweetLow, was about to ask u to look at the source
smile.gif
Hope this will fix it
biggrin.gif


I tried changing to .NET 4.6.1 on Win10 and Win8.1 x64 too, didn't reproduce the bug. I have no idea why did the ctor call MousePlot_Resize implicitly on ur PC, and not on mine.

MouseTester_v1.5.2.zip 153k .zip file


#27
Indeed. Wrong file, changed attachment.
 

Attachments

·
Registered
Joined
·
625 Posts
MouseTester.exe 57344 11.02.16 00:18
But i send my post at 0:30. Are You have time machine?
wink.gif

P.S. all is much better now
thumb.gif

P.P.S.
>I tried changing to .NET 4.6.1 on Win10 and Win8.1 x64 too, didn't reproduce the bug. I have no idea why did the ctor call MousePlot_Resize implicitly on ur PC, and not on mine.

No, it's not version sensitive - i reproduce bug on pure v4.0. More like this is any kind of multithreading initialization in action.
P.P.P.S. No, it's not the multithreading. More subtle problem! You design form at 96 dpi. But i (and probably thuNDa) use HiDPI displays (i use 144 dpi)
wink.gif
 

·
Registered
Joined
·
68 Posts
Discussion Starter · #28 ·
Quote:
Originally Posted by SweetLow View Post

More subtle problem! You design form at 96 dpi. But i (and probably thuNDa) use HiDPI displays (i use 144 dpi)
wink.gif
Again, you are right. I know high DPI is a pain in the butt with C# winforms.
mad.gif

I just tested in virtual PC and I'm sure that caused the bug. Thanks
thumb.gif


I also found some bugs I'm not proud of. So the latest version is v1.5.3 now, updated first post.
 

·
Registered
Joined
·
5 Posts
Hey everyone! I'm new to OCN and I'm trying to optimize my Razer Imperator 4G a bit. I'll probably end up just buying a different mouse soon, but testing never hurts. Below I did a few basic tests, but ran into some issues.

If anyone could point me in the right direction on how to fix/interpret these issues I'd really appreciate it. For reference, my Imperator is set to 800 DPI. Can also post system specs if anyone would like me to.

xCounts:
I did an xCounts test and included the yCounts just in case anyone was interested. I did this twice just to be on the safe side.

First test


Second test


From what I understand, everything looks decent here.

xVelocity:
Next up, I did a velocity test to see how it handled quick speeds. I swiped pretty quickly, and ended up with some silly results. Again, I tested this twice.

First test

Points spiked to 100 m/s. No idea why this happened.

Second test

This time it spiked to 120 m/s. If my hand was really that fast, I'd probably become an MMA fighter.
thumb.gif


It's hard to get useful data when these spikes happen, so that's a bit frustrating to see.

I've considered disabling my C-states in BIOS, but I read a lot on my computer when not gaming and don't want to raise my power bill too much from staring at text for 6 hours with my CPU on full blast. Will disabling C-states cause any meaningful changes in things like my PC hardware lifetime/power bills? I'd rather not tax my wallet or my computer if I can avoid it.

Anyways, we've still got one test left...

Intervals:
Finally, I made some small circles for a few seconds to check my polling rate. Mouse is currently set to 1000Hz.

First test, moving mouse quickly


Second test, moving mouse at a normal rate

For this one, are the spikes/scattered points at the beginning just junk data? If so, what would be a good ms to cut off the data at?

Not 100% sure, but my polling rate seems fine. I'm not sure what constitutes an unacceptable deviation - but I'd love to hear from everyone else.

So to cap this post, my questions are...

1) Is my xCounts tracking test done correctly? Are the results good?
2) Why am I getting huge spikes on my xVelocity tests?
3) Are the spikes on polling rate test #2 just junk?
4) Is my polling rate consistent? Are these results good as well?
5) How will C-states impact my hardware's lifetime and/or power bills?


I've been into this for some time, but mostly as a lurker. I'd like to learn a lot more, so you might see me around more regularly.

Thanks in advance for any help I get!
 

·
lololol
Joined
·
4,382 Posts
1. yes/yes
2. xvelocity = xcounts/interval. spikes in xvelocity correspond to intervals that come close to 0. see http://www.overclock.net/t/1550666/usb-polling-precision/0_100.
sometimes, it's for a much more innocuous reason: you have two mice plugged in, and as you swipe one, you accidentally move the other one by a pixel or something. this leads to two data points very close together, but from separate mice, but mousetester only recognizes this as a short interval.
3. hard to tell. sometimes, bad mouse firmware skips usb reports. it could also be your pc/os acting weird.
4. see haggard's thread linked previously
5. disabling some c states isn't the same as running your pc at full load all the time. i don't think the idle power from keeping a pc in c1 is something to worry about.
 

·
Overclocker
Joined
·
11,688 Posts
How to compare two mice in terms of input lag? It's been a while since I've done this.
Dual device, set CPI for both, hold them together and move both at once while collecting? Then check X/Y?
I'm finding that the angle and precise CPI they are at makes the curves for both a little different.
 

·
Registered
Joined
·
68 Posts
Discussion Starter · #34 ·
Exactly.

Usually you need some DPI correction, just increase or decrease the DPI of a mouse until the Velocity graph shows same speed for both mice. I usually move them left and right only, so the angle difference does not disturb me. Then change input lag value until the graphs cover each other.
 

·
Registered
Joined
·
68 Posts
Discussion Starter · #35 ·
Quote:
Originally Posted by qsxcv View Post

3. hard to tell. sometimes, bad mouse firmware skips usb reports. it could also be your pc/os acting weird.
Just realized that graph might show that the cable is about to die. It loses data connection for a few seconds but still gets voltage, so counts the measurement. When data connection recovers, it sends all the data in one poll.
 

·
Overclocker
Joined
·
11,688 Posts
Quote:
Originally Posted by dobragab View Post

Exactly.

Usually you need some DPI correction, just increase or decrease the DPI of a mouse until the Velocity graph shows same speed for both mice. I usually move them left and right only, so the angle difference does not disturb me. Then change input lag value until the graphs cover each other.
xSum vs Time graph? That seems to work best and I get 8ms delay.

Please add legend with which mouse has what colors in graph.
And also note where is the delay added, is it mouse 2 is slower by Xms than mouse 1 when X is positive?

I'm not even sure I got the delay right how do you really measure it from these graphs? I look at first count but then last is also delayed in opposing way which is weird. Can you make a picture as an example?
 

·
Registered
Joined
·
1,149 Posts
Why is it that whenever I need this file most urgently, the download link always refuse to work at precisely this time? Can't you upload the binary to GitHub instead?
 

·
Registered
Joined
·
23 Posts
Quote:
Originally Posted by daniel0731ex View Post

Why is it that whenever I need this file most urgently, the download link always refuse to work at precisely this time? Can't you upload the binary to GitHub instead?
MouseTester.zip 158k .zip file


I'm gonna assume I'm allowed to upload it... Here's the version I have, I believe it is the latest. Obviously not responsible if you computer blows up or your mouse flies away.
 

Attachments

·
Registered
Joined
·
1,149 Posts
Still the same:

 
21 - 40 of 123 Posts
Top