Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.37f1
2022.3.23f1
2023.2.17f1
6000.0.0b14
Issue ID
UUM-68283
Regression
No
Physics and Raycast have different behavior when enum is exposed in the Editor
How to reproduce:
1. Open the user-attached project “enum-bug”
2. Open the “Demo_ThrowObject3D_Desktop_Mobile_Static_Flick” scene
3. Select “ThrowingPoolControl” GameObject in the Hierarchy
4. In the Inspector, under the “Throw Control (Script)” Component “Modes” field change “Mode At Awake For Desktop” to “Click Or Tap”
5. Enter the Play Mode, hold the Left Mouse Button to throw the balls and observe the results
6. Change “Mode At Awake For Desktop” to “Flick” and open the “ThrowControl.cs” Asset
7. Change the line 67 to private “ThrowingMode modeAtAwake = ThrowingMode.ClickOrTap;”
8. Enter the Play Mode, hold the Left Mouse Button to throw the balls and observe the results
Expected results: In both cases, the balls can be thrown and they collide with the walls
Actual result: In the first case the balls are not colliding and in the second case the balls can’t be thrown
Reproducible with: 2021.3.37f1, 2022.3.23f1, 2023.2.17f1, 6000.0.0b14
Reproducible on: Windows 11 Pro, macOS 14.3.1 (user’s)
Not reproducible on: No other environment tested
Note: Also reproducible in Player
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.