DX12 Crashes after loading screen

Thanks for the head's up.  That's a pretty good test system for us.  Does it work on DX 11 for you?  On that particular card, DX 12 isn't going to do much (if anything) for you.

Hi!

It works well in DX11. I'm a bit surprised to learn that DX12 won't do much for my GTX 670. I thought it would help. The card has a lot of horsepower for its age, but I suppose it's just a question of the tech on the chip. It is a few generations behind after all.

Not worried though as I'm waiting for nVidia Pascal to change my rig. 

If there's anything else I can provide you with, don't hesitate!

Thanks!

Good evening,

I'm having a similar issue to this.

My rig:

• 5930K at 4.5GHz
• 2x Titan Xs at 1404 MHz
• SM951 m2 512 GB
• 16 GB RAM
• Watercooled
• 3440x1440 60hz monitor

Just got the game. I can run it in normal mode including the benchmark fine but when I try to launch in DX12 it freezes every time on the loading screen "optimizing turinium cores".

Win 10 Pro x64

8GB DDR3

FX-9590

2x R9-290x

Anything I can try to get it to work in DX12 mode?

Just to be clear, if people can let us know explicitgly if they're able to run it in DX 11, then we can check DX 12.

@Total: Are you running multi-gpu?  If you are, what happens if you turn it off?

I may have misunderstood you Golith but SLI is not yet enabled, that is a driver issue so you'll have to wait for Nvidia on that. Multi-GP is under DX12, SLI is under DX11, they are separate systems; there is no such thing as SLI in DX12, that is why it is referred to as multi-GPU under DX12. If multi-gpu works well for you as you state then you are good to go.

Looks like I hit the post cap so using an old post. 

Essentially your telling me that SLI/crossfire simply isn't going to exist in a DX12 environment since mGPU replaces it? I'll try and re-run a test that I saw earlier, but the conclusion was DX12 has about 20% better multi-gpu scaling. If that's true I could see SLI not being developed at all.

Now another interesting thing I saw was that a lot of software such as SLI by default and MSI Afterburner (overclocking software) allow the synchronization of GPU speeds. While running the DX12 mGPU test I saw my one GPU break this synchronization and overclock to another 40 MHz which did cause the client to crash about 1 minute later (too high of OC). I ended up un-checking synchronization and lowering the OC till it matched the other GPU and everything was peachy. My question is, I know a lot of folks would like a way to synchronize similar make/model GPUs if they are overclocking for simplicity sake.

I may have misunderstood you Golith but SLI is not yet enabled, that is a driver issue so you'll have to wait for Nvidia on that. Multi-GP is under DX12, SLI is under DX11, they are separate systems; there is no such thing as SLI in DX12, that is why it is referred to as multi-GPU under DX12. If multi-gpu works well for you as you state then you are good to go.

Edit. Re-reading this again it could be taken the wrong way. I was just trying to write it simply so there was no misunderstanding. ta

Forgot to mention before running latest 16.1.1 drivers. Yea, so I disabled crossfire for the game profile in CCC and it launched in DX12 mode. Reenabled crossfire and tried again and it froze like before so for me anyways crossfire is the issue. Is crossfire not supported yet or there is just some particular issue I am experiencing? Thanks.

CF is not supported yet, you'll have to wait on drivers for them. Turn it off, load up DX12 version of the game, turn on multi-GPU, restart the game and then see if the game is now using both GPUs. If it doesn't then yeah, you got a problem.

Also latest drivers are version 16.2 I believe, came out a couple days ago.

(assuming you can get in the game as it looks like your initial problem was that you couldn't get in)

Explicitely, DX11 works, DX12 crashes...

By the way, referring to your comment, I found this:

http://wccftech.com/directx-12-draw-calls-330-3-year-gtx-670/

So, I believe DX12 does have a positive impact, even on a GTX 670 card. So does it mean that the graphics engine Ashes is running on doesn't take advantage of it?

Thanks,

So it appears that people who have SLI and Crossfire enabled who checked mGPU in the DX12 client end up crashing. 

I think that clears things up.

No it doesn't. 

I have a single GTX 670 card and it still crashes in DX12, doesn't clear up anything for me...

Is it possible to have mGPU enabled even if you have one GPU?  If so that could crash it maybe?

If I could get in the game and enable multiple GPU, maybe, but I crash at the loading screen. 

The game just doesn't like running on my GTX670 / Driver version in DX12 mode. That's something they need to fix on their end.

Hi there,

Thought I would add that on my single card setup, I have a similar issue (bought the game today). I hit the initial loading screen on DX12 but it never gets past there and I have to CTRL+ALT+DEL or hard reset.

DX11 I can open and run the benchmark (haven't tried play yet) but DX12 is a no go.

Running an i5 2500k (4.5 GHz), R9 290 (Sapphire Tri X, lightly OCed), 8 GB 1600 MHz RAM.

Thanks!

Ashes Troubleshooting guide:

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

If that doesn't help please open a support ticket:

https://esupport.stardock.com/index.php?/default_import/Tickets/Submit

This worked for me...! DX12 now runs fine. I followed every step to the letter and it loads just fine now...

thanks!

Troubleshooting seemed to help - had few changes I could make other than delete the .ini and validate on Steam. Turns out one file was incorrect so DX12 loaded fine for me after (and benchmark showed enormous performance gains from DX11).

Thanks!

So updated / did clean install of newest AMD 16.2 drivers. Tried to launch in DX12 mode and kept freezing before getting to main menu. Deleted the settings .ini file which I couldn't find at first but found in Users\Onedrive\Documents etc instead of dir mentioned in the troubleshooting link, might want to update that as an option and then it would launch to main menu fine with crossfire disabled for the Ashes profile.

As soon as I enable multiple gpu's in game in settings and go to restart the game it freezes again before reaching the main menu and I have to delete the settings file again. I only updated this machine to windows 10 less then a month ago and did a clean install and just did clean install of 16.2 gpu drivers so I don't know what the issue would be that it refuses to work once I try to enable multi gpus.

I have crash issues as well. I just installed the game on a just broke in system and anything with more than 2 dreadnoughts on the board will crash alot.

System specs:

AMD 8350

32G ram

2 R9 390 MSI graphics cards (8G Vram)

Corsair 850W PSU

Air cooled maxes out to 70C

The game benchmark only uses 1 video card (crossfire enabled). The multi GPU button does not work. Graphics on crazy or low does not help crash issues. I did initially load it with DX 12 and it ran for a bit but crashed as well and there were almost no units on the board. I also got a crash to a red screen (new for me) and have had issues needing to restart the system to put the desktop back to the proper resolution. Gotta love beta

Jedtats, the game does not support crossfire so you don't want that enabled. DX11 currently only supports 1 GPU. For 2 GPUs you need to run DX12 with CF off and then select the mGPU from the game's menu. I am not sure it will work for you as you say DX12 crashed but thought I would clear up the CF confusion. Don't forget to use the 16.2 AMD drivers, they only came out a few days ago.