Search Issue Tracker
Not Reproducible
Votes
5
Found in
4.5.0b1
Issue ID
588418
Regression
No
"SUCCEEDED(hr)" error message is hard to understand
"SUCCEEDED(hr)" error message is hard to understand.
To reproduce:
- Open attached project on a computer with DX10 GPU
- Launch "_SimpleComputeBuffer" scene and hit Play
- Observe the "SUCCEEDED(hr)" error message in Console
Actual result: As a user it is hard to understand what this error message means.
Expected result: An error message that explains what the issue is.
A screen shot is also attached.
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
- “Label” name in Sprite Library Editor window lacks character limit causing long names go under the Object Field
- Preview image (screenshot) is not available after capturing snapshot in Memory Profiler
- Crash on UNITY_FT_Stream_ReadAt when changing TMPro properties after unloading an AssetBundle
- Particles spawn at the same position when using raw byte address buffer in VFX Graph
- Decal Shader Graph - Custom vertex interpolators are always 0
SpiritWalker
Sep 12, 2016 00:37
http://answers.unity3d.com/questions/874313/succeeded-hr-error-on-console-and-cant-see-the-ins.html
Solution by Sanky worked for me.
flashmandv
Sep 08, 2016 16:12
It happens every time I built or play.
Another error pops next to this:
rc.right == m_GfxWindow->GetWidth() && rc.bottom == m_GfxWindow->GetHeight()
sosh
Aug 08, 2016 14:28
Same problem here.
_EdzUp_
Aug 18, 2015 13:01
I think its daft that the editor itself requires DX10 to actually do things everything is fine and dandy on a DX9 GPU its only every popup and editor function that throws the message to the console.
LoneBlackfang
Jul 11, 2015 22:15
this error shows up due to the fact the Unity 3D now uses DX11 and your computer is unable to run it correctly