Reply to thread

Message

<blockquote data-quote="Sebastiii" data-source="post: 1233685" data-attributes="member: 60104">Let me explain the logs :When it failed :You see here when madVR start :[2017-11-19 15:19:39,147] [&nbsp; &nbsp; &nbsp;&nbsp; 0] [ 814] - MPMadPresenter::Constructor() - instance 0x35208968[2017-11-19 15:19:39,147] [&nbsp; &nbsp; &nbsp;&nbsp; 0] [ 814] - MPMadPresenter::Constructor() Store Device SurfaceBut no D3D device happen <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" /> (so madVR is waiting something to send the D3D information to MP)In this case it works :We can see that madVR send us D3D device :[2017-11-19 15:12:36,399] [&nbsp; &nbsp; &nbsp;&nbsp; 0] [ 3d8] - MPMadPresenterH: setDeviceSub() device 0x:4667ac00Then like it's MVC, madVR reset D3D and send us :[2017-11-19 15:12:36,513] [&nbsp; &nbsp; &nbsp;&nbsp; 0] [ 3d8] - MPMadPresenterH: setDeviceOsd() device 0x:0And then we get the final D3D device :[2017-11-19 15:12:41,550] [&nbsp; &nbsp; &nbsp;&nbsp; 0] [2040] - MPMadPresenter: setDeviceOsd : ForceOsdUpdateAnd when we get those and those line :[2017-11-19 15:12:45,579] [&nbsp; &nbsp; &nbsp;&nbsp; 0] [2040] - MPMadPresenter::ReinitOSD : ReinitOSD from : RenderOsd[2017-11-19 15:12:45,581] [&nbsp; &nbsp; &nbsp;&nbsp; 0] [2040] - MPMadPresenter::ReinitOSD : ReinitOSD for : 1920 x 1080Rendering has started <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue&nbsp; &nbsp; :p" loading="lazy" data-shortname=":p" />So when the rendering doesn't start -&gt; boom -&gt; bs -&gt; because of the deadlock <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" /></blockquote>

[QUOTE="Sebastiii, post: 1233685, member: 60104"] Let me explain the logs : When it failed : You see here when madVR start : [2017-11-19 15:19:39,147] [ 0] [ 814] - MPMadPresenter::Constructor() - instance 0x35208968 [2017-11-19 15:19:39,147] [ 0] [ 814] - MPMadPresenter::Constructor() Store Device Surface But no D3D device happen :( (so madVR is waiting something to send the D3D information to MP) In this case it works : We can see that madVR send us D3D device : [2017-11-19 15:12:36,399] [ 0] [ 3d8] - MPMadPresenterH: setDeviceSub() device 0x:4667ac00 Then like it's MVC, madVR reset D3D and send us : [2017-11-19 15:12:36,513] [ 0] [ 3d8] - MPMadPresenterH: setDeviceOsd() device 0x:0 And then we get the final D3D device : [2017-11-19 15:12:41,550] [ 0] [2040] - MPMadPresenter: setDeviceOsd : ForceOsdUpdate And when we get those and those line : [2017-11-19 15:12:45,579] [ 0] [2040] - MPMadPresenter::ReinitOSD : ReinitOSD from : RenderOsd [2017-11-19 15:12:45,581] [ 0] [2040] - MPMadPresenter::ReinitOSD : ReinitOSD for : 1920 x 1080 Rendering has started :p So when the rendering doesn't start -> boom -> bs -> because of the deadlock :( [/QUOTE]

Verification