I got enthusiastic about testing the new builds on my HTPC since the ubershaders were merged. I have had no problems with Dolphin 5.0. But now the newer builds have something going on with the monitor initialization. I have not forked out the culprit, yet, but I'm guessing it has something to do with the Quad-buffered stereoscopy (??) and the following changes.
The problem is this: using the newest builds (on portable installation, only GFX backend switched to D3D (OGL works)), the screen (on my case 3D capable LCD television (Samsung)) switches to 30Hz and the TV says that it has enabled the 3D mode as soon as I launch any game. When I check the display driver properties, it really says 29Hz 1920x1080, and I can not change it back to 59/60Hz as long as Dolphin is running. The screen also appears to have false "blueish" color temperature, as the TV's 3D mode is set up to change this. And the stereoscopy IS off in Dolphin, since I have all the default settings in the portable installation.
I have Windows 10 64bit with latest updates and Intel HD 4600 with the latest drivers from Intel. This also happened with Windows 8.1 64 bit, as I had this up until yesterday and I was too tempted to see if this was a problem with Intel's probably outdated HD 4600 drivers for Win 8.1. Updating to Win 10 (and latest Intel drivers) did not change this.
Anyone else?
The problem is this: using the newest builds (on portable installation, only GFX backend switched to D3D (OGL works)), the screen (on my case 3D capable LCD television (Samsung)) switches to 30Hz and the TV says that it has enabled the 3D mode as soon as I launch any game. When I check the display driver properties, it really says 29Hz 1920x1080, and I can not change it back to 59/60Hz as long as Dolphin is running. The screen also appears to have false "blueish" color temperature, as the TV's 3D mode is set up to change this. And the stereoscopy IS off in Dolphin, since I have all the default settings in the portable installation.
I have Windows 10 64bit with latest updates and Intel HD 4600 with the latest drivers from Intel. This also happened with Windows 8.1 64 bit, as I had this up until yesterday and I was too tempted to see if this was a problem with Intel's probably outdated HD 4600 drivers for Win 8.1. Updating to Win 10 (and latest Intel drivers) did not change this.
Anyone else?