Close
Page 1 of 3 1 2 3 LastLast
Showing results 1 to 10 of 21
  1. #1

    Default Input Device compatibility testing with KVM & KM switches

    Results of testing of various devices (Keyboards/Mice) with various synchronous KM/KVM switches with ratings as:
    • GOOD: Programmable macros & added functionality work as intended;
    • OK: Device functions but only with default key-binds or as a plain keyboard/mouse;
    • BAD: Device unusable or key pieces of the device do not function at all;

    Note: It is likely that the Aimos 4 port and 8 port both work identically but just in case not we will denote which devices have been tested with which switch...

    Test results with an Aimos 8 port Synchronous KM switch (also on newegg) will be preceded by an 8:
    Test results with an Aimos 4 port Synchronous KM switch will be preceded by a 4:
    Test results verified as identical on both will be preceded by an 8+4:




    Test results against the ShuOne 8 port Synchronouse KM switch (HowTo optimize):

    • NOTE: See the next post below as this post exceeded the max characters allowed...
    Last edited by nodoze : Yesterday at 07:59 PM

  2. #2

    Default

    Continuing from above...

    Test results against the ShuOne 8 port Synchronouse KM switch (HowTo optimize):


    Test results against the FJ Gear US-108 8 port synchronous KM switch (this may be similar to the ShuOne):


    • NOTE: See the next post below as this post exceeded the max characters allowed...
    Last edited by nodoze : Yesterday at 08:01 PM

  3. #3

    Default

    Continuing from above...

    Test results against the FJ Gear US-108 8 port synchronous KM switch (this may be similar to the ShuOne):


    • GOOD to OK: Corsair K70 RBG Rapidfire (source:bpkdasbaum see details);
    • GOOD to OK: Mouse Logitech G700S (source:bpkdasbaum see details);

    NOTE: The FJ Gear US-108 KVM has a 3 key rollover limit.
    Meaning when you walk forward (1), strafe(2) and rightlick mouselook(3) at the same time, the mouse will sometimes lose focus due to signal updates of continuous mouse, but catches itself again.
    When additionally pressing a spell button (4) the mouse will always lose focus.
    Last edited by nodoze : Yesterday at 07:49 PM

  4. #4

  5. #5

    Default

    Thanks bloodshot for all the testing info.

    The initial post at the top of the thread has been updated with everything up to this post. Thanks for submissions thus far and please post to the end of this thread any corrections or new submissions. Please link to original sources if from other threads/sites and I will try to include the links in the summary.
    Last edited by nodoze : 11-22-2020 at 10:16 AM

  6. #6

    Default Orbweaver chroma Shuone

    Quote Originally Posted by nodoze View Post
    The initial post at the top of the thread has been updated with everything up to this post. Thanks for submissions thus far and please post to the end of this thread any corrections or new submissions. Please link to original sources if from other threads/sites and I will try to include the links in the summary.

    I can confirm using a shuone that as long as the host pc has razer synapse on it with the keybinds configured for each connected pc that the orb weaver will completely function including the d pad. You CANNOT use any of the keyboard shortcuts to turn sync off/on with shuone. Work around I found is using the d pad for team movement then using the wasd keys on orbweaver for main movement.

  7. #7

    Default

    Quote Originally Posted by sgtopus View Post
    I can confirm using a shuone that as long as the host pc has razer synapse on it with the keybinds configured for each connected pc that the orb weaver will completely function including the d pad. You CANNOT use any of the keyboard shortcuts to turn sync off/on with shuone. Work around I found is using the d pad for team movement then using the wasd keys on orbweaver for main movement.
    Thanks for the info. Glad to see that on the Orbweaver (which also worked on the Aimos).

    The initial post at the top of the thread has been updated with everything up to this post. Thanks for submissions thus far and please post to the end of this thread any corrections or new submissions. Please link to original sources if from other threads/sites and I will try to include the links in the summary.

  8. #8

    Default

    Quote Originally Posted by sgtopus View Post
    I can confirm using a shuone that as long as the host pc has razer synapse on it with the keybinds configured for each connected pc that the orb weaver will completely function including the d pad. You CANNOT use any of the keyboard shortcuts to turn sync off/on with shuone. Work around I found is using the d pad for team movement then using the wasd keys on orbweaver for main movement.
    How did you get your orbweaver to work with the shuone? Mine doesn't want to see it, on either computer.

  9. #9

    Default

    Yesterday I got a 44 key Koolertron key pad (B076LZJ5JS on US Amazon) and have tested it with the ShuOne 8 port and the AIMOS 8 port. Here is what I have experienced so far. I've only tested this with a single player at the moment. While I do not expect the AIMOS results to change with multiple characters playing, I'll update my post if that ends up being the case.

    With ShuOne: BAD Completely unusable as the KM sync ignores the device entirely, even for basic movement keys. Likely incompatible due to the VID/PID hiding feature on the ShuOne.

    With AIMOS 8 Port: Somewhere between GOOD and OK. Very much usable with the exception of single button port swapping. All of my basic keys work, as do the hotkey buttons that send a keystroke with modifiers. You can use a burst key configuration with NUM* and NUM0 to turn sync on/off.

    Round robin key actions also work, which was one of the things I wanted this device for. This lets you define a button where one of three different keys are sent in sequence. Each key press sends the next key each time you press the button. My intention is to use this as a totally EULA compliant IWT key. My sequence sends move back (bound only on melee chars), my IWT key and then my DPS key.

    A burst key configuration did not work for direct port access like it did for Sync On/Off. I believe this is because the sync on/off hot key does not require you to let go of NUM0 before letting go of NUM*, which is how the direct port access hot keys work. This does not mean you cannot direct swap ports, you just need to be sure to allocate keys to NUM* and NUM1 ... NUM5 (or however high you need to go). You will need to get used to the release pattern to properly swap the port as the # key must always be released before NUM*.

    Here is a screenshot of my current configuration:


    Here is how I have my Sync On burst key configured:


    I tried many of the other types of key configurations to enable single key port swapping with no luck, this include Two Key Click configurations. If the proper key values can be determined for NUM* and NUM1 through NUM5 it should be possible to create a macro to swap ports with a single key. After spending over an hour on that I have not gotten one to work.

    Based on my experience thus far, I do not think the "Press/Release" options in the macro script editor will work. Using that option seems to bypass the AIMOS's interpretation of the key being pressed. When I run such a macro in this window I see the key output and the AIMOS does not switch. Example if I press my macro key to switch to port 2 :
    PHP Code:
    *
    I'm very new to Koolertron devices but this behavior seems to indicate the device is sending the value outputted by the key that was "pressed" as opposed to registering the key itself, if that makes sense?

    If a macro can be crafted to switch ports, it will likely have to be use the KeyDown and KeyUp actions. Unfortunately it has proven somewhat challenging to decipher the included USB HID key table PDF for activating the numpad keys. The software is not clear if you're supposed to use the decimal, hex or AT position key values. The HEX option seems off the table as that generally resulted in Key00 showing up in the macro. If anyone knows more about the proper place to find a definitive list of KeyDown/KeyUp for use in Koolertron Macro Script, please share.
    Attached Images Attached Images    
    Last edited by Wootenblatz : 11-22-2020 at 03:50 PM Reason: Adding round robin description; Adding GOOD/BAD/OK indicators.

  10. #10

    Default Orbweaver chroma Shuone

    Quote Originally Posted by skeezy View Post
    How did you get your orbweaver to work with the shuone? Mine doesn't want to see it, on either computer.

    I first configured and installed the synapse software on host pcs. I plugged orbweaver into each pc to configure the keybindings. The I disconnected it and connected the shuone. I plugged it into the keyboard port and did a test with selecting notepad if all of the keys replicated correctly. Let me know if this helps.

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •