MP2 - V2.3 MP2 & USB Problems (2 Viewers)

[MP2 Fan]

Direct Connect Tests

I think this is about all we can do. The following screenshots are from a clean v2.2.3 Client installation, using firstly a Logitech Trackman which connects directly to USB then secondly using my preferred Trackman Marble FX which connects via a PS2/USB adapter.

The results show that the system works perfectly under these circumstances.

Therefore, as previously stated, the errors only occur when both the KVM AND ShellLibHID are both present (note that the equipment list appears completely different here compared to above with the KVM in place.

As I don't have space to have a second keyboard/mouse just for MP2 testing, I'll have to just do what I can on my client machines ~(both Win10 Intel NUCs).

Trackman shots

Marble FX shots

 

[henso]

I only included them because Henso asked me to above. I presume that's why they are not enabled by default in HID Demo.

Yes, I know. I wanted to check if the mouse sends messages when not used. Can you check if there are messages logged when not touching the mouse or keyboard at all?

I also presume MP2 client uses it to basically 'debounce' replicated messages.

It ignores mouse move messages, but it still has to process each message.

How come SharpLibHID is listed as an installed NuGet package and yet all references to it in 'InputDeviceManagement.cs' are greyed out (the Includes statements)?

You mean the usings in InputDeviceManager.cs? They are shown as used for me (which they are).

Could you try the attached ClientLauncher with KVM switch? You need to have MP2 client installed and put this in the same location as the existing one. Then start and check if you still have the issue. If you have then close it (right click and select close from the notification area) and attach the ClientLauncher.log file.

 

[MP2 Fan]

HID Demo run with KVM. No spurious events logged.

usings in InputDeviceManager.cs, yes. They are greyed out and all code references further down the page are underscored in red as errors. Also ShellDllHID is not in any of the module references, nor in the Project Dependencies list. I have 97 projects in the Client solution.
I downloaded it because I was going to start looking at developing a skin. The few that there are seem to come from in-house and I have a few things I would like to try.

Back to the tests. The new ClientLauncher made no difference at all. Keyboard still buffers out at 22 characters. You then have to wait 3/4 seconds to the response to pick up. Anything typed in those few seconds goes down the sink

BTW. The test ClientLauncher is v2.3 only. It crashed when I tried it with the v2.2 Client that I already had installed.

 

[henso]

BTW. The test ClientLauncher is v2.3 only

Yes, I should have mentioned that. What about the log file I requested?

 

[MP2 Fan]

Yes, I should have mentioned that. What about the log file I requested?

Two here. First after initial install. Then I switched it off to get some normality.

Then ran it again manually to give you another set for this post.

 

[henso]

Then ran it again manually to give you another set for this post.

Thanks for that. Could you try this last version for now?

 

[MP2 Fan]

New CllientLauncher installed and run. Logs attached.

Done for tonight. 18:30 here.

 

[henso]

New CllientLauncher installed and run. Logs attached.

Thanks. The issue was still present?

 

[MP2 Fan]

Thanks. The issue was still present?

Yes, I'm afraid. No change.

 

[henso]

@Stéphane Lenclud
Any idea why starting HID Demo causes input delays for keyboard and mouse connected to an KVM switch?