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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment