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
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Add comment