Search Issue Tracker
Won't Fix
Votes
0
Found in
5.4.0f3
Issue ID
841322
Regression
Yes
CreateMatchRequest, CreateMatchResponse, ListMatchResponse and JoinMatchResponse is no longer accessible
Reproduction steps:
1. Create new project
2. Create C# script
3. Include UnityEngine.Networking.Match library
4. Try create new instances of CreateMatchRequest, CreateMatchResponse, ListMatchResponse or JoinMatchResponse in Start method
Expected result: Instances can be created (No errors)
Actual result: Classes cannot be accessed due to its protecion level
This used to work before 5.4 release. Now the match making approach is changed and users cannot use the old approach.
Reproduced on: Unity 5.4.1f1, 5.4.2f1
Not reproduced on: Unity 5.25f1, 5.3.3f1
The documentation should also be updated to use new approach:
https://docs.unity3d.com/ScriptReference/Networking.Match.NetworkMatch.html
The example in this documentation currently does not compile
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Add comment