-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ROS2] Multiplayer support #328
Draft
lgleim
wants to merge
5
commits into
o3de:development
Choose a base branch
from
lgleim:multiplayer
base: development
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lgleim
added
kind/feature
Categorizes issue or PR as related to a new feature.
sig/network
Categorizes an issue or PR as relevant to SIG Network.
sig/simulation
Categorizes an issue or PR as relevant to SIG Simulation
status/active
Indicates that an issue or PR is actively being worked on by a contributor.
feature/robotics
This item is related to robotics.
labels
May 12, 2023
Added a new function "IsAutonomousOrNonMultiplayer" to the "ROS2GemUtilities" to help components determine if they are attached to an entity that is Networked. This is preliminary work to allow components to be activated selectively in the future, avoiding duplicated work for the ROS2 multiplayer architecture. Signed-off-by: Lars Gleim <lars.gleim@huawei.com>
Adapt ROS2SystemComponent such that each O3DE instance has a distinct ROS2 node name by appending a pseudorandom suffix. Signed-off-by: Lars Gleim <lars.gleim@huawei.com>
Refactored ROS2GemUtilities to avoid compilation issues with the ROS2.Static target and moved the CreateComponent function to the RobotImporterUtils Signed-off-by: Lars Gleim <lars.gleim@huawei.com>
Signed-off-by: Lars Gleim <lars.gleim@huawei.com>
Signed-off-by: Lars Gleim <lars.gleim@huawei.com>
@lgleim was there any further work done on this? Do you have a preferred course of action? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
feature/robotics
This item is related to robotics.
kind/feature
Categorizes issue or PR as related to a new feature.
sig/network
Categorizes an issue or PR as relevant to SIG Network.
sig/simulation
Categorizes an issue or PR as relevant to SIG Simulation
status/active
Indicates that an issue or PR is actively being worked on by a contributor.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Add support for multiplayer (client/server) simulation to the ROS2 Gem, based on a (Gazebo-inspired) "fat-client" architecture, using an O3DE server for state synchronization among clients.
What is the relevance of this feature?
There are an increasing number of use cases for simulating fleets of robots.
One area of application is in the context of warehouse simulation (cf. the Ros2FleetRobotTemplate) where many AMRs need to be simulated in the same environment.
While O3DE is already capable of simulating the physics of many robots (100+) on a single machine, there are clear limits to single-node scalability. This work should raise that ceiling and explore the scalability of an architecture with centralized state synchronization.
Feature design description
To evaluate the feasibility and scalability properties of multi-robot simulation in O3DE using a traditional Client-Server architecture, support for the O3DE Multiplayer Gem should be added to the ROS2 Gem.
Developers will then be able to simulate different robots on different machines, while the simulation state will be synchronized through a central game server. This approach is analogous to traditional multiplayer gaming.
Loosely inspired by the architecture of Gazebo Ignition, which employs a central "primary" for synchronizing the state of the simulation, we plan to make use of the O3DE Multiplayer Gem, creating
Technical design description
What are the advantages of the feature?
What are the disadvantages of the feature?
How will this be implemented or integrated into the O3DE environment?
Are there any alternatives to this feature?
How will users learn this feature?