Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
6000.0.58f2
6000.2.11f1
6000.3.0a5
6000.4.0a4
Issue ID
UUM-126846
Regression
No
[macOS] Keyword incompatibility errors are shown when opening the XR Environment window or entering Play Mode
How to reproduce:
1. Open the “ReproProject.zip“ project
2. Open the “SampleScene“
3. Open the “Window > XR > AR Foundation > XR Environment“
4. Observe the Console window
5. Clear the Console window
6. Enter the Play Mode
7. Observe the Console window
8. Clear the Console window
9. Exit the Play Mode
Expected result: No errors
Actual result: Errors “State comes from an incompatible keyword space“ and “Keyword state size mismatch ([] vs [] keywords)“ are shown
Reproducible with: 6.0.6 (6000.0.62f1), 6.3.0 (6000.0.62f1, 6000.2.11f1), 6.4.0-pre.1 (6000.0.62f1, 6000.2.11f1, 6000.3.0b9, 6000.4.0a4)
Reproducible environment: macOS 15.7 (M4 Max), macOS 26.0.1 (M2)
Not reproducible environment: Windows 11 Pro (22H2)
Note: The reproduction with steps 3 only happens one time after the project is reopened (Reimport is performed), and the reproduction with steps 6 happens consistently
Errors:
State comes from an incompatible keyword space
Expected: From shader: 'Simulation/Standard Lit' Keyword count: [] Keywords:
Keyword state size mismatch ([] vs [] keywords)
KeywordSpace: From shader: 'Simulation/Standard Lit' Keyword count: [] Keywords:
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