How nitrosaccharose/qt-unity-socket works
This repository demonstrates a Qt desktop client communicating over a socket with a Unity object simulator. The main workflow is: an operator connects and sends movement keys from Qt; Unity simulates the object and returns its state for display in Qt. The README documents both directions, while the supplied Qt source confirms connection, key sending, and message display. Unity source was not sampled, so internal Unity dispatch and simulation links are omitted. A separate Qt widget implements timer-driven charts.
Main entry points: mainwindow.cpp Main window · SocketClient.cs Socket client · main.cpp Qt entry
Components 7
Qt client
- Qt entry
qt-project/main.cpp - Main window
qt-project/mainwindow.cpp - Timer charts
qt-project/widget.cpp
Unity simulator
- Socket client
unity-project/Assets/SocketClient.cs - Camera controller
unity-project/Assets/CameraController.cs - Simulator scene
unity-project/Assets/Scenes/SampleScene.unity
Other components
- Operator
Connections 5
- Qt entry → Main window: creates window
- Operator → Main window: connects, presses keys
- Main window → Socket client: sends key data
- Socket client → Main window: returns state
- Main window → Operator: displays messages