It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Anyone else have problems with Homm3 and the mouse cursor causing graphical glitches and slow downs in the game? The only thing that has changed is I've installed a new video card. I went from a amd 7870 to a RX 480. Same video card drivers in fact (well reinstalled for new card).

The game loads fine but when moving the mouse around on screen it causes corrptions on screen (small black dots as I move mouse around) and disappears randomly. Game is mostly unplayable now.

TIA

Edit:

Looks like it works when in XP3 compatibility mode. But seems to crash repeatedly on the troop barracks screen in a city. Crazy.
Post edited September 08, 2016 by fluran22
ya had the problem too, xp service pack 2 compatibility fixed it for me. I don't have troop barracks crashes though..

Maybe mods might help too.
Just an update, the newest AMD video drivers should fix the problem. 16.9.2, the readme for them mentions this problem.
After game started, in main menu, press "F4". Screen will blink, then You'll get a message about incorrect colour depth, press OK. After that all should work fine.
Greetings.
Post edited February 18, 2018 by FilipSosna
avatar
FilipSosna: After game started, in main menu, press "F4". Screen will blink, then You'll get a message about incorrect colour depth, press OK. After that all should work fine.
Greetings.
Thanks, never had issue like this up until recently, your method fix my problem with black dots.
Thanks for the info FilipSosna.
avatar
FilipSosna: After game started, in main menu, press "F4". Screen will blink, then You'll get a message about incorrect colour depth, press OK. After that all should work fine.
Greetings.
avatar
PainOfSalvation: Thanks, never had issue like this up until recently, your method fix my problem with black dots.
Also, check the checkbox for 256 color in compatibility mode for the program itself. Then, you should not have to mess with F4 again.