Velum Studio
All guides

Guides › Velum Gauges

When Velum Gauges hears nothing

Nothing heard, Windows Firewall, ports, a console's new address, and SimHub alongside Velum.

When the gauge stays dimmed, the Inspector usually says why, in plain words, and the setup window's Status line says what Velum is hearing. Start there, then look below.

Nothing heard

Work down this list:

  1. Are you driving or flying? Games only send while you're actually playing. Menus, pauses, replays and loading screens are quiet. The Inspector says Nothing on 5310 in 10 s when nothing's come in.
  2. Is the game's data output on? Check the setting in your game's setup guide. Some games turn it off again after an update.
  3. The address. It must be the address of the computer running Velum, exactly as the setup window shows it. From a console it's never 127.0.0.1.
  4. The port. The game's port and Velum's Listen on port must match. Not sure what the game is set to? Press Find it for me and drive for 30 seconds: Velum says where it hears your game.
  5. The firewall, on Windows, for a console or another PC. See below.
  6. The network. The console or gaming PC and the computer running Velum must be on the same home network. A guest Wi-Fi network usually keeps devices apart.

If the Status line says packets weren't from a game Velum Gauges knows yet, something is reaching Velum, but it isn't a game Velum Gauges can read yet, or the game is set to a format Velum doesn't read (for Forza Motorsport, pick Dash).

Windows Firewall

On Windows, games on a console or another PC are kept out until you let them in. Games on the same PC don't need this.

  1. Press Let Velum Gauges hear games on your home network, under Game connection or in the setup window.
  2. Windows asks for permission. Say yes. (If you don't see it, it may be behind the setup window.)
  3. The Firewall line in the setup window says when games can get through.

It adds one permission: Velum's plugin helper, only the ports Velum Gauges listens on, only on home (Private) networks. If you changed Listen on port since, the Firewall line says the permission is for other ports: press the button again to update it.

  • "Blocking Velum Gauges" means Windows made a block rule when its own "allow access" popup was closed. The same button clears that block.
  • "This PC's network is set to Public" means Windows keeps games out on this network whatever the permission says. Open Windows Settings › Network & internet › your network, and set Network profile type to Private.
  • To take it away, press Remove the home-network permission in the setup window.

Ports 5200 to 5300

Forza Horizon 6 uses ports 5200 to 5300 itself, so it won't send to any of them. Velum's usual port, 5310, is just outside that range. If you've set Listen on port inside it, the setup window warns you; set it back to 5310 and type the same in the game.

Two apps can't listen on the same port on one computer. If the Status line says Couldn't listen on a port, another app (often SimHub or a dashboard app) already has it. Pick a different port in Velum and in the game, or let Velum pass the numbers on to the other app (below).

My Xbox got a new address

Consoles can get a new address on your network after a restart. When that happens, Velum notices the same game coming from a new address and asks, for example, Is this Kloe's Xbox? under Recent senders. Press Yes, it's the same one, and the gauge follows it, name and all. Velum never moves a driver without asking.

To stop it happening, give the console a fixed address in your router's settings. Routers call this a DHCP reservation or a static lease. Your router's own help explains where to find it.

Using it alongside SimHub

Most games send to only one place, so SimHub and Velum can't both hear the game directly. Put Velum first and let it pass everything on:

  1. Point the game at Velum (port 5310), as in its setup guide.
  2. In SimHub, set the game to listen on a different port from Velum, for example 5300.
  3. In Velum, under Relay to, add 127.0.0.1:5300 (SimHub on this PC), or the address and port of another PC.

Velum sends SimHub an exact copy of every packet, so SimHub works just as before. The same goes for a motion rig, a wheel's software or a dashboard on a tablet: up to eight places. With Driver on Automatic every driver's packets are passed on; with a driver picked, only theirs. The Status line counts what's been relayed, and says so if a relay fails.

You can also do it the other way round, with SimHub first and set to forward packets on to Velum's port. That works for one player, but everything then arrives from SimHub, so Velum can't tell two consoles apart. For two players, send to Velum first.

Other things

The numbers freeze or the gauge dims mid-raceThe game stopped sending: a pause, a replay, or a rewind. It picks up again as soon as you're driving.
The wrong player's numbersSet the gauge's Driver to that player instead of Automatic, and name each one so they're easy to tell apart.
X-Plane isn't foundType its address under X-Plane's address and press Ask this X-Plane. See X-Plane.
Microsoft Flight Simulator isn't foundVelum has to run on the sim's own PC, and needs SimConnect.dll. See Microsoft Flight Simulator.
The truck game doesn't show the SDK messageThe helper isn't in the game's plugins folder, or the game was running while it was copied. Close the game and press Install the truck helper again. See the trucks guide.

Still stuck?

Post in the Velum Studio Testers Discord with your game, where it runs, and a screenshot of the setup window. If the numbers look wrong rather than missing, press Record packets under Game connection, drive for a minute, press Stop recording, and attach the file it saved (it goes in the Recordings folder). It holds only what your game sent, and it lets us see exactly what you saw.

New and still growing: tell us what you find in the Velum Studio Testers Discord.