hardwareAll guides

KMBox Net vs MAKCU vs Ferrum

Three ways to put the aim of the second PC into the game PC. They do the same job; what differs is the link they take their orders on, and that is what should decide.

Contents
  1. 01They do the same job
  2. 02The difference that matters
  3. 03Picking one
  4. 04In the menu
  5. 05About latency

01They do the same job

All three sit between your mouse and the game PC. Your movements pass through; when the second PC has a correction to make, it sends it to the box and the box adds it to the same USB stream. The game PC sees one ordinary mouse and nothing else.

So the question is never "which one aims better". The aim is computed on the second PC and is identical in all three cases. The question is how the box receives it.

02The difference that matters

  • KMBox Net takes its orders over the network, as UDP packets to an address and a port. The second PC needs no cable to it at all - only a network path.
  • MAKCU and Ferrum take theirs over a serial link: a second USB cable from the box to the second PC, seen there as a COM port.

That single difference decides the cabling, the failure modes and, usually, the choice.

03Picking one

Take the KMBox Net when the two machines are not next to each other, when you want the second PC to be a laptop you move around, or when you are short of USB ports. Its failure modes are network ones: an address that changed, client isolation on the access point, a VPN swallowing UDP.

Take a MAKCU or a Ferrum when both machines sit on the same desk. A cable has nothing to configure: no address, no port, no UUID. Its failure modes are driver ones: a missing USB serial driver, a port already held by another program, the wrong baud rate.

If you have none of them yet and the machines are side by side, serial is the shorter path. If your second PC moves, the Net box stops being a cable problem.

04In the menu

The products ask for the same thing either way: Settings > Device, then the device type.

  • Serial (MAKCU, Ferrum, KMBox B): a port, which Auto finds on its own, and a baud rate - 4000000, or 115200 for a box that only speaks that.
  • KMBox Net: an IP (192.168.2.188 by default), a port (8965) and the eight-character UUID shown on the box screen.

Auto-connect makes either of them come back by itself at the next launch, so this is a one-time setup.

05About latency

On a local network a UDP packet and a 4 Mbaud serial write are both far below the time it takes the game to draw the next frame, so neither is a bottleneck for aim. A 115200 link is the one case where the wire is slow enough to notice, which is why it is a fallback rather than a default.

What does change the feel is not the box: it is the smoothing and the FOV you set in the aim settings.

06Questions

Is a KMBox Net better than a MAKCU?
Neither aims better - the aim is computed on the second PC in both cases. The KMBox Net takes its orders over the network, a MAKCU over a USB serial cable; pick the one that fits how your two machines are placed.
Do I need a cable between the KMBox Net and the second PC?
No. That is its point: the second PC reaches it over the network. The only cables are your mouse into the box and the box into the game PC.
Which one is lowest latency?
In practice none of them is the limit: a UDP packet on a local network and a 4 Mbaud serial write are both well under a frame. Only a 115200 serial link is slow enough to matter.
Can I use a device I already own?
If it speaks the KMBox Net protocol, or if it is a serial box like a MAKCU, a Ferrum or a KMBox B, the Device settings cover it.
Do I need an aim device at all?
Only for the aim features. ESP, loot, radar and the rest need nothing but the DMA card and the second PC.

Read next

Every elusive product runs on this setup, from one account and one loader.

See the products
KMBox Net vs MAKCU vs Ferrum: Which Aim Device, elusive