mirror of
https://github.com/baldurk/renderdoc.git
synced 2026-05-05 17:40:39 +00:00
baldurk
7149302680
* There's not a good accepted terminology for this kind of event, and for historical reasons 'drawcall' has been the accepted term, even though that can be quite confusing when a dispatch or a copy is a 'drawcall'. * This is particularly highlighted by the event browser filters where $draw() includes draws and dispatches, but $dispatch() only includes dispatches, it's hard to intuitively understand why $draw() matches all of these calls. * As a result we've defined the term 'action' to cover these types of events in the same way that we defined 'event' in the first place to mean a single atomic API call.
31 lines
891 B
Python
31 lines
891 B
Python
import rdtest
|
|
import renderdoc as rd
|
|
|
|
|
|
class VK_VS_Max_Desc_Set(rdtest.TestCase):
|
|
demos_test_name = 'VK_VS_Max_Desc_Set'
|
|
|
|
def check_capture(self):
|
|
|
|
action = self.find_action("Draw")
|
|
|
|
self.check(action is not None)
|
|
|
|
self.controller.SetFrameEvent(action.eventId, False)
|
|
|
|
pipe: rd.PipeState = self.controller.GetPipelineState()
|
|
|
|
# We only need to check the color output for the first vertex - if we got that, the test succeeded.
|
|
# We're not testing VS out fetch in general here, just that it works when there's no spare descriptor set
|
|
postvs_data = self.get_postvs(action, rd.MeshDataStage.VSOut, 0, 1)
|
|
|
|
postvs_ref = {
|
|
0: {
|
|
'vtx': 0,
|
|
'idx': 0,
|
|
'vertOut.col': [1.0, 0.2, 0.75, 0.8],
|
|
},
|
|
}
|
|
|
|
self.check_mesh_data(postvs_ref, postvs_data)
|