Reply to thread

Message

<blockquote data-quote="Seeco" data-source="post: 309175" data-attributes="member: 58425">For no apparent reason I have also been getting this error message lately, before it has always worked flawlessly regardless of which of DirectDraw or Direct3D I would use. Using DirectDraw solves the issue for me as well, although I'm not sure what exactly the effect is of doing so. I have to point out though that in recent betas of Reclock the DirectDraw is actually marked as &quot;preferred&quot; instead of Direct3D which used to be so. That if anything should point to that using DirectDraw does not result in a lowered functionality. It would be strange to put an option at the very top of the program's config which renders the whole thing unusable <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />If anybody has any insights to what the effect of either choice is I would be very interested in hearing it.</blockquote>

[QUOTE="Seeco, post: 309175, member: 58425"] For no apparent reason I have also been getting this error message lately, before it has always worked flawlessly regardless of which of DirectDraw or Direct3D I would use. Using DirectDraw solves the issue for me as well, although I'm not sure what exactly the effect is of doing so. I have to point out though that in recent betas of Reclock the DirectDraw is actually marked as "preferred" instead of Direct3D which used to be so. That if anything should point to that using DirectDraw does not result in a lowered functionality. It would be strange to put an option at the very top of the program's config which renders the whole thing unusable :) If anybody has any insights to what the effect of either choice is I would be very interested in hearing it. [/QUOTE]

Verification