Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.2.0f3
Issue ID
984209
Regression
No
The origin and direction of the Ray get swapped on the client side when the Ray is passed to ClientRpc method
To reproduce:
1. Open the project, attached by the tester (RpcClientRay.zip)
2. Build the project for PC
3. Launch the build and enter Play mode in the Editor
4. In the build connect as host and as client in the Editor
5. In the build, press Space
6. Observe the console messages in the Editor
7. Inspect the Test.cs script
Expected: Ray.origin and Ray.destination are not swapped when the ray is passed to ClientRpc method
Reproduced in 5.6.5p2, 2017.1.3p1, 2017.2.0f3, 2017.3.1p1, 2018.1.0b8, 2018.2.0a1
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
- [VFX] Custom HLSL with 'int' parameter, without the 'in/out/inout' access modifier is not supported
- [Windows] Lens Flare doesn't work in the Lens Flare Showroom URP Sample Scene
- Crash on ujob_execute_job while using OverlapBoxCommand when collisions are more than maxHits
- The validity of the multiple handles can behave differently based on the load/release operations order, when multiple Addressables.LoadAssetAsync and Addressables.Release are used to load and release the same Addressable Asset
- Dynamic text is rendered in the background when it is inside the <font> tag
Resolution Note:
Mass closure of UNET Bugs.
As UNet is Deprecated we are moving to low maintenance mode, where critical issues can get fixes.
Closing this bug as part of cleaning-up the Bug List.
If you feel this bug is really a road-blocker, you can reopen the bug and we will work this one.