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
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
- Crash after the “State comes from an incompatible keyword space“ log when opening the project
- [Android] GameObject are not rendered at all or rendered black when in the custom shader “multi_compile_instancing“ is enabled with two “float4” instance properties are present on older devices
Add comment