Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0b2
Issue ID
905286
Regression
Yes
Regression. One of spawnable objects is destroyed on the Host in Editor on 2017.1.0b2
Regression - started to appear in 2017.1.0b2, but everything is good in 2017.1.0b1
When open "Tanks!!! Reference Project" project from A$ in 2017.1.0b2 and connect through MatchMaker - Editor part doesn't work
How we can reproduce it
1 Create new project
2 Go to AssetStore and find "Tanks!!! Reference Project" (https://www.assetstore.unity3d.com/en/#!/content/80165)
3 Import this package to your project
or
just open attached project
4 Start host in Editor
5 Build and Run Standalone and connect it as Client
--- please see attached video (TanksRefProjectProblem.swf) with the explanation ---
Actual result: second tank (spawnable object) doesn't appear in the Editor instance (Host), but everything works fine in Standalone (Client). Somehow "OnNetwirkDestroy" is called on second tank object...
!!! When start Host in Standalone and Client in Editor - everything works fine !!!
Expected results: there should be 2 tanks (spawnable object)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment