i have tested running the bridge from native ROS-Noetic in windows machine, and the issue still remain

`

C:\opt\ros\noetic\catkin_ws\src\beamng-ros-integration\beamng_control\launch>roslaunch example.launch
... logging to C:\Users\ideas.ros\log\e14b845c-5aac-11ec-9345-00155da39b36\roslaunch-DESKTOP-HKDK1FO-4692.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://127.0.0.1:56417/

SUMMARY

PARAMETERS

• /beamng/host: 192.168.0.113
• /beamng/port: 64255
• /rosdistro: noetic
• /rosversion: 1.15.9

NODES
/
beamng_control (beamng_control/bridge.py)

ROS_MASTER_URI=http://127.0.0.1:11311
process[beamng_control-1]: started with pid [1764]
2021-12-12 02:14:16,425 |INFO |beamngpy |Started BeamNGpy logging.
2021-12-12 02:14:16,427 |WARNING |py.warnings |C:\opt\ros\noetic\x64\lib\site-packages\beamngpy\beamng.py:69: DeprecationWarning: The use of beamng.setup_logging is deprecated and will be removed in future versions. Use beamngcommon.set_up_simple_logging or beamngcommon.config_logging instead.
create_warning(warn_msg, DeprecationWarning)

2021-12-12 02:14:16,427 |WARNING |py.warnings |C:\opt\ros\noetic\x64\lib\site-packages\beamngpy\beamng.py:69: DeprecationWarning: The use of beamng.setup_logging is deprecated and will be removed in future versions. Use beamngcommon.set_up_simple_logging or beamngcommon.config_logging instead.
create_warning(warn_msg, DeprecationWarning)

2021-12-12 02:14:16,431 |INFO |rosout |cmd args['C:\opt\ros\noetic\catkin_ws\devel\lib\beamng_control\bridge.py', 'C:\opt\ros\noetic\catkin_ws\src\beamng-ros-integration\beamng_control\config\scenarios\simple_scenario.json']
2021-12-12 02:14:16,435 |INFO |beamngpy.BeamNGpy |Opening BeamNGpy instance.
2021-12-12 02:14:16,437 |INFO |beamngpy.BeamNGpy |Connecting to BeamNG.tech at: (192.168.0.113, 64255)
2021-12-12 02:14:16,802 |INFO |rospy.internal |topic[/rosout] adding connection to [/rosout], count 0
←[31m[FATAL] [1639246477.488770]: Could not establish connection, check whether BeamNG.tech is running.
←[0m2021-12-12 02:14:37,488 |CRITICAL |rosout |Could not establish connection, check whether BeamNG.tech is running.
2021-12-12 02:14:37,492 |WARNING |py.warnings |sys:1: ResourceWarning: unclosed <socket.socket fd=1372, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('0.0.0.0', 56451)>

2021-12-12 02:14:37,492 |WARNING |py.warnings |sys:1: ResourceWarning: unclosed <socket.socket fd=1372, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('0.0.0.0', 56451)>

2021-12-12 02:14:37,494 |INFO |rospy.core |signal_shutdown [atexit]
2021-12-12 02:14:37,496 |INFO |rospy.internal |topic[/rosout] removing connection to /rosout
2021-12-12 02:14:37,496 |INFO |rospy.impl.masterslave |atexit
2021-12-12 02:14:37,517 |WARNING |py.warnings |C:\opt\ros\noetic\x64\lib\site-packages\rospy\core.py:598: DeprecationWarning: isAlive() is deprecated, use is_alive() instead
if t.isAlive():

2021-12-12 02:14:37,517 |WARNING |py.warnings |C:\opt\ros\noetic\x64\lib\site-packages\rospy\core.py:598: DeprecationWarning: isAlive() is deprecated, use is_alive() instead
if t.isAlive():

←[31m[beamng_control-1] process has died [pid 1764, exit code 1, cmd python C:\opt\ros\noetic\catkin_ws\devel\lib\beamng_control\bridge.py C:\opt\ros\noetic\catkin_ws\src\beamng-ros-integration\beamng_control\config\scenarios\simple_scenario.json __name:=beamng_control __log:=C:\Users\ideas.ros\log\e14b845c-5aac-11ec-9345-00155da39b36\beamng_control-1.log].
log file: C:\Users\ideas.ros\log\e14b845c-5aac-11ec-9345-00155da39b36\beamng_control-1*.log←[0m
all processes on machine have died, roslaunch will exit
shutting down processing monitor...
... shutting down processing monitor complete
done

`

from beamng-ros-integration.

port number wasn't correct in [beamng-ros-integration/beamng_control/launch/bridge.launch] default value was 64255, while the correct value is 64256

from beamng-ros-integration.