Search Issue Tracker
Fixed in 5.3.5
Votes
0
Found in
Issue ID
788164
Regression
No
0x80070057 and 0x887A0005 errors on Intel cards
We don't have a solid repro case for this, but we have lots of errors with 0x80070057 and 0x887A0005 ( DXGI_ERROR_DEVICE_REMOVED ? ) which have been reported in the wild with an automated crash reporter
Comments (5)
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
- Crash on mono_dump_native_crash_info when changing a Particle System Renderer’s Material Shader to Standard Unlit
- VFX Prefab doesn’t have Preview icon in Project window and Preview window is empty in Inspector window
- Visual Effect Graph error message does not disappear and lasts forever until the Visual Effect Graph is reopened even when the error causing connection/node is deleted and Visual Effect Graph is saved
- “RenderSettings customReflection texture has invalid type” error keeps getting thrown even when Environment Reflections was set back to Skybox from Custom with an invalid texture
- Particle System with the custom Material breaks the Scene view when the material is using a Shader Graph with the Texture with the power of negative value
olkeencole
Aug 10, 2017 19:25
Out of curiosity, are any of you using the mesh compression on the import settings for some of your models?
HarryCodder
Mar 09, 2017 09:45
We're having those in 5.4.4 as well.
valtterip
Jan 28, 2017 20:44
We are on the verge of a game release and ran into this issue with 5.4.1f1, according to this bug this should be fixed in the Unity version we are using, or is it?
Huge amount of these notes, so far reproducible only on a system using Renderer: Intel(R) HD Graphics 4600 VRAM: 1136 MB
d3d11: failed to create 2D texture id=839 width=64 height=64 mips=7 dxgifmt=28 [D3D error was 887a0005]
d3d11: failed to create 2D texture shader resource view id=839 [D3D error was 80070057]
...
Ps. Forcing DX9 (-force-d3d9 params) are often proposed as a workaround for this and it seems to work in our case as well, this strongly indicates the issue is not fixed in 5.4.1f1.