BeamNG.drive plugin 2.0.3.0

You might check to make sure that you have motion in SimHub turned off, that might be causing the conflict.
EDIT: Look under Add/Remove Features bottom left of the main menu.

@Historiker thanks for the reply, thats currently set to disabled.
I would think that this set up in the screen shot would be all thats needed, forward to a port from SimTools, and listen on that port in SimHub

I also noticed that in the SimHub instructions for this game it mentioned 63392 for the port to set inside of beamNg, so i just tried setting that port as the SimTools relay and then setting it as the UDP port in SimHub but I am still not getting any guage data in SimHub

Ok! ChatGPT for the win! I fed it the SimTools instruction PDF and described my issue and now its solved.

ChatGpt:

Short version: for BeamNG you don’t actually want to use the SimTools UDP Relay for SimHub – that’s why SimHub is seeing nothing.

Let me walk through what’s really happening and then give you a working setup.

What’s going wrong right now
BeamNG has two separate UDP protocols:

• MotionSim – meant for motion platforms (pos, velocity, accel, roll/pitch/yaw, etc.)BeamNG Documentation
  
  
• OutGauge – meant for dashboards (speed, RPM, throttle, etc.)BeamNG Documentation
  

SimTools’ BeamNG plugin uses the MotionSim data (on its own port, usually 4123) for motion. When you enable UDP Relay in SimTools, it forwards those same MotionSim packets to another port.

SimHub’s BeamNG support, on the other hand, expects OutGauge (or its own SH Telemetry mod format) – not MotionSim. So:

SimTools is happily relaying MotionSim → SimHub
SimHub is listening… but to it, those packets are the wrong format, so it ignores them
Result: no gauges, no shakers.

So your ports are probably fine; it’s the type of data that’s mismatched.

The better approach for BeamNG: no UDP relay at all
BeamNG can run multiple protocols at once on different ports.BeamNG Documentation
So the clean solution is:

• SimTools uses MotionSim on one port (for motion)
  
  
• SimHub uses OutGauge on another port (for dash/shakers)
  

No SimTools UDP Relay involved.

1. BeamNG settings
In BeamNG:

1. Go to Options → Other → Protocols (or similar depending on version).
   
   
2. Enable both:
   
   • OutGauge UDP protocol → this will feed SimHub
     
     
   • MotionSim UDP protocol → this will feed SimToolsBeamNG Documentation
     
3. Set IPs and ports something like:
   

• OutGauge (for SimHub):
  
  • IP: 127.0.0.1
    
    
  • Port: 63392 (this is commonly used by SimHub for BeamNG; if yours is different, just match whatever SimHub is set to).Sim Racing Studio
    
• MotionSim (for SimTools):
  
  • IP: 127.0.0.1
    
    
  • Port: 4123 (SimTools’ default motion port – confirm in the SimTools plugin docs / settings).XSimulator Motion Simulator
    

Key point: OutGauge and MotionSim must be on different ports.
You don’t need to touch SimTools’ UDP Relay for this game.

I’m all good now, ChatGPT helped me figure out that I just didn’t need to set the port forwarding on SIM tools. And to use the out gauge port directly from what set in beam