lee/renderdoc
1
0
Fork 0
mirror of https://github.com/baldurk/renderdoc.git synced 2026-05-06 01:50:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

When iterating captures, don't compare outputs that are uninitialised

Browse Source
This commit is contained in:
baldurk
2020-07-16 17:17:53 +01:00
parent cccbb18bb9
commit 1316dbc65b
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
util/test/tests/Iter_Test.py
+10
View File
@@ -140,6 +140,11 @@ class Iter_Test(rdtest.TestCase):
else:
debugged = value.value.fv[0:value.columns]
# For now, ignore debugged values that are uninitialised. This is an application bug but it causes false reports of problems
for idx in range(4):
if value.value.uv[idx] == 0xcccccccc:
debugged[idx] = expect[idx]
# Unfortunately we can't ever trust that we should get back a matching results, because some shaders
# rely on undefined/inaccurate maths that we don't emulate.
# So the best we can do is log an error for manual verification
@@ -268,6 +273,11 @@ class Iter_Test(rdtest.TestCase):
debuggedValue = [debugged.value.f.x, debugged.value.f.y, debugged.value.f.z, debugged.value.f.w]
# For now, ignore debugged values that are uninitialised. This is an application bug but it causes false reports of problems
for idx in range(4):
if debugged.value.uv[idx] == 0xcccccccc:
debuggedValue[idx] = lastmod.shaderOut.col.floatValue[idx]
# Unfortunately we can't ever trust that we should get back a matching results, because some shaders
# rely on undefined/inaccurate maths that we don't emulate.
# So the best we can do is log an error for manual verification