Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
2
Found in
6000.4.0b3
6000.5.0a4
Issue ID
UUM-131992
Regression
No
“dstorage.dll“ and “dstoragecore.dll“ are present when "Enable DirectStorage" setting is disabled
Reproduction steps:
1. Create new project
2. Open the Player Settings (Edit > Project Settings > Player)
3. Under Other Settings > Configuration note that “Enable DirectStorage“ is disabled
4. Open Build Profiles (File > Build Profiles)
5. Build
6. Open the Build’s folder
Expected result: “dstorage.dll“ and “dstoragecore.dll“ does not exist
Actual result: “dstorage.dll“ and “dstoragecore.dll“ are present
Reproducible with: 6000.4.0b3, 6000.5.0a4
Could not test with: 6000.0.65f1, 6000.3.4f1 (“Enable DirectStorage” setting does not exist)
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
- After deleting the both DLL files, Player won’t start
Add comment
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
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may impact this issue.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may impact this issue.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.