MVDSTD:SetupOutputBuffers: Difference between revisions

Revision as of 03:09, 25 April 2016 view source Yellows8 (talk \| contribs) Bureaucrats, Administrators 6,264 edits →Response ← Older edit		Revision as of 03:32, 25 April 2016 view source Yellows8 (talk \| contribs) Bureaucrats, Administrators 6,264 edits →Description Newer edit →
Line 71:		Line 71:
	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.		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. It appears a separate frame is written into the buffers for each individual entry.