Two machines, one desk: physical layout
The USB cable between the two machines is the shortest leash on the desk. The layout has to be designed outward from it.
By Lethal Hardware Desk
Almost every layout problem in a two-machine build starts the same way. You design the desk around the monitors, then discover where the USB cable has to go. It works the other way round. The card lives in the game PC and talks to the second PC over one link. That link wants to be short, direct and undisturbed. That single constraint decides more about the desk than any monitor arm does.
Start from the cable, not the screens
The link runs from the card's data port to a rear motherboard USB 3 port. Nothing goes in between. No hub, no dock, no extension, no front-panel header. Every one of those is a documented cause of a device that enumerates and then drops out mid-read. Every one is also a thing you will fail to suspect for weeks. So the second PC has to live within a short cable of the back of the game PC. That, rather than anything aesthetic, fixes its position on the desk.
- The DMA cable is the shortest run on the desk, with slack only at the card end
- That slack is not optional: tension on a USB-C socket is a slow way to kill a board
- Route it through a case cutout that does not pinch it, and do not bundle it tightly with power cables
- The second PC goes where the cable reaches comfortably, not where it looks best
- Leave the rear ports of both machines reachable without moving furniture
Do not route the card's data link through a KVM, a hub, a monitor's downstream ports or a dock. That holds even for a device that works faultlessly for everything else you own. When the read drops out three weeks later, you will not connect it to the switch you installed today. You will spend the evening reinstalling drivers instead.
Giving the second PC a screen
The second PC's screen does two unrelated jobs. Buying for the wrong one is the usual mistake. Administration means drivers, a read test, an error message. It happens rarely, and any screen does it, including a borrowed one for an afternoon. Reading a radar during a match is about glance distance and position, not panel quality. Decide which jobs you need before spending anything. For administration alone, the honest answer is often no monitor at all.
| Option | Good for | Costs you |
|---|---|---|
| Small portable panel beside the monitor | In-match reading with no switching, at a glance distance you can tune by moving the stand | Desk space and one more cable, on a panel you will use for nothing else |
| A spare monitor you already own | Free if it exists, and large enough for administration and a map at once | Real desk space, and it is usually too large for a comfortable glance |
| KVM switch | Setup and administration on a tidy desk, with a full-size view of either machine | You see one machine at a time, which makes it useless during a match |
| Phone or tablet on the local network | A map you can position anywhere, with no new hardware to buy | Needs a network path and software that serves a web view, and adds a little latency |
| Headless over remote desktop | Zero desk footprint for a machine you rarely touch | No in-match view, and no way in on the day the network is the thing that broke |
These combine. The common mature setup is two rows at once: headless or KVM for administration, plus a panel or a phone for in-match reading.
Where a KVM helps and where it does not
A KVM shares one monitor, keyboard and mouse between both machines. A button switches between them. For the hours you spend building the thing it is genuinely good. You get a full-size view of whichever machine you are working on, and no second keyboard on the desk. During a match it does nothing, because the entire point is seeing both at once. It is also one more device in the video path. That means one more suspect on the day a screen stays black. Buy it for the setup phase. Keep a direct cable for the day you need to bypass it.
The ergonomics people get wrong
- A radar panel placed too high or too far away — it belongs low and close, just under the main monitor's bottom edge, angled up
- The second PC on the floor under the desk, where the USB cable is stretched taut and the intake eats carpet dust
- A mini PC pushed against a wall or wedged behind a monitor stand with no clearance for its own exhaust
- A second keyboard and mouse occupying prime desk space for a machine you touch twice a week
- Both machines and both monitors on one overloaded extension lead, behind the desk, unreachable
- The second PC's exhaust pointed straight into the game PC's intake
The first item accounts for most complaints about a radar being hard to use. A map that requires moving your head is a map you stop reading under pressure. Move the same panel six inches lower and closer and it stops being a problem. The rest are variations on one mistake. They treat the second machine as furniture rather than as a computer. It needs air, power, and a cable you can reach.
Heat, power and the boring parts
Two machines in one footprint means two heat sources and two power draws in a space designed for one. Give the second PC its own intake clearance. Keep its exhaust away from the game PC. Put both on power you can switch without crawling. Plan for a full shutdown of the game PC as well. That is the standard fix for a hung card, and it happens more often than newcomers expect. So the power button should be reachable without dismantling the desk. So should any cable you might need to reseat.
Once four or five USB cables leave the back of the game PC, they are indistinguishable. The one that matters is the one you move between the flashing and data ports. A strip of tape at each end turns a ten-minute crawl into a five-second job. Every single time.
Read next
Questions about this? Ask on Discord
All posts