Search Issue Tracker

Not Reproducible

Votes

0

Found in

2021.3.40f1

2022.3.38f1

6000.0.10f1

6000.1.0a7

6000.2.0a1

7000.0.0a1

Issue ID

UUM-75656

Regression

No

The boolean value of one GameObject is logged as False and for the other GameObject the value is logged as True when the GameObjects are identical

-

How to reproduce:
1. Open the “ReproBooleanValue“ project
2. Open the “ReproScene“
3. Deactivate the “SButton“ GameObject and “Beats/S-Beat“ GameObject
4. Enter the Play Mode
5. Press any button on the keyboard or click on the Game view
6. Once the “Beats/A-Beat“ GameObject turns green press the 'A' key on the keyboard
7. Observe the Console window
8. Exit the Play Mode
9. Activate the “SButton“ GameObject and “Beats/S-Beat“ GameObject
10. Deactivate the “AButton“ GameObject and “Beats/A-Beat“ GameObject
11. Repeat the steps 4 through 7 with the “Beats/S-Beat“ GameObject

Expected result: The “canBePressed“ property of “AButton” and “SButton“ is logged as True
Actual result: The “canBePressed“ property of “AButton” is logged as False and for the “SButton“ it is logged as True

Reproducible with: 2021.3.40f1, 2022.3.38f1, 6000.0.10f

Reproducible on: macOS 14.5 (Intel), Windows 10 Pro (22H2)
Not reproducible on: No other environments tested

Notes:
- Even though the same scripts (“Button_Control.cs“) are used for both “SButton“ and “AButton“ (same with “A-Beat“ and “S-Beat“) GameObjects, the behavior differs
- The exposed property “Can Be Pressed“ in the Inspector window (for the “A-Beat“ GameObject) shows that the value is True when logging shows it as False
- The duplicate GameObject of the incorrectly working “AButton“ and “A-Beat“ GameObjects work as expected

  1. Resolution Note:

    Caused by two corrupted objects sharing the same InstanceID, Reimport resolves the issue.

Add comment

Log in to post comment