You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 18, 2022. It is now read-only.
We are accepting issues and we want your feedback.
Description
Specifying a layer as write access for an entity's components makes it not working.
Expected behaviour
Since the "UnityGameLogic" worker is responsible for the "game_logic" layer, components with "game_logic" write access should behave the same as before.
Current behaviour
The inspector shows no "Authoritative Workers" on the entities. The SendCreatePlayerRequestSystem sporadically activates with a chunk (about once per second). The HandleCreatePlayerRequestSystem never activates. Other entities such as the Spinners are never spawned so this might also affect the GameObjectCreation module.
Possible solution
Steps to reproduce
Modify "default_launch.json" and "spatialos.UnityGameLogic.worker.json" with the contents of the attached files.
Modify "SnapshotGererator.cs" so that each "WorkerUtils.UnityGameLogic" write access is replaced with "game_logic" layer (modified file attached for convenience).
Add "game_logic" string to the list "AllWorkerAttributes" in "WorkerUtils.cs".
Generate the snapshot.
Launch locally.
Go in Sample scene and Play.
Environment
Use the new layers to create entities instead of the old approach with specific workers.
Running basic diagnostics suite
Network Access Checks
Google Storage APIs Reachable: PASSED
Spatial Website Reachable: PASSED
Spatial Auth Server Reachable: PASSED
Spatial Maven Reachable: PASSED
Spatial API Reachable: PASSED
Spatial Secure Customer Proxy Reachable: PASSED
Can Bind to Local Port: PASSED
Spatial Proxy Reachable: PASSED
Spatial Website TLS and GRPCTLS Ports Reachable: PASSED
Spatial Auth TLS and GRPCTLS Ports Reachable: PASSED
Spatial Maven TLS and GRPCTLS Ports Reachable: PASSED
Spatial API TLS and GRPCTLS Ports Reachable: PASSED
Spatial Deployments Reachable: PASSED
Spatial Logs Reachable: PASSED
Spatial Monitoring Proxy Reachable: PASSED
Spatial Locator Reachable: PASSED
Maven Central Repo Reachable: PASSED
Sonatype OSS Repo Reachable: PASSED
All checks successful
Windows 10 64 bit, Unity 2018.3.0b10
The text was updated successfully, but these errors were encountered:
* Additions/changes to Get Started
Changed the wording and layout of some pages to add a little more clarity.
Added info about a few potential installation slip ups that might occur.
* Errant commas
* Update build-unreal-fork.md
* Update build-unreal-fork.md
* Update SpatialGDK/Documentation/content/get-started/build-unreal-fork.md
Co-Authored-By: NotRobSheridan <rob@notrobsheridan.co.uk>
* Purged some ings
* Update SpatialGDK/Documentation/content/get-started/build-unreal-fork.md
Co-Authored-By: NotRobSheridan <rob@notrobsheridan.co.uk>
* Update build-unreal-fork.md
* Update build-unreal-fork.md
* Update build-unreal-fork.md
* Update build-unreal-fork.md
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
SnapshotGenerator.zip
default_launch.zip
spatialos.UnityGameLogic.worker.zip
We are accepting issues and we want your feedback.
Description
Specifying a layer as write access for an entity's components makes it not working.
Expected behaviour
Since the "UnityGameLogic" worker is responsible for the "game_logic" layer, components with "game_logic" write access should behave the same as before.
Current behaviour
The inspector shows no "Authoritative Workers" on the entities. The SendCreatePlayerRequestSystem sporadically activates with a chunk (about once per second). The HandleCreatePlayerRequestSystem never activates. Other entities such as the Spinners are never spawned so this might also affect the GameObjectCreation module.
Possible solution
Steps to reproduce
Environment
Use the new layers to create entities instead of the old approach with specific workers.
Running basic diagnostics suite
Network Access Checks
Google Storage APIs Reachable: PASSED
Spatial Website Reachable: PASSED
Spatial Auth Server Reachable: PASSED
Spatial Maven Reachable: PASSED
Spatial API Reachable: PASSED
Spatial Secure Customer Proxy Reachable: PASSED
Can Bind to Local Port: PASSED
Spatial Proxy Reachable: PASSED
Spatial Website TLS and GRPCTLS Ports Reachable: PASSED
Spatial Auth TLS and GRPCTLS Ports Reachable: PASSED
Spatial Maven TLS and GRPCTLS Ports Reachable: PASSED
Spatial API TLS and GRPCTLS Ports Reachable: PASSED
Spatial Deployments Reachable: PASSED
Spatial Logs Reachable: PASSED
Spatial Monitoring Proxy Reachable: PASSED
Spatial Locator Reachable: PASSED
Maven Central Repo Reachable: PASSED
Sonatype OSS Repo Reachable: PASSED
All checks successful
Windows 10 64 bit, Unity 2018.3.0b10
The text was updated successfully, but these errors were encountered: