MVDSTD:SetupOutputBuffers: Difference between revisions

Created page with "=Request= {| class="wikitable" border="1" |- ! Index Word ! Description |- | 0 | Header code [0x001F0902] |- | 1-35 | 0x8C-byte input structure. |- | 36 | Size of each buffe..."
 
 
(3 intermediate revisions by the same user not shown)
Line 32: Line 32:
| 1
| 1
| Resultcode
| Resultcode
|-
| 2-17
| Output state
|}
|}


Line 72: Line 69:
This command isn't used by SKATER.
This command isn't used by SKATER.


This loads the input structure into state, the vaddrs are also converted to physaddrs.
This loads the input structure into state, the vaddrs are also converted to physaddrs. It appears using this command multiple times will replace the entry-list in state with the input entry-list.


Once this command is used, each [[MVDSTD:ControlFrameRendering|rendered]] frame will be written into the output buffers specified by the entry-list in state, instead of the output buffers from configuration. Exactly how multiple entries is handled during rendering is unknown.
Once this command is used, each [[MVDSTD:ControlFrameRendering|rendered]] frame will be written into the output buffers specified by the entry-list in state, instead of the output buffers from configuration. A separate frame is written into the buffers for each individual entry.