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
- Red spots appear when Blending Lighting Scenarios using Adaptive Probe Volumes
- [Windows] About Unity Window needs to be opened twice to adapt to resolution
- NullReferenceException and temporary graph corruption after entering playmode if output node connection was changed
- Sprite Renderer with Animation does not reflect Sprite changes in the Scene when switching Mask Interaction
- Error "NullReferenceException: Object reference not set to an instance of an object" is present when loading 3D text mesh in Player from an asset bundle that is built with an older Editor version
Add comment