Skip to content
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

City minimap details replicating incorrectly on clients #66

Open
AndyTechGuy opened this issue Jul 31, 2020 · 1 comment
Open

City minimap details replicating incorrectly on clients #66

AndyTechGuy opened this issue Jul 31, 2020 · 1 comment
Labels
Type: Bug Issues reporting and PRs fixing problems

Comments

@AndyTechGuy
Copy link
Contributor

When using DynamicCities in multiplayer, there are key differences in the minimap displays between the host and a client player:

image image
Left: Minimap of the hosting player
Right: Minimap of a client player with the same position & zoom

Normally in singleplayer, the two parts of the city minimap (the district overlay and the city centre indicator) load in when the player first enters the area of the city. However when a client enters the city, this console warning message appears:

No SettlementCache found! Unable to create district overlay

This console log originates from this line in MinimapOverlaySystem. The information that places the overlays on the minimap comes from a SettlementsCacheComponent attached to a global settlement cache entity, which is created in the SettlementCachingSystem. This console log shows that the settlement cache entity is only present on the server. This entity has a NetworkComponent attached, meaning that it should theoretically be replicating to all clients, but it is not replicating for an unknown reason.

These minimap issues can be fixed in one of two ways:

  1. Figure out why the entity containing the SettlementsCacheComponent isn't replicating to clients; if the entity was replicating then the system would work as intended even on multiplayer.

  2. Use network events instead of components to communicate overlay information. This route should be used only after exhausting the first route.

@AndyTechGuy AndyTechGuy added Type: Bug Issues reporting and PRs fixing problems Status: Needs Discussion Requires help discussing a reported issue or provided PR and removed Status: Needs Discussion Requires help discussing a reported issue or provided PR labels Jul 31, 2020
@skaldarnar
Copy link
Contributor

Thanks for this detailed report - it should give enough clues on where to start investigation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issues reporting and PRs fixing problems
Projects
None yet
Development

No branches or pull requests

2 participants