Reply to thread

Message

<blockquote data-quote="Scythe42" data-source="post: 882683" data-attributes="member: 95833">A workaround for HDMI handshake issues when negotiating the resolution is in the works. A friend of mine had the issue as well (I never had it).&nbsp;I checked his BIOS settings and updated some settings in regards to AHCI/ACPI. I just set everything to the&quot;highest&quot; level (meaning newest version) and also made sure that no &quot;non PNP OS&quot; stuff or other &quot;legacy&quot; options were selected. So a general overhault from the defaults he had. And the issue was gone as he told me. This might not work for everyone as it is largely BIOS dependent and even other equipment can be the cause of problems. You could screw things up bad here. So if you do not know what you are doing, better don't as it might not help you.&nbsp;The problem is that the&nbsp; WDDM driver model when certain ACPI versions are not available, HDMI handshakes work a bit differently (fully according to specs). This results in a visible fullscreen application getting a non cooperative DirectX device message DURING the negotiating setting it to some XGA resolution before negotiating continues instead of AFTER it. And MP can suffer from this depending on your ACPI integration and settings on a BIOS/EFI level (they are also known to be buggy very often at newer versions).&nbsp;In this case the system does try and error as it cannot fully control the interface. ACPI does more stuff than just sleep states. And please don't start to play with tools that manipulate such things on an OS level. This will only make stuff worse. &nbsp;Anyway, long story short:&nbsp;As a workaround MP will minimize itself on such negotiations (meaning it will not be touched at once by the lost D3D device) and later restores itself to the now correct negotiated resolution. This should also apply to S3 states, switching displays and other stuff. Needs some work to test but it should be possible to provide a workaround for most systems that suffer HDMI handshake issues in regards to not minimized full screen apps during the handshake.&nbsp;But the root cause are just bad BIOS defaults that do not allow the GPU to do all the modern stuff &quot;seamless&quot;. &nbsp;Basically any HDMI handshake/negotiating that involved the GPU should not have side effects on MP in the future anymore. This needs some work as the D3D device part that is involved here needs some rework.&nbsp;So please be patient here. I'm working on this one.</blockquote>

[QUOTE="Scythe42, post: 882683, member: 95833"] A workaround for HDMI handshake issues when negotiating the resolution is in the works. A friend of mine had the issue as well (I never had it). I checked his BIOS settings and updated some settings in regards to AHCI/ACPI. I just set everything to the"highest" level (meaning newest version) and also made sure that no "non PNP OS" stuff or other "legacy" options were selected. So a general overhault from the defaults he had. And the issue was gone as he told me. This might not work for everyone as it is largely BIOS dependent and even other equipment can be the cause of problems. You could screw things up bad here. So if you do not know what you are doing, better don't as it might not help you. The problem is that the WDDM driver model when certain ACPI versions are not available, HDMI handshakes work a bit differently (fully according to specs). This results in a visible fullscreen application getting a non cooperative DirectX device message DURING the negotiating setting it to some XGA resolution before negotiating continues instead of AFTER it. And MP can suffer from this depending on your ACPI integration and settings on a BIOS/EFI level (they are also known to be buggy very often at newer versions). In this case the system does try and error as it cannot fully control the interface. ACPI does more stuff than just sleep states. And please don't start to play with tools that manipulate such things on an OS level. This will only make stuff worse. Anyway, long story short: As a workaround MP will minimize itself on such negotiations (meaning it will not be touched at once by the lost D3D device) and later restores itself to the now correct negotiated resolution. This should also apply to S3 states, switching displays and other stuff. Needs some work to test but it should be possible to provide a workaround for most systems that suffer HDMI handshake issues in regards to not minimized full screen apps during the handshake. But the root cause are just bad BIOS defaults that do not allow the GPU to do all the modern stuff "seamless". Basically any HDMI handshake/negotiating that involved the GPU should not have side effects on MP in the future anymore. This needs some work as the D3D device part that is involved here needs some rework. So please be patient here. I'm working on this one. [/QUOTE]

Verification