Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.0b8
Issue ID
1051692
Regression
No
Write operation in IJobComponentSystem [ReadOnly] variable doesn't create a warning message
How to reproduce:
1. Open user-submitted project (unity-job-system-execution-order-issue.zip)
2. Open "SampleScene.unity" scene
3. Play the scene with "SuccessSystemsOrder_Spawner" game object active (Observe cube behavior)
4. Play the scene with "IgnoreSystemsOrder_Spawner" game object active (Observe cube behavior)
5. Inspect "ModifySpeedSystem.cs" file code at line 30.
6. Change "[ReadOnly] ref MoveSpeed moveSpeed" to "[WriteOnly] ref MoveSpeed moveSpeed"
7. Repeat steps 3, 4
Expected result: Generated cubes don't move
Actual result: Generated cubes move due to system execution order being incorrect due to incorrect variable access flags
Reproducible with: Entities 0.0.12-preview 8
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
Add comment