Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.2.1
Issue ID
N4EBUG-120
Regression
No
Different hashes between server and client are created when connecting to a server instance
How to reproduce:
1. Open the attached "NetCodeErrorRepro" project
2. Open the “Assets/Scenes/Bootstrap.unity“ Scene
3. Enter Play Mode and press the “Server“ button
4. Install “serve” by typing “npm install -g serve“ in Mac Terminal
5. Type “cd {where the project is located}/BasicNetcodeWebGame/Builds/Client“ and press “Enter”
6. Type “serve -s -l 3000 --ssl-cert server.crt --ssl-key server.key“ and press “Enter“
7. Open this link “[https://localhost:3000|https://localhost:3000“]”
8. Press the “Client“ button in the Web Player
9. Open the Inspect Console by right-clicking and selecting the “Console” tab
Expected result: A blue circle player appears in the Web Player
Actual result: Errors appear in the Inspector Console
Reproducible with: 1.2.0 (6000.0.5f1), 1.2.1 (2022.3.31f1, 6000.0.5f1)
Couldn’t test with: 1.1.0-pre.3 (6000.0.5f1) (Errors in the Console)
Reproducible on: macOS 14.5 Sonoma (Intel), Windows 11 (reported by user)
Not reproducible on: No other environment tested
Notes:
- Universal Package Manager needs to be installed on the system for the mentioned commands to work
- Might need to type “sudo “ before the commands and enter the system password for the commands to work if permission is denied
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
- Editor Launch Screen will close when Enter is pressed on it
- ObjectPool's pool is destroyed when entering Play Mode without reloading Domain
- [Android] Permission window is not shown when using a Build App Bundle (Google Play) with Minify set to Release
- NullReferenceException errors appear in the Console and Inspector window turns black when dragging .cs and .uxml files to another directory
- Crash when reimporting fbx asset used as tree by specific Terrain component
Resolution Note:
There are no fixes planned for this Bug