The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
by pauli on Thursday April 11th 2013, 6:35
The game initially seems to work without any issues. Just setting -nostartup seemed to work with the current version of the game, but I might have all kinds of overrides from other Steam games.
However, upon building more units, buildings and/or exploring the map the game slowly chokes, but it only seems to affect selecting things with the mouse.
The selection rectangle initially just gets a bit choppy but later can lag behind as much as 10 seconds. Same thing with clicking on buildings or even the game menu button, the game might react 10 seconds later. The game is, understandably, unplayable at that point. Mouse scrolling on the other hand remains instant when the cursor reaches the edge.
There are some odd timing related things in the game anyway, so how much of this really has to do with Wine is unclear.
by marcel on Thursday April 11th 2013, 1:32
Hi, when i run the game it starts normally but it;s laggy as hell. When i move with mouse the latency is like 10000ms. When i get mouse onto icon like "single player" it takesfor ever to be framed and after that i can click. Click is fast. When i started game it was same. Horrible latency. What can I do to change it? I don;t see anyone with this type of trouble.
Mouse issues scrolling edge
by Andre on Wednesday April 10th 2013, 14:57
Did someone recognize mouse issues too.
For me it is like if I point my cursor in any direction close to the edge, but not so far that it should start scrolling, the map is scrolled a tiny bit in that particular direction. After that tiny bit it stops.
After that pointing even more far to an edge, to actually scroll, it works just fine.
Visual C++ 2012 Runtime no longer needed
by Nell Hardcastle on Wednesday April 10th 2013, 3:33
There was a comment about installing msvcp110.dll and mfc110.dll. These both belong to the VC++ 2012 runtime and was a requirement of the game before build 58061. That was also causing problems on Windows XP, so the developers built against VC++ 2010 (winetricks vcrun2010) only.
This also means both bugs linked (17273 and 31487) no longer apply.