Ashes of the Singularity v1.1

1 bug in DX11 mode, another bug in DX12 mode

Hi !

While attempting to play with v. 1.1, in DX12 mode, I repeatedly experienced this : I try to select units by using area selection with the mouse and instead of selecting units the game freezes : the game doesn't respond to any command event the Escape key to get to the Menu !  I have to kil the process to end the game.  It never happened with the previous release of the game.

While attempting to play with v. 1.1, in DX11 mode, when I loose against the AIs I get the finale message which contains a "Done" button : when I press the "Done" button, the game freezes and the main menu never shows up.  It never happened with the previous release of the game.

I have no screen shots but those 2 bugs can be reproduced with just a little time.

My CPU is an AMD FX-9370 running at 4.4 Ghz and my 2 graphics cards are ASUS Strix GeForce GTX-980 OC Edition. I have 16 Gigs of RAM and my paging file (virtual memory) is set 33792 megs. expandable to 65536  megs. I use 64 bit Windows 10 v. 1511.

To the Devs : Thanks in advance for fixing the bugs !

To all others : Thanks in advance for any help about that !

 

 

 

 

 

6,337 views 10 replies
Reply #1 Top

Hello,

 

I have the following

Asus X99-Pro/USB 3.1

5820K

2 x 980 TI in MGPU 

16GB Ram

Intel 840 SSD

Asus Essence STX sound card

Acer X34 Predator Gsync @ 95hz (3440x1440)

 

Today i played Ashes for the first time since the recent patch, i just experienced my first crash. I am pretty sure i had just selected some units and the game froze up. I could move the mouse still and tried to Alt Tab and Ashes wouldnt respond, went white and asked me if i wanted to close the application.

So possibly had the same as the OP.

 

Hope this gets patched out ASAP, thanks in advance.

Reply #2 Top

I have the same problem here... the game crash every time i try to play... this happend like 5-20 min of game played. 

 

Some times its happend when i try to load a saved game or when i minimize the game.

 

I have this comp

 

Saberthoot Z77

12gb ddr3 1600mhz

970 gtx EVGA SC on SLI

i5 3570k stock

Playing on HDD

Have played whit the 364.51 drivers before and after the last patch, and now i tried whit 361.91 (recommended for ashes) and the problem still happend.

 

Grettings.

Reply #3 Top

If I ever have any issues with game updates I will make sure my GPU and audio drivers are up-to-date. And, if the game's from Steam, I'll right-click it in my Library, select Properties, click the Local Content tab, and either have it check the integrity of my local files or delete local files and re-install. No idea whether this will help in your instances. But it is the first thing I do whenever anything like this occurs.

Good luck!

Reply #4 Top

I had the same issue a few games after the update, 5 mins in and 5 constructors built it crashed...

 

I have;

MSI z170a M7 Gaming board

i7 6700 3.4 CPU

8 Gb RAM (3200)

MSI GTX980 Ti OC

Playing on Samsung NVMe SSD

I've updated drivers for all.

 

 

 

Reply #5 Top

First see the common solutions in the troubleshooting guide. If you still have issues please follow the instructions at the bottom of the guide on how to use the support tool and submit a support ticket so we can assist further.

https://esupport.stardock.com/index.php?/Knowledgebase/Article/View/530/175/general-ashes-of-the-singularity-troubleshooting

 

Reply #6 Top

Quoting LordVader2194, reply 4

I had the same issue a few games after the update, 5 mins in and 5 constructors built it crashed...


I have;

MSI z170a M7 Gaming board

i7 6700 3.4 CPU

8 Gb RAM (3200)

MSI GTX980 Ti OC

Playing on Samsung NVMe SSD

I've updated drivers for all.
 
End of LordVader2194's quote

 

Try again without the overclock on your GPU. Because more CPU cores can talk to the GPU in Ashes than most games it has to work a lot harder so overclocks become unstable. Worth trying at default clocks.

Reply #8 Top

Quoting Kazzerigian, reply 3

If I ever have any issues with game updates I will make sure my GPU and audio drivers are up-to-date. And, if the game's from Steam, I'll right-click it in my Library, select Properties, click the Local Content tab, and either have it check the integrity of my local files or delete local files and re-install. No idea whether this will help in your instances. But it is the first thing I do whenever anything like this occurs.

Good luck!
End of Kazzerigian's quote

 

After this step I'll check temps. I'll check temp max on CPU and GPU and run HWMonitor, or something like it while playing the game to monitor temps.

Reply #9 Top

Quoting LordVader2194, reply 7

Its a factory stable OC mate, bought like that, I'm not that daft to push them myself lol
End of LordVader2194's quote

Ah, fair enough. The problem seems common enough that it looks like it is either a game bug or a driver issue rather than peoples hw/sw. All the cards people list with this kind of problem here or on Steam forums seem to be running Nvidia. 3rd option I guess is a common piece of software that all the users have which causes it causing it, but the problem seems to persists in both dx11 and dx12 so that makes that less likely. If it is software anti-virus is the most common culprit.

Reply #10 Top

You could also try turning of a-sync compute in the games .ini file as that seems the most obvious thing from a layman's point of view (me :)) where Nvidia GPUs may hiccup on (in case it is Nvidia cards only).