Now hesitating on updating until something can be done about those frustratingly notorious issues.
It is always destined to happen 99% of the time for drivers to break something on updates even though other things get fixed.
I am still waiting in terror for the Game Ready drivers to have a stable update after the several glitch-tastic builds potentially bricking computers upon updating. (if it ain't fixed,don't break it more)
And if a Shield TV hotfix can be done (hopefully ASAP) and succeed,I could finally change my signature to reflect the new version number.
@MonadoBoy: Maybe I should try that Dolphin version to see if it works right on 3.2 like my current installed build,please tell me the build number you tried initially on the upgrade.
It is always destined to happen 99% of the time for drivers to break something on updates even though other things get fixed.
I am still waiting in terror for the Game Ready drivers to have a stable update after the several glitch-tastic builds potentially bricking computers upon updating. (if it ain't fixed,don't break it more)
And if a Shield TV hotfix can be done (hopefully ASAP) and succeed,I could finally change my signature to reflect the new version number.
@MonadoBoy: Maybe I should try that Dolphin version to see if it works right on 3.2 like my current installed build,please tell me the build number you tried initially on the upgrade.
Shield TV Pro (stock/non-rooted OTA 6.3)
Acer Aspire E 15 E5-575G-59EE
CPU: i5-6200U 2.3-2.8Ghz _ GPU: Nvidia GeForce 940MX 2GB (GDDR5) VRAM
Hyundai 8GB DDR4 Dual-channel SDRAM _ 1000GB HDD
New; CPU: Intel i9 9900KF_ GPU: Nvidia RTX 2060 Super | ◕‿◕
Acer Aspire E 15 E5-575G-59EE
CPU: i5-6200U 2.3-2.8Ghz _ GPU: Nvidia GeForce 940MX 2GB (GDDR5) VRAM
Hyundai 8GB DDR4 Dual-channel SDRAM _ 1000GB HDD
New; CPU: Intel i9 9900KF_ GPU: Nvidia RTX 2060 Super | ◕‿◕
