I stumbled across the Settlers History Editions yesterday and since I am huge fan of the original, extensively played on an Amiga 500 ages ago, I just went and bought the updated version for modern PCs. I hoped for fullscreen but hey, even a window would be alright...
...if I could play at all. The mouse works up to the mission screen, as soon as I am on the map there's no response. Frame rate is around something between 5-20 fps. Don't know if that's somehow relevant. Playing with keyboard works, but that's rather painful.
Anyone knows something before I'll try to get a refund?
Thanks.
well then, some specs before someone at UBI is asking for the obvious:
- The Mouse is a Logitech MX518. Wether I used Logitech software (G Hub) or not did not matter.
- As described above: Using the keyboard for player 1 works but is cumbersome
- I own a multidisplay setup. First is an LG on 3840 x 2160 resolution, second HP with Full HD
- for this setup I use to graphic cards: The LG is connected to a Geforce GTX 1080, the HP to internal Intel HD 530
- its irrelevant on which screen I am trying to play
- CPU is a nice Intel Core i7 6700K
- RAM is 32GB
- runs on Win10 Pro, x64
Now the fun part
As soon as I connect a standard MS XBox controller to the rig, the game fails when I try to launch through UPlay. Doesn't matter if I configure the game controls to use the controller or not, it does not work. Configuring the controller for player 1 on running the game directly by Siedler1-exe (as administrator, win7 compatible) from the installation folder, the game starts again.
Mouse still does not work, but playable with controller (okayish).
My guess is: Someone f*cked up the DirectX Inputs and those get slushed through an extra layer in UPlay. If I am getting this right there are two bugs.