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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment