mirror of
https://github.com/baldurk/renderdoc.git
synced 2026-05-05 01:20:42 +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.
49 lines
1.5 KiB
Python
49 lines
1.5 KiB
Python
import renderdoc as rd
|
|
import rdtest
|
|
|
|
|
|
class GL_State_Trashing(rdtest.TestCase):
|
|
demos_test_name = 'GL_State_Trashing'
|
|
|
|
def check_capture(self):
|
|
last_action: rd.ActionDescription = self.get_last_action()
|
|
|
|
self.controller.SetFrameEvent(last_action.eventId, True)
|
|
|
|
self.check_triangle(out=last_action.copyDestination)
|
|
|
|
action = self.find_action("Draw")
|
|
|
|
self.controller.SetFrameEvent(action.eventId, False)
|
|
|
|
postvs_data = self.get_postvs(action, rd.MeshDataStage.VSOut, 0, action.numIndices)
|
|
|
|
postvs_ref = {
|
|
0: {
|
|
'vtx': 0,
|
|
'idx': 0,
|
|
'gl_Position': [-0.5, -0.5, 0.0, 1.0],
|
|
'v2f_block.pos': [-0.5, -0.5, 0.0, 1.0],
|
|
'v2f_block.col': [0.0, 1.0, 0.0, 1.0],
|
|
'v2f_block.uv': [0.0, 0.0, 0.0, 1.0],
|
|
},
|
|
1: {
|
|
'vtx': 1,
|
|
'idx': 1,
|
|
'gl_Position': [0.0, 0.5, 0.0, 1.0],
|
|
'v2f_block.pos': [0.0, 0.5, 0.0, 1.0],
|
|
'v2f_block.col': [0.0, 1.0, 0.0, 1.0],
|
|
'v2f_block.uv': [0.0, 1.0, 0.0, 1.0],
|
|
},
|
|
2: {
|
|
'vtx': 2,
|
|
'idx': 2,
|
|
'gl_Position': [0.5, -0.5, 0.0, 1.0],
|
|
'v2f_block.pos': [0.5, -0.5, 0.0, 1.0],
|
|
'v2f_block.col': [0.0, 1.0, 0.0, 1.0],
|
|
'v2f_block.uv': [1.0, 0.0, 0.0, 1.0],
|
|
},
|
|
}
|
|
|
|
self.check_mesh_data(postvs_ref, postvs_data)
|