Search Issue Tracker
Fixed in 1.0.4
Votes
16
Found in [Package]
1.0.2
Issue ID
1146415
Regression
No
NetworkTransformChild component from Multiplayer HLAPI package cannot be added to GameObjects due to a typo in its name
How to reproduce:
1. Create a new Unity project
2. Download the Multiplayer HLAPI package
3. In the Project window navigate to Packages > Multiplayer HLAPI > Runtime
4. Look for the NetworkTransformChild.cs script
Expected result: NetworkTransformChild.cs is named correctly
Actual result: NetworkTransformChild.cs has a typo and is instead named NetworkTranformChild.cs
Reproducible with Unity versions: 2019.1.0f2, 2019.2.0a12
Could not test with Unity versions: 2017.4.25f1, 2018.3.13f1(Multiplayer HLAPI package not available)
Tested with package versions:
preview - 0.2.4, 1.0.2
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash when total memory consumption is over 2GB
- Red dots are rendered when copying texture with ASTC format and CompressGpu
- [Linux] "Trying to load color backbuffer into a complex RenderPass setup" error is thrown after entering Play mode in AR Mobile template project
- [Android] Neither of the callbacks are called when several videos with VideoPlayer are spawned on the target on the Google Pixel devices
- Texture2D memory allocation size is significantly increased when running on iOS device
TimCoster
Jun 11, 2019 09:33
Another problem this typo causes is that when I change the names to be correct, Unity collab doesn't allow me to publish changes to the project because the networktransformchild files can't be copied.
TimCoster
Jun 11, 2019 09:27
Could this please be fixed?? I don't understand why it has to take several weeks to fix a one character typo. This is a very annoying problem because I have to look for the NetworkTransformChild.cs and .meta files in finder and change the names of the files every time I have to relaunch Unity, which is about a hundred times a day because, well...steamVR macOS beta and openVR :( .. Thanks in advance