4.3 Unity, Unreal, ROS, C++, and Python Integration Workflow
4.3 Integration Process for Unity, Unreal, ROS, C++, and Python
The following is a general project process. It does not mean that the same set of plugins or interfaces is provided by default for every technology stack.
2. Establish the Minimum Data PathOne device set, one action result
3. Extend Business LogicMapping, interactions, multiple devices
4. Complete AcceptanceArchive versions and evidence
Items to Confirm for Each Technology
Unity
Editor and runtime versions, target platform, data-driven objects, and build output.
Unreal Engine
Engine version, Blueprint or C++ requirements, target platform, and plugin delivery format.
ROS
ROS version, operating system, message integration target, and runtime topology.
C++
Compiler, architecture, build system, runtime libraries, and minimum program objective.
Python
Interpreter version, environment management method, dependencies, and method of consuming data.
Avoid Mixing Versions
Do not use an SDK, example, receiver, or firmware from another project in the current project. Before upgrading any component, save a version baseline that can be rolled back.
