Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 1013987" data-attributes="member: 10858">Exactly, I was just stating how bad the current MP1 implementation for the vizualization is (please see the attachement which shows the visial aspect - technical side is even far more worse <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />).&nbsp;As stated earlier the whole visualization in MP1 should be rewritten - preferrably in such way that D3D textures are used for the data passing, that way the visualisation provider can render directly to a D3D surface (using pixel shaders etc) and then MP Skin Engine can just compose UI. It would be the most efficient way to handle the visualization and also it would give really good ability to use modern GPU resources for the actual visualization. 2nd option would to allow bitmaps to be trasnferred between MP Skin Engine and visualization provider, but that is already pretty horrible solution (even thou better than current) and shouldn't be implemented.</blockquote>

[QUOTE="tourettes, post: 1013987, member: 10858"] Exactly, I was just stating how bad the current MP1 implementation for the vizualization is (please see the attachement which shows the visial aspect - technical side is even far more worse :)). As stated earlier the whole visualization in MP1 should be rewritten - preferrably in such way that D3D textures are used for the data passing, that way the visualisation provider can render directly to a D3D surface (using pixel shaders etc) and then MP Skin Engine can just compose UI. It would be the most efficient way to handle the visualization and also it would give really good ability to use modern GPU resources for the actual visualization. 2nd option would to allow bitmaps to be trasnferred between MP Skin Engine and visualization provider, but that is already pretty horrible solution (even thou better than current) and shouldn't be implemented. [/QUOTE]

Verification