Search Issue Tracker
Fixed in 5.4.1
Votes
0
Found in
5.4.0b25
Issue ID
813621
Regression
No
-runWithIntegrityLevelLow argument does not affect integrity level
1. Create & build for Windows Standalone a primitive scene with 5.4.0b25
2. Launch build using command line argument -runWithLowIntegritylevel
3. Using Process Explorer application notice integrity level of running build.
Expected result: integrity level should be low
Actual result: integrity level is medium
(Alternatively see user attached photo BadIntegrityLevel.png)
Note: Documentation does not mention anything about such flag, but it is mentioned in 5.4.0b25 release notes(https://unity3d.com/unity/beta/unity5.4.0b25).
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
- [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”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment