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
- [VFX] Custom HLSL with 'int' parameter, without the 'in/out/inout' access modifier is not supported
- [Windows] Lens Flare doesn't work in the Lens Flare Showroom URP Sample Scene
- Crash on ujob_execute_job while using OverlapBoxCommand when collisions are more than maxHits
- The validity of the multiple handles can behave differently based on the load/release operations order, when multiple Addressables.LoadAssetAsync and Addressables.Release are used to load and release the same Addressable Asset
- Dynamic text is rendered in the background when it is inside the <font> tag
Add comment