Posted October 29, 2016
PraetorianWolfie: I've sent this issue to GOG support a few days ago.
The were able to confirm that the launch-crash was happening with the new AMD drivers and that reverting to last months drivers for AMD (Non-WHQL-Win10-64Bit-Radeon-Software-Crimson-16.8.2-Aug11) would fix the issue.
I reverted to July's 16.7.3, which also work ok with these games.
However, if the issue is with the new WDDM 2.1 driver model from Windows 10 Anniversary Update (version 1607), which the new AMD and Nvidia (and any GPU) drivers are going to support, I think the issue will continue to exist in future driver builds unless AMD and Nvidia address this particular case with a bugfix or LucasArts (?) / Disney Interactive issue a patch.
In my case Windows 10 had reverted back to AMD driver version 16.6 - of course without bothering to tell me! I was rather surprised when Monkey 1&2 SE suddenly refused to work. However, going back to 16.8.2 solved things. Now they work again. The were able to confirm that the launch-crash was happening with the new AMD drivers and that reverting to last months drivers for AMD (Non-WHQL-Win10-64Bit-Radeon-Software-Crimson-16.8.2-Aug11) would fix the issue.
I reverted to July's 16.7.3, which also work ok with these games.
However, if the issue is with the new WDDM 2.1 driver model from Windows 10 Anniversary Update (version 1607), which the new AMD and Nvidia (and any GPU) drivers are going to support, I think the issue will continue to exist in future driver builds unless AMD and Nvidia address this particular case with a bugfix or LucasArts (?) / Disney Interactive issue a patch.
P.S.: It does help to check the driver version number from time to time in case Windows 10 feels free (again) to secretly install its preferred driver version without asking and replace the user's version of preference... (at the moment Windows 10 appears to do so every couple of days and that already is my being generous - in the past two days it did so twice! so I can only advise anyone with an AMD card to be rather vigilant as far as currently installed driver versions are concerned! sometimes Windows does rather feel like occupational therapy ;-)...)
P.P.S.:By the way, I have since managed to solve the problem of Windows 10 always installing bleeding version 16.6 over my preferred version (16.8.2) after a couple of days. Go to the Device Manager, click on graphics card and then tell Windows to roll back to the previous driver version (i.e. in my case 16.8.2). The procedure takes a while after which you should reboot. You will now see, at least in the case of version 16.8.2, which happens to be working best with my R9 390 (apart from the last Catalyst version), that AMD Settings acts a little strangely like for example ignoring the banner advertisements setting (sort of on regardless of how you set it...). Even restoring factory defaults does not work. However, you can solve the problem by uninstalling AMD Settings (not the driver) via the Windows control panel and add or remove software. Now all you need to do is to reinstall AMD Settings through the installer of the driver of your choice - in my case, as mentioned above, version 16.8.2. Now you will find that things finally appear to be working again the way they were supposed to!
Post edited November 15, 2016 by patricklibuda