The software runs on a second PC. The game PC only has the DMA card in a PCIe slot. Nothing from XFX is injected into the game.
You do not pick a firmware mode in the menu. The files sitting next to the exe decide the link.
Leave vmm.dll, leechcore.dll and FTD3XX.dll where the loader put them. The overlay opens the card as fpga and keeps the first handle that answers. It does not reopen the card to flip algorithms, which is what drops a HITM firmware.
MITM builds ship their own leechcore.dll (and sometimes vmm.dll and FTD3XX.dll). Put that set in a folder named mitm next to the exe. The overlay loads that copy automatically. The loader does not replace files inside mitm, and it also leaves a leechcore.dll you already replaced in the main folder alone.
Put rdma.txt or rdma.ini next to the exe. One IP per line, or ip=192.168.1.10. A full device string such as RAWUDP://ip=192.168.1.10 is also accepted. If that file exists, the overlay tries the RDMA link before the USB FPGA. No settings toggle.
On startup the overlay looks for KMBox Net on the LAN (the usual 192.168.2.188 and the .188 address of your own subnet, ports 16824 and 16896). Serial boards are classified by USB id: CH340 is KMBox B, CH343 is MAKCU, CP210x and Espressif bridges are Ferrum. Each port is asked km.version(). MAKCU then steps up to 4 Mbaud. Ferrum steps up to 3 Mbaud. A controller passed through the MAKCU controller firmware still uses that same command channel, so aim, magnet and trigger all send through it.
Leave Auto-Connect on. The overlay keeps trying for about twenty minutes. A stale KMBox Net address no longer blocks the COM port. If two serial devices are plugged in, the one that answers the km protocol wins. Close any other tool that already has the COM port open.
KMBox Net and KMBox B packets are small. MAKCU and Ferrum take a full move. Smoothness is 1 (fast) through 100 (slow) on all of them. Per-weapon profiles override the global FOV and smooth when that weapon is in hand.
Keys look like XFX-XXXXXX-XXXXXX-XXXXXX-XXXXXX. Letter case does not matter. If the site says the key is already used, an admin can move it onto your account.
That call is HTTPS to xfx.systems. A VPN, DNS filter or firewall is the usual cause. Try another network. The loader will not start the product until that check returns.
Open a ticket in Discord. An admin clears the lock. This is what happens after a new motherboard, a new Windows install, or moving the loader to a different machine.
The DMA link did not attach. Confirm the card enumerates, the game is in a match rather than a menu, and you fully quit the overlay including the tray icon before launching a new build. A MITM leechcore.dll left in the main folder is kept. A set inside mitm\ is preferred over the stock DLLs.
The actor pass is one scatter, not a read per player. Raising the ESP refresh floor in Settings hands time back to the card. The web radar does not add reads. It reuses the snapshot the ESP already has.