sanoj52

Played some more today, and I noticed it's been bumped to 0.99something. It didn't crash, and I finished the fourth mission without problems. Difficulty ramps up there, but it is manageable. Are you planning on having difficulty settings for the campaign? If not, you should make this mission a bit easier, or you might get a lot of frustrated customers - I don't think I would have beaten it without my previous experiences in skirmishes and MP, and I'd assume many will play the

I've seen the same, and I assume it is a bug. My workaround is to build new factories closer to the frontline, so it is even good for something - without that bug I always forget about building a forward base.

Reading again what I wrote I realise that it sounds dismissive of your feedback and I apologise for that. My intention was rather to let the devs know that the problems you describe are not a 100% reproducible... I thought the AI sending this small force against the brain whale was fitting in the sense it(?) had no idea what it was up against, and seeing the small force wiped out in a matter of seconds made Haalee realise that it severely underestimated the enemy, thus

The third mission worked flawlessly for me, and I actually did like the humour of the 'well, that was embarrassing'. But another thing that I have been noticing for a while now (not specific to this version): There still seems to be a problem with armies. Sometimes when the main unit died while the army was selected, the buttons for forming and disbanding the army would be greyed out, and some of the units would just sit there and do nothing, while others would

So far I played the tutorial and the first mission of the campaign (Kepler). General suggestions/ideas/...: I suppose this is planned already for the release version, but I really like having (the choice of) subtitles in movies and cutscenes. English is not my native language, and I'm sometimes having a hard time understanding it when there are music or noises in the background. The way the game "focuses" on the small window with the messages duri

I could leave my antivirus running and Ashes didn't crash, so that's nice. According to my monitoring tool it uses less RAM, too (~6GB max after running the benchmark and two matches on small maps, compared to 11GB max with Beta 2). Also, I like the new smoother graphs on whatever the screen is called that you get after winning (or losing) a match. Performance stayed the same (~35 FPS on High with a GTX 960).

Set the 'Bind Cursor' option to always. Default is fullscreen only.

8-6-3

Xeon E3-1231 v3, 8GB, GTX 960 4GB, Windows 10

OK, so for me the solution was to let Windows handle the size of the pagefile. I had limited it to 2GB, which apparently wasn't enough for this game...

I have the same problem, but with a fresh install and a Nvidia GTX 960.